tracker issue : CF-3121288

select a category, or use search below
(searches all categories and all time range)


| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/AsDesigned

Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff (Aaron Neff)

Created: 02/23/2012

Components: Language, Java Integration

Versions: 10.0

Failure Type: Enhancement Request

Found In Build/Fixed In Build: Public Beta /

Priority/Frequency: Trivial / Unknown

Locale/System: English / Platforms All

Vote Count: 1

Even tho it's THIS-scope'd, javaSettings is only read when the application starts.  Some, like myself, may assume javaSettings is read on _any_ request that follows applicationStop().

An applicationStop() shouldn't be necessary, just to reload javaSettings.  It would be helpful to have a javaSettingsReload(), just as there is an ormReload().

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3121288

External Customer Info:
External Company:  
External Customer Name: itisdesign
External Customer Email:



Related thread:
Comment by External U.
20631 | February 23, 2012 12:39:00 AM GMT
We can't go on adding a new function for every setting that goes in the application.cfc. One should use ApplicationStop to reload the application.
Comment by Rupesh K.
20632 | February 28, 2012 12:49:17 AM GMT
Hi Rupesh, Thanks for the follow-up. Could it be documented that applicationStop() is required for reloading javaSettings? Should I file a ticket? Thanks!, -Aaron
Comment by External U.
20633 | February 29, 2012 01:10:38 AM GMT
Hi Rupesh, This issue (a per-App setting not running on every request) is the same as CF-3916906 (another per-App setting not running on every request). Since CF-3916906 is being fixed, can this ticket also please be fixed in the same manner? Thanks!, -Aaron
Comment by External U.
20634 | September 11, 2015 03:44:17 PM GMT
"We can't go on adding a new function for every setting that goes in the application.cfc" No, but you could add methods to the application scope class. CFML is an OO language these days; you're allowed to take an OO approach with your own solutions too. This'd be a bit crap, but you could even have a single method which is reloadSetting(String settingname) (or something along those lines). If there's a real-world constraint preventing settings being reloaded in a piecemeal fashion, then so be it. but excuses like "We can't go on adding a new function for every setting that goes in the application.cfc" demonstrate a lack of will to be helpful, and ingenuity to arrive at inventive solutions.
Comment by External U.
20635 | September 11, 2015 03:59:21 PM GMT
+1 Vote must be between 25 and 4000 charactersVote must be between 25 and 4000 characters
Vote by External U.
20637 | September 11, 2015 04:00:30 PM GMT
Hi Adam, I just realized Rupesh never replied. And, I'm guessing he never will (since he's now on another Adobe team). So, I've filed CF-4199432, to document which per-app settings are read on each request. Thanks!, -Aaron
Comment by Aaron N.
20636 | August 06, 2017 07:58:19 AM GMT