Status/Resolution/Reason: Closed/Withdrawn/CannotReproduce
Reporter/Name(from Bugbase): Paul Cassar / Paul Cassar (Godwin Schembri)
Created: 12/05/2015
Components: Installation/Config, JEE Deployment
Versions: 11.0
Failure Type:
Found In Build/Fixed In Build: CF11_Final /
Priority/Frequency: Major / All users will encounter
Locale/System: English / Windows 7 SP1 64-bit
Vote Count: 0
Problem Description:
After deploying an EAR file generated through Coldfusion 11 Update 7 Admin, the Default ScriptSrc Directory
setting in Server Settings remains the same as path available on the server from where the EAR file was generated. This issue has been observed when Coldfusion is installed as an EAR file on JBoss Application Server.
Steps to Reproduce:
* Generate EAR file with a different context root from a properly configured and functional installation
* Deploy EAR file on a different system without exploding it (eg. using the JBoss Administration Console)
* Open Server Settings-> Settings -> Check Default ScriptSrc Directory setting
Actual Result:
The EAR file installation would be configured with the same Default ScriptSrc path as configured on the originating system even though the context root was changed.
Expected Result:
The Default ScriptSrc path on the newly deployed EAR file should reflect the proper context root.
Any Workarounds:
The Default ScriptSrc path must be changed to reflect new context root prior to EAR file generation.
Configure
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 4096245
External Customer Info:
External Company:
External Customer Name: Godwin Schembri
External Customer Email:
External Test Config: My Hardware and Environment details:
Windows Core i5
8GB RAM
Windows 7
Coldfusion 11 Update 7
JBoss EAP 6.3.0
Attachments:
- December 05, 2015 00:00:00: 1_2015-12-05_11_14_08-ColdFusion_Administrator.png
Comments: