You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Jesus Castillo <je...@gmail.com> on 2013/02/02 07:24:59 UTC
NPE on MessageModeInInterceptor when sending empty SOAPBody
I'm getting a NPE on MessageModeInInterceptor when sending a SOAP message
with empty body.
I'm using Dispatch with SOAPMessage and the Provider interface.
Everything is fine if the SOAPBody contains a payload but it fails when is
empty. This is the stack trace.
java.lang.NullPointerException
at
org.apache.cxf.jaxws.interceptors.MessageModeInInterceptor.handleMessage(MessageModeInInterceptor.java:71)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(JettyHTTPDestination.java:354)
at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:318)
at
org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:72)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1074)
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1010)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
at
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
at org.eclipse.jetty.server.Server.handle(Server.java:361)
at
org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:485)
at
org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:937)
at
org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:998)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:856)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240)
at
org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
at
org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:627)
at
org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:51)
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
at java.lang.Thread.run(Thread.java:662)
and that line is:
public void handleMessage(Message message) throws Fault {
if
(!bindingName.equals(message.getExchange().get(BindingOperationInfo.class)
.getBinding().getName())) {
It seems that the BindingOperationInfo is not found in the exchange.
This is the scenario:
CXF 2.7.0
NO wsdl. It's pure SOAP.
Soap 1.2 Binding although tested with 1.1. and is the same error.
Client side using Dispatch API with SOAPMessage.
Service side using Provider interface with SOAPMessage.
Regards,
Jesus.
--
View this message in context: http://cxf.547215.n5.nabble.com/NPE-on-MessageModeInInterceptor-when-sending-empty-SOAPBody-tp5722638.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: NPE on MessageModeInInterceptor when sending empty SOAPBody
Posted by Jesus Castillo <je...@gmail.com>.
Thanks Aki,
That works for me as this is still in development. I will await 2.7.4 then.
Rgds,
Jesus.
2013/2/15 Aki Yoshida-3 [via CXF] <ml...@n5.nabble.com>
> Hi Jesus,
> good to hear that it worked.
>
> Regarding the release schedule of 2.7.x, a new version is usually
> released in every 2 month or so.
> And version 2.7.3 was just released 10 days ago, I suppose it will
> take some time until 2.7.4 will be released.
>
> regards, aki
>
> 2013/2/14 Jesus Castillo <[hidden email]<http://user/SendEmail.jtp?type=node&node=5723253&i=0>>:
>
>
> > Hi Aki,
> >
> > Tested the fix today and it's working fine. Thanks!
> >
> > Any idea when it will be released?
> >
> > Jesus.
> >
> >
> > 2013/2/12 Aki Yoshida-3 [via CXF] <[hidden email]<http://user/SendEmail.jtp?type=node&node=5723253&i=1>>
>
> >
> >> Hi Jesus,
> >>
> >> The current 2.7.4-SNAPSHOT should contain the fix. Could you try it
> >> out with your scenario?
> >> Thanks.
> >>
> >> aki
> >>
> >> 2013/2/5 Jesus Castillo <[hidden email]<
> http://user/SendEmail.jtp?type=node&node=5723034&i=0>>:
> >>
> >> > Hi Aki,
> >> >
> >> > I opened a JIRA ticket.
> https://issues.apache.org/jira/browse/CXF-4812
> >> >
> >> > Re the provider, this is how the annotations look like:
> >> >
> >>
> >>
> >> ------------------------------
> >> If you reply to this email, your message will be added to the
> discussion
> >> below:
> >>
> >>
> http://cxf.547215.n5.nabble.com/NPE-on-MessageModeInInterceptor-when-sending-empty-SOAPBody-tp5722638p5723034.html
> >> To unsubscribe from NPE on MessageModeInInterceptor when sending empty
> >> SOAPBody, click here<
>
> >> .
> >> NAML<
> http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
> >>
> >
> >
> >
> >
> > --
> > View this message in context:
> http://cxf.547215.n5.nabble.com/NPE-on-MessageModeInInterceptor-when-sending-empty-SOAPBody-tp5722638p5723222.html
>
> > Sent from the cxf-user mailing list archive at Nabble.com.
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://cxf.547215.n5.nabble.com/NPE-on-MessageModeInInterceptor-when-sending-empty-SOAPBody-tp5722638p5723253.html
> To unsubscribe from NPE on MessageModeInInterceptor when sending empty
> SOAPBody, click here<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5722638&code=amVzdXMuYS5jYXN0aWxsb0BnbWFpbC5jb218NTcyMjYzOHwtNzE3NTA2NzE5>
> .
> NAML<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://cxf.547215.n5.nabble.com/NPE-on-MessageModeInInterceptor-when-sending-empty-SOAPBody-tp5722638p5723254.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: NPE on MessageModeInInterceptor when sending empty SOAPBody
Posted by Aki Yoshida <el...@gmail.com>.
Hi Jesus,
good to hear that it worked.
Regarding the release schedule of 2.7.x, a new version is usually
released in every 2 month or so.
And version 2.7.3 was just released 10 days ago, I suppose it will
take some time until 2.7.4 will be released.
regards, aki
2013/2/14 Jesus Castillo <je...@gmail.com>:
> Hi Aki,
>
> Tested the fix today and it's working fine. Thanks!
>
> Any idea when it will be released?
>
> Jesus.
>
>
> 2013/2/12 Aki Yoshida-3 [via CXF] <ml...@n5.nabble.com>
>
>> Hi Jesus,
>>
>> The current 2.7.4-SNAPSHOT should contain the fix. Could you try it
>> out with your scenario?
>> Thanks.
>>
>> aki
>>
>> 2013/2/5 Jesus Castillo <[hidden email]<http://user/SendEmail.jtp?type=node&node=5723034&i=0>>:
>>
>> > Hi Aki,
>> >
>> > I opened a JIRA ticket. https://issues.apache.org/jira/browse/CXF-4812
>> >
>> > Re the provider, this is how the annotations look like:
>> >
>>
>>
>> ------------------------------
>> If you reply to this email, your message will be added to the discussion
>> below:
>>
>> http://cxf.547215.n5.nabble.com/NPE-on-MessageModeInInterceptor-when-sending-empty-SOAPBody-tp5722638p5723034.html
>> To unsubscribe from NPE on MessageModeInInterceptor when sending empty
>> SOAPBody, click here<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5722638&code=amVzdXMuYS5jYXN0aWxsb0BnbWFpbC5jb218NTcyMjYzOHwtNzE3NTA2NzE5>
>> .
>> NAML<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>
>
>
>
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/NPE-on-MessageModeInInterceptor-when-sending-empty-SOAPBody-tp5722638p5723222.html
> Sent from the cxf-user mailing list archive at Nabble.com.
Re: NPE on MessageModeInInterceptor when sending empty SOAPBody
Posted by Jesus Castillo <je...@gmail.com>.
Hi Aki,
Tested the fix today and it's working fine. Thanks!
Any idea when it will be released?
Jesus.
2013/2/12 Aki Yoshida-3 [via CXF] <ml...@n5.nabble.com>
> Hi Jesus,
>
> The current 2.7.4-SNAPSHOT should contain the fix. Could you try it
> out with your scenario?
> Thanks.
>
> aki
>
> 2013/2/5 Jesus Castillo <[hidden email]<http://user/SendEmail.jtp?type=node&node=5723034&i=0>>:
>
> > Hi Aki,
> >
> > I opened a JIRA ticket. https://issues.apache.org/jira/browse/CXF-4812
> >
> > Re the provider, this is how the annotations look like:
> >
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://cxf.547215.n5.nabble.com/NPE-on-MessageModeInInterceptor-when-sending-empty-SOAPBody-tp5722638p5723034.html
> To unsubscribe from NPE on MessageModeInInterceptor when sending empty
> SOAPBody, click here<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5722638&code=amVzdXMuYS5jYXN0aWxsb0BnbWFpbC5jb218NTcyMjYzOHwtNzE3NTA2NzE5>
> .
> NAML<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://cxf.547215.n5.nabble.com/NPE-on-MessageModeInInterceptor-when-sending-empty-SOAPBody-tp5722638p5723222.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: NPE on MessageModeInInterceptor when sending empty SOAPBody
Posted by Aki Yoshida <el...@gmail.com>.
Hi Jesus,
The current 2.7.4-SNAPSHOT should contain the fix. Could you try it
out with your scenario?
Thanks.
aki
2013/2/5 Jesus Castillo <je...@gmail.com>:
> Hi Aki,
>
> I opened a JIRA ticket. https://issues.apache.org/jira/browse/CXF-4812
>
> Re the provider, this is how the annotations look like:
>
Re: NPE on MessageModeInInterceptor when sending empty SOAPBody
Posted by Jesus Castillo <je...@gmail.com>.
Hi Aki,
I opened a JIRA ticket. https://issues.apache.org/jira/browse/CXF-4812
Re the provider, this is how the annotations look like:
@WebServiceProvider(portName="myPort", serviceName="myService")
@ServiceMode(value=Service.Mode.MESSAGE)
public class MyProvider implements Provider<SOAPMessage> {
...
}
All I need is that the message reach this Provider.
Rgds,
Jesus.
2013/2/5 Aki Yoshida-3 [via CXF] <ml...@n5.nabble.com>
> Hi Jesus, all,
> I initially thought that an empty body might not be allowed, but BP
> 1.1 seems to allow an empty body.
>
> http://www.ws-i.org/profiles/basicprofile-1.1-2004-08-24.html#Bindings_and_Parts
>
> "Use of wsdl:message elements with zero parts is permitted in Document
> styles to permit operations that can send or receive envelopes with
> empty soap:Bodys."
>
> So, it looks like it definitely needs to be handled (not just avoiding
> NPE but also invoking the correct operation). Could you open a jira
> ticket for this?
>
> And in your particular case, do you have an annotated provider impl
> with multiple operations and you want the matching operation to be
> chosen based on the action header in the message? (this use case seems
> to correspond to what Dan mentioned).
>
> thanks.
> regards, aki
>
> 2013/2/4 Jesus Castillo <[hidden email]<http://user/SendEmail.jtp?type=node&node=5722752&i=0>>:
>
>
> > Just to clarify, this is a pure SOAP1.2 messaging system. So no WSDL is
> > needed or used. That section is for WSDL mainly.
> >
> > Jesus.
> >
> >
> >
> >
> > --
> > View this message in context:
> http://cxf.547215.n5.nabble.com/NPE-on-MessageModeInInterceptor-when-sending-empty-SOAPBody-tp5722638p5722727.html
>
> > Sent from the cxf-user mailing list archive at Nabble.com.
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://cxf.547215.n5.nabble.com/NPE-on-MessageModeInInterceptor-when-sending-empty-SOAPBody-tp5722638p5722752.html
> To unsubscribe from NPE on MessageModeInInterceptor when sending empty
> SOAPBody, click here<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5722638&code=amVzdXMuYS5jYXN0aWxsb0BnbWFpbC5jb218NTcyMjYzOHwtNzE3NTA2NzE5>
> .
> NAML<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://cxf.547215.n5.nabble.com/NPE-on-MessageModeInInterceptor-when-sending-empty-SOAPBody-tp5722638p5722769.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: NPE on MessageModeInInterceptor when sending empty SOAPBody
Posted by Aki Yoshida <el...@gmail.com>.
Hi Jesus, all,
I initially thought that an empty body might not be allowed, but BP
1.1 seems to allow an empty body.
http://www.ws-i.org/profiles/basicprofile-1.1-2004-08-24.html#Bindings_and_Parts
"Use of wsdl:message elements with zero parts is permitted in Document
styles to permit operations that can send or receive envelopes with
empty soap:Bodys."
So, it looks like it definitely needs to be handled (not just avoiding
NPE but also invoking the correct operation). Could you open a jira
ticket for this?
And in your particular case, do you have an annotated provider impl
with multiple operations and you want the matching operation to be
chosen based on the action header in the message? (this use case seems
to correspond to what Dan mentioned).
thanks.
regards, aki
2013/2/4 Jesus Castillo <je...@gmail.com>:
> Just to clarify, this is a pure SOAP1.2 messaging system. So no WSDL is
> needed or used. That section is for WSDL mainly.
>
> Jesus.
>
>
>
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/NPE-on-MessageModeInInterceptor-when-sending-empty-SOAPBody-tp5722638p5722727.html
> Sent from the cxf-user mailing list archive at Nabble.com.
Re: NPE on MessageModeInInterceptor when sending empty SOAPBody
Posted by Jesus Castillo <je...@gmail.com>.
Just to clarify, this is a pure SOAP1.2 messaging system. So no WSDL is
needed or used. That section is for WSDL mainly.
Jesus.
--
View this message in context: http://cxf.547215.n5.nabble.com/NPE-on-MessageModeInInterceptor-when-sending-empty-SOAPBody-tp5722638p5722727.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: NPE on MessageModeInInterceptor when sending empty SOAPBody
Posted by Daniel Kulp <dk...@apache.org>.
On Feb 4, 2013, at 11:27 AM, Glen Mazza <gm...@talend.com> wrote:
> Not having a SOAP body would seem to violate rule R2710 of the WS-I Basic Profile (http://www.ws-i.org/profiles/basicprofile-1.1.html#Operation_Signatures).
This was something that was updated in BP 2.0:
http://ws-i.org/Profiles/BasicProfile-2.0-2010-11-09.html#Operation_Signatures
which allows the body elements to be non-unique as long as the was:Action headers are unique.
Dan
>
> Glen
>
> On 02/04/2013 10:21 AM, Jesus Castillo wrote:
>> Hi Aki,
>>
>> the information about what service to invoke is not in the SOAP body but in
>> the SOAP headers.
>> Hence the request has an empty SOAP body.
>>
>> Rgds,
>>
>> Jesus.
>>
>>
>>
>> --
>> View this message in context: http://cxf.547215.n5.nabble.com/NPE-on-MessageModeInInterceptor-when-sending-empty-SOAPBody-tp5722638p5722719.html
>> Sent from the cxf-user mailing list archive at Nabble.com.
>
>
> --
> Glen Mazza
> Talend Community Coders - coders.talend.com
> blog: www.jroller.com/gmazza
>
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: NPE on MessageModeInInterceptor when sending empty SOAPBody
Posted by Glen Mazza <gm...@talend.com>.
Not having a SOAP body would seem to violate rule R2710 of the WS-I
Basic Profile
(http://www.ws-i.org/profiles/basicprofile-1.1.html#Operation_Signatures).
Glen
On 02/04/2013 10:21 AM, Jesus Castillo wrote:
> Hi Aki,
>
> the information about what service to invoke is not in the SOAP body but in
> the SOAP headers.
> Hence the request has an empty SOAP body.
>
> Rgds,
>
> Jesus.
>
>
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/NPE-on-MessageModeInInterceptor-when-sending-empty-SOAPBody-tp5722638p5722719.html
> Sent from the cxf-user mailing list archive at Nabble.com.
--
Glen Mazza
Talend Community Coders - coders.talend.com
blog: www.jroller.com/gmazza
Re: NPE on MessageModeInInterceptor when sending empty SOAPBody
Posted by Jesus Castillo <je...@gmail.com>.
Hi Aki,
the information about what service to invoke is not in the SOAP body but in
the SOAP headers.
Hence the request has an empty SOAP body.
Rgds,
Jesus.
--
View this message in context: http://cxf.547215.n5.nabble.com/NPE-on-MessageModeInInterceptor-when-sending-empty-SOAPBody-tp5722638p5722719.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: NPE on MessageModeInInterceptor when sending empty SOAPBody
Posted by Aki Yoshida <el...@gmail.com>.
Hi,
getting an NPE is bad and this needs to be fixed.
But my question is that you are expecting your target service to be
found and invoked with a null source in your scenario?
regards, aki
2013/2/2 Jesus Castillo <je...@gmail.com>:
> I'm getting a NPE on MessageModeInInterceptor when sending a SOAP message
> with empty body.
> I'm using Dispatch with SOAPMessage and the Provider interface.
>
> Everything is fine if the SOAPBody contains a payload but it fails when is
> empty. This is the stack trace.
> java.lang.NullPointerException
> at
> org.apache.cxf.jaxws.interceptors.MessageModeInInterceptor.handleMessage(MessageModeInInterceptor.java:71)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(JettyHTTPDestination.java:354)
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:318)
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:72)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1074)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1010)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
> at
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
> at org.eclipse.jetty.server.Server.handle(Server.java:361)
> at
> org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:485)
> at
> org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:937)
> at
> org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:998)
> at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:856)
> at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240)
> at
> org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
> at
> org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:627)
> at
> org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:51)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
> at java.lang.Thread.run(Thread.java:662)
>
>
> and that line is:
>
> public void handleMessage(Message message) throws Fault {
> if
> (!bindingName.equals(message.getExchange().get(BindingOperationInfo.class)
> .getBinding().getName())) {
>
>
> It seems that the BindingOperationInfo is not found in the exchange.
> This is the scenario:
>
> CXF 2.7.0
> NO wsdl. It's pure SOAP.
> Soap 1.2 Binding although tested with 1.1. and is the same error.
> Client side using Dispatch API with SOAPMessage.
> Service side using Provider interface with SOAPMessage.
>
> Regards,
>
> Jesus.
>
>
>
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/NPE-on-MessageModeInInterceptor-when-sending-empty-SOAPBody-tp5722638.html
> Sent from the cxf-user mailing list archive at Nabble.com.