Hi,
I have a webservice operation response (rpc/lit) with multiple parts, But
the second part of the response can be null. The wsld2java generates wrapper
class with XXXResponse where XXX is the operation name. But the generated
Wrapper throws exception when any message part is null while seriali
Hi,
I have a rpc/literal webservice with multiple parameters in its response. It
is possible that one of the parameter can be null i.e. the expected soap
response is but the ADB Wrapper generated by
wsdl2java tool throws exception while serializing it. If I wrap both the
parameters myself in a xx
I am in a process of migrating to Axis2 with ADB binding from axis1.
Basically I have a rpc/literal Web Service operation Response with multiple
parts in it. Of this one of the message part itself can be null. The message
definition looks likes this
In the above exampl
Hi,
Is it possible to expose a rpc/literal webxservice in unWrapped manner as
with doc?. The reason I am asking this question is, I have a webservice with
operation response having multiple parts in it. But one of the part is
nillable i.e, it can be null and so the respose should be
xsi:nillable="
t modified this
to return the xsi:nul="true" instead of throwing null it works fine. can
some one let me know how to get around this. Is there any option to specify
nil=true for the message parts?
Regards,
Krishna
krishna.arani wrote:
>
> Hi,
> The last message was not gett
Hi,
The last message was not getting posted to mailing list so I again posting
again. sorry If it causes any problem.
In my rpc/literal style webservice, I have a element with
multiple parts in it. One of the part can be nullable. The problem is the
generated ADB from wsdl2java throws an except
Hi,
In my rpc/literal style webservice, I have a element with
multiple parts in it. One of the part can be nullable. The problem is the
generated ADB from wsdl2java throws an exception if the part is null while
serialising to xml.
here the "entity" can be null.
