Status/Resolution/Reason: Closed/Fixed/
Reporter/Name(from Bugbase): Paul Cassar / Paul Cassar (Godwin Schembri)
Created: 10/29/2014
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 / Linux RH Enterprise 6
Vote Count: 0
Related Bugs:
CF-3972701 - Similar to
CF-3972701 - Similar to
Problem Description:
After deploying an EAR file generated through Coldfusion 11 Admin, the default Custom Tags Path 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 from a properly configured and functional installation
* Deploy EAR file on a different system without exploding it (eg. using the JBoss Administration Console)
* Open Extensions -> Custom Tags Page to see the default Custom Tags Path
Actual Result:
The EAR file installation would be configured with the same default Custom Tags Path as configured on the originating system.
Expected Result:
The default Custom Tags Path on the installed system should default to the same location ([cfusion_root]/WEB-INF/cfusion/CustomTags)
Any Workarounds:
The default Custom Tags Path can be configured programatically in Application.cfc relative to the coldfusion application path.
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3844825
External Customer Info:
External Company:
External Customer Name: gschembri
External Customer Email:
External Test Config: My Hardware and Environment details:
REHL 6.4
JBoss 6.2 EAP
Coldfusion 11 Enterprise
Attachments:
Comments: