One common way is to eliminate your overloaded operations entirely and
send a complextType as the single parameter to your new operation. Then
model the optionality in the complexType:
I've taken the liberty to partition your example into 2 parts that make
more sense to me. To me the modify o
Hi all,
I am in the process of exposing an existing service as a
Doc/Lit Wrapped Service. I know that Doc/Lit Wrapped does not support method
name overloading, so i am left with the task of trying to resolve it for my
services. I was just wondering if there was any industry-standard '
My web service has overloaded methods like:
MyObject test1(String s1, String s2, MyObject obj);
MyObject[] test1(String s1, String s2, MyObject[]
obj);
But Axis 1.1 Beta seems to get confused on which
method to invoke on my web service. If my client
(running Apache SOAP) makes a call to the fir
I'm converting our application from Apache SOAP to
Apache Axis and am having trouble getting Axis 1.1
beta to invoke the proper overloaded method of my web
service. I have 2 methods with the same name but with
different signatures. They both take 3 arguments, the
first two of which are st
