That is really odd. None of the xfire classes hardcode the woodstox
refence. Maybe it is in a parent classpath or something??
Also, why are you using the RI? It is awful, slow and buggy. You really
should use Woodstox :-)
- Dan
Adam Kramer wrote:
I have a deployed web service that whenever it attempts to generate
WSDL, generates and error that it is looking for the Woodstox
implementation of stax.
WSTX is not on the classpath, but the RI stax-dev-1.1.2 is. Below is
the stacktrace:
javax.xml.stream.FactoryConfigurationError: Provider
com.ctc.wstx.stax.WstxInputFactory not found
at javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java:72)
at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:120)
at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:92)
at
javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:136)
at org.codehaus.xfire.util.STAXUtils.<clinit>(STAXUtils.java:47)
at
org.codehaus.xfire.util.jdom.StaxBuilder.<init>(StaxBuilder.java:150)
at
org.codehaus.xfire.wsdl11.builder.AbstractWSDL.<clinit>(AbstractWSDL.java:50)
at
org.codehaus.xfire.wsdl11.builder.DefaultWSDLBuilderFactory.createWSDLBuilder(DefaultWSDLBuilderFactory.java:25)
.
.
.
Any idea why it won't find the BEA stax impl?
Adam
--
Dan Diephouse
Envoi Solutions
http://envoisolutions.com
http://netzooid.com/blog
