cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CXF-2214) When using Hibernate with dOSGi, CXF gives java.lang.ClassNotFoundException: com.bea.xml.stream.MXParserFactory
Date Mon, 26 Oct 2009 20:18:59 GMT

     [ https://issues.apache.org/jira/browse/CXF-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Kulp resolved CXF-2214.
------------------------------

       Resolution: Invalid
    Fix Version/s: Invalid


There really isn't anything that WE can do about this.   This is technically a bug in the
xml stream 1.0.1 bundle in that it's not properly looking for an implementation of stax (the
woodstox bundle, for example) or you haven't provided a bundle for com.bea.xml.stream.MXParserFactory.

I'd SUGGEST using the ServiceMix stax bundle:
http://repo2.maven.org/maven2/org/apache/servicemix/specs/org.apache.servicemix.specs.stax-api-1.0/
as that has an OSGi enabled factory finder that should find proper Stax implementations (such
as the recommend woodstox).



> When using Hibernate with dOSGi, CXF gives java.lang.ClassNotFoundException: com.bea.xml.stream.MXParserFactory
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-2214
>                 URL: https://issues.apache.org/jira/browse/CXF-2214
>             Project: CXF
>          Issue Type: Bug
>          Components: Distributed-OSGi
>    Affects Versions: 2.2.1
>         Environment: Sun Java 1.6.0_10 x64
> Vista x64
> Equinox 3.5
> Hibernate 3.3.1 (and therefore StaX 1.0.1)
>            Reporter: Markus Thielen
>             Fix For: Invalid
>
>
> When using Hibernate 3.3.1 together with dOSGi i get an exception when i query a webservice
with ?wsdl.
> The browser results in a blank page.
> EXCEPTION 
> 	javax.xml.stream.FactoryConfigurationError: Provider com.bea.xml.stream.MXParserFactory
not found
> 	at javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java:72)
> 	at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:178)
> 	at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:92)
> 	at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:136)
> 	at org.apache.cxf.staxutils.StaxUtils.<clinit>(StaxUtils.java:78)
> 	at org.apache.cxf.transport.http.WSDLQueryHandler.writeResponse(WSDLQueryHandler.java:208)
> 	at org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:240)
> 	at org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:70)
> 	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:729)
> 	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:206)
> 	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> 	at org.mortbay.jetty.Server.handle(Server.java:324)
> 	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
> 	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:829)
> 	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513)
> 	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
> 	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
> 	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
> 	at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:488)
> WARN  org.mortbay.jetty  - Nested in javax.xml.stream.FactoryConfigurationError: Provider
com.bea.xml.stream.MXParserFactory not found:
> 	java.lang.ClassNotFoundException: com.bea.xml.stream.MXParserFactory
> 	at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:489)
> 	at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:405)
> 	at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:393)
> 	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
> 	at javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java:68)
> 	at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:178)
> 	at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:92)
> 	at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:136)
> 	at org.apache.cxf.staxutils.StaxUtils.<clinit>(StaxUtils.java:78)
> 	at org.apache.cxf.transport.http.WSDLQueryHandler.writeResponse(WSDLQueryHandler.java:208)
> 	at org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:240)
> 	at org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:70)
> 	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:729)
> 	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:206)
> 	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> 	at org.mortbay.jetty.Server.handle(Server.java:324)
> 	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
> 	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:829)
> 	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513)
> 	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
> 	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
> 	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
> 	at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:488)
> I have figured out that this bundle is the cause of the evil:
> com.springsource.javax.xml.stream-1.0.1.jar
> but i need it for having this bundle resolved:
> com.springsource.org.dom4j-1.6.1.jar
> that i need for having this bundle resolved:
> com.springsource.org.hibernate-3.3.1.GA.jar
> So i guess there is a problem between hibernate and CXF/dOSGi?
> Im dont have any more clues, would really appreciate any fix here.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message