Title:
Bug 82738:If you have per application mappings and either onSessionEnd() fires and creates components using those per application mappings, they fail as they are not respected
| View in TrackerStatus/Resolution/Reason: Closed/Withdrawn/
Reporter/Name(from Bugbase): Luis Majano / Luis Majano (Luis Majano)
Created: 04/24/2010
Components: General Server
Versions: 9.0
Failure Type: Unspecified
Found In Build/Fixed In Build: 0000 /
Priority/Frequency: Normal / Unknown
Locale/System: English / Platforms All
Vote Count: 5
Problem:
If you have per application mappings and either onSessionEnd() fires and creates components using those per application mappings, they fail as they are not respected.
Also, if you have event gateways defined that call CFCs inside your application and that CFC creates objects using the per application mappings, they also fail.
The errors is that the engine cannot find the component or interface.Once you add the mapping to the server administrator, the errors dissapear. However, this is not a good workaround. Per application mappings should be respected by all internal threads.
Method:
Have usage of onsessionEnd() or an event gateway that calls into your application under Application.cfc with some per application mappings to folders outside of our application root. Then on that calling template or CFC, create objects using these mappings.
Result:
per application mappings are not being respected when calls are made to the application via onSessionEnd() or via event gateways.
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3041368
External Customer Info:
External Company:
External Customer Name: Luis Majano
External Customer Email: 7A3D2E124563615A99201549
External Test Config: 04/24/2010Attachments:
Comments: