Looking at the tomcat 6.0 docs, the problem is that when using a
context.xml file the path attribute is ignored and the context path is
inferred purely from the filename/path of the context file.
For the path attribute the documentation states:
The value of this field must not be set except when statically defining
a Context in server.xml, as it will be inferred from the filenames used
for either the .xml context file or the docBase.
Thus on copying the nuxeo.xml template file in
templates/default/conf/Catalina/localhost it needs to be renamed to
${org.nuxeo.ecm.contextPath}.xml (minus any leading or trailing slashes).
In addition TomcatConfigurator with the hardcoded constant would need
modification too.
I guess a JIRA is in order....
Thanks,
Sean
On 13/11/10 21:45, Sean Radford wrote:
Hi,
Is it me, or is the org.nuxeo.ecm.contextPath variable options broken
in 5.4 on tomcat?
It changes the path attribute of the Context element in nuxeo.xml but
the webapp is still deployed under nuxeo.
Anyone else having the same problem?
Thanks,
Sean
--
Dr. Sean Radford, MBBS, MSc
http://www.tacola.com/
http://www.tacolaecm.com/
t: +44 (0)845 KEY HELP
t: +44 (0)845 539 4357
m: +44 (0)7802 24 24 86
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
To unsubscribe, go to http://lists.nuxeo.com/mailman/options/ecm
