Community
Participate
Working Groups
There are some fairly serious limitations in the current context configuration support. If a user provides META-INF/context.xml inside an archive, then this is copied to the relevant place in the configuration directory. Subsequent deployments of the application will use the context configuration from the configuration directory, which may not match the content of META-INF/context.xml. There is also a general issue that the configuration directory should be under the user's control and should not be updated by Gemini Web. Given the imminent release of Gemini Web, I'll document a known issue in the Virgo User Guide pointing to this bug and we can fix this bug in a subsequent release such as 1.1.1.
A partial workaround is to delete the copy of the file (e.g. $SERVER_HOME/config/[enginename]/[hostname]/[contextpath].xml) before redeploying the application.
This bug has an assignee, so changing status to ASSIGNED.
With migration to Tomcat 7 now we can introduce such switch. See TODO comment in org.eclipse.gemini.web.tomcat.internal.WebappConfigLocator.resolveWebappContextXml(String, String, File) method.
Created attachment 196074 [details] Patch
The patch looks good.
Change is tested, committed and pushed. Commit Id: 5f7547194bf220e32baf47086d44be39cce32004
Note 1.2.0.M05 may become 2.0.0.M01 if bug 346408 is implemented before the milestone.