I'm trying to migrate to JBoss 7.1.1 from 4.0.5.
In our application we use lot of symlinks to support CMS content
which is managed externally and to support some file bases caching.
Here is how the deployment looks like
Under "/deploy/jboss-4.0.5.GA/server/czen/deploy" we've our exploded
WAR directory release.war
Here release.war is a symlink to '/deploy/webapp/current' which in
turn is a symlink to an actual release folder like
'release-version-xyz' folder has the following structure
Here both Content and Cache folders are symlinks to
respectively. [note that symlinks are at multiple levels in the dir structure]
This deployment structure worked perfectly fine on JBoss 4.0.5 and
now I'm moving this app to JBoss 7.1.1 and here is the deployment
Under "/deploy/jboss-as-7.1.1.Final/czen/deployments" I've moved our
release.war as a symlink. Rest of the structure remains the same as
mentioned above. With this setup JBoss 7 start up/ application
initialization fails because it's not able to follow the symlink and
find a file that my application is trying to read at startup. I
looked over the documentation and forums to figure out a solution for
this but no luck.
Symlinks were supported in 4.0.5 through a configuration param in
context.xml under jbossweb-tomcat55.sar. In 7.X version the context.xml
support doesn't seem to be there. Following JIRAs are realted to this issue
Is there some workaround for this issue? Please let me know.