[
https://issues.apache.org/activemq/browse/SMX4-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46527#action_46527
]
Guillaume Nodet commented on SMX4-138:
--------------------------------------
The problem is actually a bit tricky.
It actually come from SMX4KNL-119.
The reason is that the SAAJ jar imports some com.sun.org.apache packages that
come with the JAXP ri from sun (which is included in the sun JRE).
For some reason (I guess it's a bug in felix), the bundle resolution does not
always fail, but the wiring is not completely done, which means in our case,
the saaj-api was not wired to the saaj-impl bundle, thus leading to a
ClassNotFoundException on javax.xml.soap from saaj-impl bundle.
Anyway, reverting SMX4KNL-119 does the trick.
There is still one problem though. The saaj-impl bundle do require the jaxp-ri
packages (com.sun.org.apache.*) to be available. Currently, this means that
saaj only works on Sun JVMs.
> testSoapHandlerOsgi failed
> --------------------------
>
> Key: SMX4-138
> URL: https://issues.apache.org/activemq/browse/SMX4-138
> Project: ServiceMix 4
> Issue Type: Test
> Reporter: Freeman Fang
> Assignee: Freeman Fang
> Fix For: 4.0-m2
>
>
> get exception like
> at
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:497)
> Caused by: javax.xml.soap.SOAPException: Unable to create message factory for
> SOAP: Provider org.apache.axis2.saaj.MessageFactoryImpl not found
> at javax.xml.soap.MessageFactory.newInstance(MessageFactory.java:89)
> at
> org.apache.cxf.binding.soap.saaj.SAAJInInterceptor.handleMessage(SAAJInInterceptor.java:77)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
