You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by patsimon <pa...@heypatty.com> on 2012/10/08 07:48:57 UTC
Re: Classloading issue - Wrong SoapPartImpl getting picket up and
throwing HIERARCHY_REQUEST_ERR
How does one configure the endpoint with the property of
org.apache.cxf.binding.soap.messageFactoryClassName ?
I am attempting to do this with client (ie. <jaxws:client) but nothing
appears to be working
<jaxws:client id="blahPort"
serviceClass="org.open.BlahPort"
address="${endpoint}">
<jaxws:features>
<ref bean="gzipFeature"/>
<ref bean="fastInfosetFeature"/>
</jaxws:features>
<jaxws:properties>
<entry key="org.apache.cxf.binding.soap.messageFactoryClassName"
value="com.sun.xml.internal.messaging.saaj.soap.SOAPPartImpl" />
</jaxws:properties>
<jaxws:outInterceptors>
<ref bean="outPasswordInterceptor" />
</jaxws:outInterceptors>
</jaxws:client>
--
View this message in context: http://cxf.547215.n5.nabble.com/Classloading-issue-Wrong-SoapPartImpl-getting-picket-up-and-throwing-HIERARCHY-REQUEST-ERR-tp5627639p5715960.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: Classloading issue - Wrong SoapPartImpl getting picket up and throwing HIERARCHY_REQUEST_ERR
Posted by Freeman Fang <fr...@gmail.com>.
Yeah, this kind of issue is very hard to resolve in servlet container, but OSGi container could help you a lot from the lib versions co-exist perspective.
-------------
Freeman 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: http://weibo.com/u/1473905042
On 2012-10-12, at 下午1:51, patsimon wrote:
> Just to bring some closure to this issue (and help others who have the same
> problem), it look's like it's not possible to upgrade CXF with the version
> of AXIS2 mentioned. This is because they both have dependancies on the
> XmlSchema lib, but they both need different versions.. So I ended up using
> AXIS2 and JAxB for databindings..
>
>
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/Classloading-issue-Wrong-SoapPartImpl-getting-picket-up-and-throwing-HIERARCHY-REQUEST-ERR-tp5627639p5716451.html
> Sent from the cxf-user mailing list archive at Nabble.com.
Re: Classloading issue - Wrong SoapPartImpl getting picket up and
throwing HIERARCHY_REQUEST_ERR
Posted by patsimon <pa...@heypatty.com>.
Just to bring some closure to this issue (and help others who have the same
problem), it look's like it's not possible to upgrade CXF with the version
of AXIS2 mentioned. This is because they both have dependancies on the
XmlSchema lib, but they both need different versions.. So I ended up using
AXIS2 and JAxB for databindings..
--
View this message in context: http://cxf.547215.n5.nabble.com/Classloading-issue-Wrong-SoapPartImpl-getting-picket-up-and-throwing-HIERARCHY-REQUEST-ERR-tp5627639p5716451.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: Classloading issue - Wrong SoapPartImpl getting picket up and
throwing HIERARCHY_REQUEST_ERR
Posted by patsimon <pa...@heypatty.com>.
Thanks for the reply Dan.
I tried setting this in catalina.properties (like below) and it's still
getting into the axis2 code.
org.apache.cxf.binding.soap.messageFactoryClassName=com.sun.xml.internal.messaging.saaj.soap.SOAPPartImpl
I am using cxf 2.2.10 BTW and trying to avoid an upgrade if possible due all
the code that is pegged to libs that also need to move with CXF (WSS4J
etc..)
Any suggestions greatly appreciated.
--
View this message in context: http://cxf.547215.n5.nabble.com/Classloading-issue-Wrong-SoapPartImpl-getting-picket-up-and-throwing-HIERARCHY-REQUEST-ERR-tp5627639p5716045.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: Classloading issue - Wrong SoapPartImpl getting picket up and throwing HIERARCHY_REQUEST_ERR
Posted by Daniel Kulp <dk...@apache.org>.
Just checked the code this morning and unfortunately, this setting only currently works as a system property, not an endpoint property. :-(
Dan
On Oct 8, 2012, at 1:48 AM, patsimon <pa...@heypatty.com> wrote:
> How does one configure the endpoint with the property of
> org.apache.cxf.binding.soap.messageFactoryClassName ?
>
> I am attempting to do this with client (ie. <jaxws:client) but nothing
> appears to be working
>
> <jaxws:client id="blahPort"
> serviceClass="org.open.BlahPort"
> address="${endpoint}">
> <jaxws:features>
> <ref bean="gzipFeature"/>
>
> <ref bean="fastInfosetFeature"/>
>
> </jaxws:features>
> <jaxws:properties>
> <entry key="org.apache.cxf.binding.soap.messageFactoryClassName"
> value="com.sun.xml.internal.messaging.saaj.soap.SOAPPartImpl" />
> </jaxws:properties>
> <jaxws:outInterceptors>
> <ref bean="outPasswordInterceptor" />
> </jaxws:outInterceptors>
> </jaxws:client>
>
>
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/Classloading-issue-Wrong-SoapPartImpl-getting-picket-up-and-throwing-HIERARCHY-REQUEST-ERR-tp5627639p5715960.html
> Sent from the cxf-user mailing list archive at Nabble.com.
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com