Antwort: Re: JaxWsProxyFactoryBean & wsa:soapaction [Virus checked]

[ja...@external.t-mobile.at]

problem in email has also a solution - to add service attribute to jaxws 
bean definition
e.g.

        <jaxws:endpoint
                id="endpoint-org.test.HelloPort"
                implementor="#org.test.HelloPort"
                implementorClass="org.test.HelloPort"
                address="/xasddsd" 
                wsdlLocation="classpath:xxx.wsdl"
                serviceName="serNs:createActivateContractResponseService"
                xmlns:serNs="http://blablba/createActivateContract/"
        />




Adrian C <ad...@gmail.com> 
06/12/2008 13:38
Bitte antworten an
users@cxf.apache.org


An
users@cxf.apache.org
Kopie

Thema
Re: JaxWsProxyFactoryBean & wsa:soapaction  [Virus checked]








after playing around with this I found that if I turned off ws-addressing
then I had no SOAPAction set either - which let me to this post

http://www.nabble.com/empty-soap-action-using-JAXWS-JAXB---Virus-checked--tp17100357p17100357.html


work around is to set the endpoint also in the JaxWsProxyFactoryBean 


Adrian C wrote:
> 
> I seem to be having a problem with JaxWsProxyFactoryBean and
> wsa:soapaction.
> 
> When I turn on WSA in my consumer CXF seems to generate the incorrect
> wsa:soapaction if I set the serviceName & wsdlLoction. It seems to
> concatenate the request namespace, the service name and the name of the
> rootelement of the request instead of using the SOAPAction annotation!
> Anyone ideas how to workaround this?
> 

-- 
View this message in context: 
http://www.nabble.com/JaxWsProxyFactoryBean---wsa%3Asoapaction-tp17797653p17797737.html

Sent from the cxf-user mailing list archive at Nabble.com.