Thats impossible. Because the Axis Server didn´t expect wrapped methods.
We use unwrapped. The Problem is that AXIS always send an non empty
SOAP-Body. (It is hard Coded)
I guess thats a problem of AXIS 1.4.. I tried to create a dummyElement
called notifyPermissionCreationResponse. Than all work
Change your client setting to wrapped and everything should work fine.
On 4/23/07, Andreas Gabel <[EMAIL PROTECTED]> wrote:
On the server side we had document/literal configured. Which means the
method is not wrapped.
On the client side i have nothing configured, i think we also had
document/lit
On the server side we had document/literal configured. Which means the
method is not wrapped.
On the client side i have nothing configured, i think we also had
document/literal unwrapped.
How i can configure xfire-Client that i didn´t get this Exception?
Andreas
Tomek Sztelak schrieb:
Probab
Probably you have different use/style settings and client and server side.
On 4/23/07, Andreas Gabel <[EMAIL PROTECTED]> wrote:
Hey Guys,
i had a WS which runs with AXIS 1.4. As you can see from the parts of
WSDL the method is a void method. The service runs as document/literal
unwrapped.
I
Hey Guys,
i had a WS which runs with AXIS 1.4. As you can see from the parts of
WSDL the method is a void method. The service runs as document/literal
unwrapped.
If i create a xFire client i get an Exception!!!
Thats because Axis 1.4 send me not an empty SoapBody. The answer from
Axis look
