Just a note to those of you who are using Maven 2: transitive
dependencies may not always work the same way from plugin to plugin!
"mvn eclipse:eclipse" put jaxb-impl-2.1.3.jar on my .classpath while
"mvn package" put jaxb-impl-2.1.2.jar into my war file. To resolve, I
simply called it out explicitly in my pom.xml.
<dependency>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-impl</artifactId>
<version>2.1.3</version>
<scope>compile</scope>
</dependency>
I dream of a build tool integrated with OSGi and/or the Java Module
System. May be a new Maven version, may be something else.
Cameron
On 5/15/07, Cameron Taggart <cameron.taggart_at_gmail.com> wrote:
> Thanks! I had jaxb-impl-2.1.2.jar in there, but switching to
> jaxb-impl-2.1.3 makes it work. I just checked and the correct one is
> shipped with jaxws-ri-2.1.1.
>
> Cameron
>
> On 5/15/07, Vivek Pandey <Vivek.Pandey_at_sun.com> wrote:
> > Its part of jaxb-impl.jar. you may like to put this jar in the classpath.
> >
> > -vivek.
> >
> > Cameron Taggart wrote:
> > > Same situation as before. Thinks are working from within Jetty
> > > launched from Eclipse, but not when deployed as a war to Tomcat. Any
> > > idea where com.sun.istack.XMLStreamReaderToContentHander is found?
> > >
> > > Stack Trace:
> > > java.lang.NoClassDefFoundError:
> > > com/sun/istack/XMLStreamReaderToContentHandler
> > > at
> > > com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:220)
> > > at
> > > com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:149)
> > > at
> > > com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:121)
> > > at
> > > com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:280)
> > >
> > > at
> > > com.sun.xml.ws.transport.http.HttpAdapter.decodePacket(HttpAdapter.java:207)
> > >
> > > at
> > > com.sun.xml.ws.transport.http.HttpAdapter.access$500(HttpAdapter.java:74)
> > > at
> > > com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:363)
> > >
> > > at
> > > com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:175)
> > > at
> > > com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:134)
> > >
> > > at
> > > com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doPost(WSServletDelegate.java:159)
> > >
> > > at
> > > com.sun.xml.ws.transport.http.servlet.WSSpringServlet.doPost(WSSpringServlet.java:52)
> > >
> > >
> > > I did find this posting with the same problem, but it didn't help me:
> > > http://forums.java.net/jive/thread.jspa?messageID=215484
> > >
> > > Cameron
> > >
> > > On 5/15/07, Cameron Taggart <cameron.taggart_at_gmail.com> wrote:
> > >> Resolved. Somehow that is the error you get when you try to deploy
> > >> the war without jaxws-spring-1.4.jar or xbean-spring-2.8.jar. My
> > >> mistake, but seriously not the most obvious error message. I was
> > >> launching Jetty from within Eclipse and those jars were on the
> > >> classpath.
> > >>
> > >> cheers,
> > >> Cameron
> > >>
> > >> On 5/15/07, Cameron Taggart <cameron.taggart_at_gmail.com> wrote:
> > >> > I was able to get JAX-WS RI 2.1.1 working with Spring 2.0.5 and Jetty
> > >> > 6.1.3. However, when I try to deploy to Tomcat 6.0.13 or 5.5.17 I get
> > >> > this strange error that I haven't been able to figure out. I'm also
> > >> > running Java 6.
> > >> >
> > >> > org.xml.sax.SAXParseException: White spaces are required between
> > >> > publicId and systemId.
> > >> >
> > >> > The invalid xml file is attached. It is based on the example here:
> > >> > https://jax-ws-commons.dev.java.net/spring/
> > >> >
> > >> > Any help is appreciated. Thanks,
> > >> >
> > >> > Cameron
> > >> >
> > >> >
> > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe_at_jax-ws.dev.java.net
> > > For additional commands, e-mail: users-help_at_jax-ws.dev.java.net
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe_at_jax-ws.dev.java.net
> > For additional commands, e-mail: users-help_at_jax-ws.dev.java.net
> >
> >
>