Yeah, the difference is that it will use the soap 1.2 by default.
Not sure if the problem is on the xfire side or the servicemix-http
side, but there is a problem and I do not think that changing the
default soap version is a good solution (you can always do that on the
http endpoint deployment when needed).
Could you please raise a JIRA ?
If you ever reproduce the NPE, please put in the JIRA, it will
certainly help ...
Cheers,
Guillaume Nodet
On 4/29/06, Juergen Mayrbaeurl <[EMAIL PROTECTED]> wrote:
>
> You're right. The code in ProviderProcessor constructor doesn't have any
> problems and won't throw a NPE. The XFire based webservice that gets called
> by the servicemix-http component will throw the NPE. I don't know how to
> show you the misbehaviour, because I would have to provide an XFire based
> webservice.
>
> Anyway. Do you think it's a good idea to use an uninitialized attribute in
> the ProviderProcessor constructor?
>
> public ProviderProcessor(HttpEndpoint endpoint) {
> this.endpoint = endpoint;
> this.soapMarshaler = new SoapMarshaler(endpoint.isSoap());
> if (endpoint.isSoap() && "1.1".equals(endpoint.getSoapVersion())) {
> this.soapMarshaler.setSoapUri(SoapMarshaler.SOAP_11_URI);
> }
> this.jbiMarshaler = new JBIMarshaler();
> }
>
> What happens after
> 'this.soapMarshaler.setSoapUri(SoapMarshaler.SOAP_11_URI);' is called? Any
> difference in calling the webservice?
>
> Kind regards
> Juergen
> --
> View this message in context:
> http://www.nabble.com/servicemix-http-NPE-of-XFire-based-webservice-without-soap-version-t1526887.html#a4148377
> Sent from the ServiceMix - User forum at Nabble.com.
>
>
