Try writing some calls to findClass in a servlet init method. The appearance here is that your jar is somehow escaping from the webapp classpath.
On Thu, Sep 4, 2008 at 12:21 PM, Martijn Brinkers <[EMAIL PROTECTED]> wrote: > I can get it working if I add the jar file that contains the JAXB > annotated classed to the jetty classpath: > > java > -Djetty.class.path="/home/martijn/workspace/mimesecure/mimesecure.jar" > -jar start.jar > > The war file it tries to deploy actually contains mimesecure.jar so it's > kind of strange that JAXB cannot find the classes if I do not use > jetty.class.path. > > I saw a similar posting > https://issues.apache.org/jira/browse/GERONIMO-3793?page=com.atlassian.jira.plu > but I do not know if the problem they report is the same problem I have. > > Any idea? > > Thanks, > > Martijn Brinkers > > > On Thu, 2008-09-04 at 15:58 +0200, Martijn Brinkers wrote: >> I get the follwoing exception when I deploy my web application in Jetty >> (6.1.11) and start a soap request (my web app acts as a soap client) >> >> Caused by: javax.xml.bind.JAXBException: >> mitm.application.mimesecure.ws.AdminDTO is not known to this context >> >> The strange thing is that my application works when deployed from >> Eclipse using run-jetty-run (an Eclipse Jetty plugin). I have tried all >> kinds of things but still no luck and I ran out of ideas. >> >> Any idea what's causing this? it must be some kind of classloading >> problem? >> >> Thanks, >> >> Martijn Brinkers >> >> PS. I use CXF 2.1 >> >> > >
