Matt Raible wrote:
According to Carlos Sanchez, it looks like XWork depends on Xalan, but
doesn't specify it in its pom.xml. Thoughts?
http://issues.appfuse.org/browse/APF-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12576
Matt
Hi Matt,
I think this is a pretty common problem when users run a container with
a non-trivial application for the first time on their machine. It's
usually a container configuration problem.
AFAIK, XWork and others depend on JAXP, not xalan (javax.xml.transform.*).
In some container distributions, the container includes a JAXP
implementation (eg. xalan.jar). On some distributions, Sun's JAXP
implementation take precedence in the classpath.
Also, to complicate it, some distributions of the same container have
had different precedence of the JAXP implementation (I encountered this
with tomcat 5.5 distributions in Debian).
I'm not sure why the OP's Jetty instance on Windows was seeing the wrong
implementation, but as all the comments suggest it's related to
classpath precedence.
Anyway, I'm pretty sure XWork should not have xalan as a direct
dependency. Applications can include it directly, the container may
included it, or the administrator may need to install it depending on
the container, or maybe there's another JAXP implementation provided. I
suppose the pom could show it as an optional or provided dependency, but
that doesn't actually prevent the problem and it's not true (jaxp is
provided, not xalan). I've never investigated any further than that.
Yes, it's stupid and time-wasting.
cheers,
Jeromy Evans
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
