My WSDL is RPC/literal. What I did just now I rewrote the WSDL to
document/literal style and it's working.
Examining carefully the two different SOAP messages in case of RPC style the
SOAPAction=""
which was caused by the fact that in WSDL file the soapAction was not
defined in:
Now I have http
On 8/3/11 2:30 PM, Claus Ibsen wrote:
On Tue, Aug 2, 2011 at 2:03 PM, Kovacs Zsolt wrote:
I'm still fighting with this java.lang.NullPointerException: MEP not found
problem. The only difference I have with other
WSDL documents is the soap binding type is RPC.
CXF doesn't support RPC/encod
On Tue, Aug 2, 2011 at 2:03 PM, Kovacs Zsolt wrote:
> I'm still fighting with this java.lang.NullPointerException: MEP not found
> problem. The only difference I have with other
> WSDL documents is the soap binding type is RPC.
>
If I recall then Apache CXF does not support the RPC style? But I
Rem: I use SOAPui for client side.
On Mon, Jul 25, 2011 at 1:20 PM, Kovacs Zsolt wrote:
>
> I tried to set useSoapEnvelope="true" but I got the same error, and if
> useJBIwrapper="true"
> the error message is org.apache.cxf.interceptor.Fault: Operation not bound
> on this message
>
> Thanks, Zsol
I tried to set useSoapEnvelope="true" but I got the same error, and if
useJBIwrapper="true"
the error message is org.apache.cxf.interceptor.Fault: Operation not bound
on this message
Thanks, Zsolt
On Mon, Jul 25, 2011 at 1:08 PM, Ashwin Karpe wrote:
> Hi,
>
> You have both useJBIwrapper and use
Hi,
You have both useJBIwrapper and useSoapEnvelope set to false. Shouldn't one
of them be true?
Cheers,
Ashwin...
-
-
Ashwin Karpe
Apache Camel Committer & Sr Principal Consultant
FUSESource (a Progress Software Corporation subsidiary
