Including wadi and its dependencies in the jetty configuration/classpath breaks
numerous bits of geronimo
---------------------------------------------------------------------------------------------------------
Key: GERONIMO-1578
URL: http://issues.apache.org/jira/browse/GERONIMO-1578
Project: Geronimo
Type: Bug
Components: web
Versions: 1.1
Reporter: David Jencks
Assigned to: David Jencks
Fix For: 1.1
Wadi and AMQ and lots of other stuff is currently included directly in the
jetty configuration classpath. This breaks use of derby and amq. The derby
problem can be seen by trying to run daytrader and configuring the db: the amq
derby 10.0 classes are used instead of geronimo's 10.1 classes.
While there might be other problems contributing to this, including wadi
directly in the jetty classpath is not an acceptable integration method in any
case, so I am removing it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
