You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by Daniel Kulp <dk...@apache.org> on 2011/09/08 20:40:39 UTC
New saaj-impl bundle....
I just committed a new bundle for saaj-impl 1.3.9.
It's actually a LARGE change from the current 1.3.2 . One of the problems
with SAAJ is that it subclasses some classes that are internal to the Sun JDK
and thus doesn't run on the IBM JDK unless you pull in an additional library
(jaxp-ri).
HOWEVER, pulling in jax-ri, due to it's META-INF/services, cause other issues
of having different parsers used, etc... Thus, that solution sucks. That's
my main issue is that I keep getting the jaxp-ri parser (which is complete
crap) instead of woodstox
For the new version, I'm having all the "com.sun.*" stuff that it needs pulled
into the bundle as well (but not the META-INF/services stuff). Thus, the
bundle is self contained. It runs fine on the IBM JDK. It also runs fine on
the Sun JDK and doesn't require updating the jre.properties to export the
com.sun.org.apache.internal things.
The downside is the bundle is larger (2M instead of 300K). HOWEVER, it
doesn't require the 4.5M jaxp-ri bundle so there is a net gain.
Does anyone see any issues with this approach?
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Talend - http://www.talend.com
Re: New saaj-impl bundle....
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Dan,
it sounds good for me. The size of the bundle is not really a big deal
(largely less that "side" effects depending of the parser, etc).
+1
Regards
JB
On 09/08/2011 08:40 PM, Daniel Kulp wrote:
>
> I just committed a new bundle for saaj-impl 1.3.9.
>
> It's actually a LARGE change from the current 1.3.2 . One of the problems
> with SAAJ is that it subclasses some classes that are internal to the Sun JDK
> and thus doesn't run on the IBM JDK unless you pull in an additional library
> (jaxp-ri).
>
> HOWEVER, pulling in jax-ri, due to it's META-INF/services, cause other issues
> of having different parsers used, etc... Thus, that solution sucks. That's
> my main issue is that I keep getting the jaxp-ri parser (which is complete
> crap) instead of woodstox
>
> For the new version, I'm having all the "com.sun.*" stuff that it needs pulled
> into the bundle as well (but not the META-INF/services stuff). Thus, the
> bundle is self contained. It runs fine on the IBM JDK. It also runs fine on
> the Sun JDK and doesn't require updating the jre.properties to export the
> com.sun.org.apache.internal things.
>
> The downside is the bundle is larger (2M instead of 300K). HOWEVER, it
> doesn't require the 4.5M jaxp-ri bundle so there is a net gain.
>
> Does anyone see any issues with this approach?
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: SAAJ implementation in SM 4.4.2
Posted by Freeman Fang <fr...@gmail.com>.
Hi,
A quick question, did you change any default configuration from SMX 4.4.2?
－－－－－－－－－－－－－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://fusesource.com | http://www.redhat.com/
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: @Freeman小屋
On 2013-3-7, at 上午3:00, cajunesque wrote:
> Hi guys.
>
> This is my second post, and I write it only after a week of trying on my
> own...
> I am recently upgrading from SM 4.3.0 to 4.4.2 and notice a problem with
> SAAJ impl that I cannot solve.
>
> I have tried loading saaj-impl 1.3.9. (as well as previous version), yet no
> matter what I do, the factory finder never locates it. (ws discovery library
> in requires saaj to create soap envelopes). I am not using jaxm.properties,
> and the only jar in either my local mvn repo or system directory (or my
> cache, for that matter) with a META-INF/service file is the saaj-impl 1.3.9
> jar. This is the error I get:
> com.ms.wsdiscovery.xml.exception.WsDiscoveryXMLException: Unable to create
> new SOAP message: Provider
> com.sun.xml.messaging.saaj.soap.SAAJMetaFactoryImpl not found
>
> In fact, before I specifically set -D vm vars, SM was looking for the axis
> implementation, and could not find that (I have no dependency set to axis)
> and would similarly complain:
> com.ms.wsdiscovery.xml.exception.WsDiscoveryXMLException: Unable to create
> new SOAP message: Provider org.apache.axis2.saaj.SAAJMetaFactoryImpl not
> found
>
> I have attached my config files and the features file I am deploying.
> config.properties
> <http://servicemix.396122.n5.nabble.com/file/n5716044/config.properties>
> custom.properties
> <http://servicemix.396122.n5.nabble.com/file/n5716044/custom.properties>
> jre.properties
> <http://servicemix.396122.n5.nabble.com/file/n5716044/jre.properties>
> esb-proxies-1.9.5-features.xml
> <http://servicemix.396122.n5.nabble.com/file/n5716044/esb-proxies-1.9.5-features.xml>
>
> At runtime, here are the bundles loaded (even with just the first two, same
> problem):
> karaf@root> osgi:list -t 0 | grep -i saaj
> [ 86] [Active ] [ ] [ ] [ 10] Apache ServiceMix ::
> Specs :: SAAJ API 1.3 (1.9.0)
> [ 136] [Active ] [ ] [ ] [ 25] Apache ServiceMix ::
> Bundles :: saaj-impl (1.3.9.2)
> [ 200] [Active ] [ ] [ ] [ 60]
> wrap_mvn_javax.xml.soap_saaj-api_1.3.1 (0)
> [ 201] [Active ] [ ] [ ] [ 60]
> wrap_mvn_com.sun.xml.messaging.saaj_saaj-impl_1.3.4 (0)
>
> Strangely enough all this works fine in SM 4.3.0.
> What is the new SM doing differently? ANy help would be appreciated.
>
> Mark Bordelon
>
>
>
> --
> View this message in context: http://servicemix.396122.n5.nabble.com/New-saaj-impl-bundle-tp4783563p5716044.html
> Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
SAAJ implementation in SM 4.4.2
Posted by cajunesque <Ma...@LiveNation.com>.
Hi guys.
This is my second post, and I write it only after a week of trying on my
own...
I am recently upgrading from SM 4.3.0 to 4.4.2 and notice a problem with
SAAJ impl that I cannot solve.
I have tried loading saaj-impl 1.3.9. (as well as previous version), yet no
matter what I do, the factory finder never locates it. (ws discovery library
in requires saaj to create soap envelopes). I am not using jaxm.properties,
and the only jar in either my local mvn repo or system directory (or my
cache, for that matter) with a META-INF/service file is the saaj-impl 1.3.9
jar. This is the error I get:
com.ms.wsdiscovery.xml.exception.WsDiscoveryXMLException: Unable to create
new SOAP message: Provider
com.sun.xml.messaging.saaj.soap.SAAJMetaFactoryImpl not found
In fact, before I specifically set -D vm vars, SM was looking for the axis
implementation, and could not find that (I have no dependency set to axis)
and would similarly complain:
com.ms.wsdiscovery.xml.exception.WsDiscoveryXMLException: Unable to create
new SOAP message: Provider org.apache.axis2.saaj.SAAJMetaFactoryImpl not
found
I have attached my config files and the features file I am deploying.
config.properties
<http://servicemix.396122.n5.nabble.com/file/n5716044/config.properties>
custom.properties
<http://servicemix.396122.n5.nabble.com/file/n5716044/custom.properties>
jre.properties
<http://servicemix.396122.n5.nabble.com/file/n5716044/jre.properties>
esb-proxies-1.9.5-features.xml
<http://servicemix.396122.n5.nabble.com/file/n5716044/esb-proxies-1.9.5-features.xml>
At runtime, here are the bundles loaded (even with just the first two, same
problem):
karaf@root> osgi:list -t 0 | grep -i saaj
[ 86] [Active ] [ ] [ ] [ 10] Apache ServiceMix ::
Specs :: SAAJ API 1.3 (1.9.0)
[ 136] [Active ] [ ] [ ] [ 25] Apache ServiceMix ::
Bundles :: saaj-impl (1.3.9.2)
[ 200] [Active ] [ ] [ ] [ 60]
wrap_mvn_javax.xml.soap_saaj-api_1.3.1 (0)
[ 201] [Active ] [ ] [ ] [ 60]
wrap_mvn_com.sun.xml.messaging.saaj_saaj-impl_1.3.4 (0)
Strangely enough all this works fine in SM 4.3.0.
What is the new SM doing differently? ANy help would be appreciated.
Mark Bordelon
--
View this message in context: http://servicemix.396122.n5.nabble.com/New-saaj-impl-bundle-tp4783563p5716044.html
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.