Hi ,
Stanley: Thanks, by following steps you suggested I got the OutPut.
But I update the web reference on .NET side, it will flush out my changes. So this is very rudimentory solution for me.
How did you solve your problem?
Anne: I got your point. I will try to use WSDL first approach and will unwrapp the Arrays.
Amit
On 7/7/06, Stanley Stanev <[EMAIL PROTECTED]> wrote:
We changed one of the XML serialization attributes of the array ITEM
In the Reference.cs (generated proxy) we altered the individual response object (in the sample case we did FindAllCompaniesResponse)
There is an XmlArrayItemAttribute("item", IsNullable=false)
that we changed to:
XmlArrayItemAttribute("companies", IsNullable=false)
item ->companies
in your case companies should be something else...
enjoy,
Stanimir Stanev (Stanley)On 7/6/06, Amit Andhale <[EMAIL PROTECTED]> wrote:
Hi,
Thanks for prompt reply!
Yes! I do have "style=WRAPPED" in my WSDL.
I have not checked with "DOCUMENT" style. I will check it and post my reply
soon.
Could you please tell me what changes you have made on .NET side Proxy
class?
This is very important task for me. And for the first time I am working on
Axis web service.
Amit
On 7/6/06, Stanley Stanev <[EMAIL PROTECTED]> wrote:
>
>
> Amit,
>
> we have solved this by changing a bit the generated proxy classes on the
.NET side, not good as it requires a very small change, but no way you can
fix this, bad for Axis 1.x
>
> also, I bet you have in your WSDD style="wrapped" when you describe your
service
>
> can you try with style="document", what is the result? what is the SOAP in
this case?
>
> thanks,
>
> Stanley Stanev
>
>
> Amit Andhale wrote:
>
>
> Hi John,
> Did your problem get solved using Axis2 or XFire?
>
> Amit
>
>
> On 7/5/06, Amit Andhale <[EMAIL PROTECTED] > wrote:
> >
> > Thanks John! I also tried out removing ArrayMapping from WSDD. But issue
still persists.
> >
> >
> >
> > On 7/5/06, john andersen <[EMAIL PROTECTED] > wrote:
> > >
> > > I ran into the exact same issue with both Axis 1.4 and Axis 1.3 but I
used a gSOAP client instead of .NET - the array member tags were set to the
name of the enclosing array. This problem does not exist in Axis2. Unless
this is a valid way to represent an array in XML, this seems to be an Axis
1.3/1.4 issue.
> > >
> > > Can this be a configuration issue? I have added/removed ArrayMappings
in the wsdd and have no idea what else I can poke to alter this behavior.
> > >
> > >
> > >
> > >
> > >
> > > On 7/5/06, Amit Andhale <[EMAIL PROTECTED] > wrote:
> > >
> > >
> > >
> > > Hi Anne,
> > > I rebooted the server and redeployed the service.
> > > I am still getting the SOAP Response in following fashion,
> > >
> > >
> > > <OuterObject>
> > > <ArrayOfInnerObjects>
> > > <ArrayOfInnerObjects>....</ArrayOfInnerObjects>
# WRONG
> > > <ArrayOfInnerObjects>....</ArrayOfInnerObjects>
# WRONG
> > > </ArrayOfInnerObjects>
> > > </OuterObjects>
> > >
> > >
> > > Please find actual SOAP response below:
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]-- ---------------------------------------- Stanimir Stanev (Stanley) Senior Java Developer www.stanev.com ----------------------------------------
