The best way is to define it explicitly in your WSDL. This is an
example of a wrapped array of the bar element:
<element name="foobar">
<complexType>
<sequence>
<element name="foo" type="s:string"/>
<element name="arrayOfBar"/>
<complexType>
<sequence>
<element name="bar" type="s:string"
maxOccurs="unbounded"/>
</sequence>
</complexType>
</element>
</sequence>
</complexType>
</element>
Here's the same using an unwrapped array:
<element name="foobar">
<complexType>
<sequence>
<element name="foo" type="s:string"/>
<element name="bar" type="s:string" maxOccurs="unbounded"/>
</sequence>
</complexType>
</element>
Anne
On 8/2/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi anne,
Could you please tell me how to created a unWrapped array.
I am using axis 1.4 and using style="wrapped" use="literal"
Please looking fwd to your reply..
Thanks and Regards
Chandra
________________________________
From: Pradeep Reddy [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 02, 2006 4:29 AM
To: [email protected]
Subject: Re: Axis 1.3: Axis Interoperability issue with .net
Anne,
Thanks for the workaround.
I moved up ContactInfo to AssetContact and that worked.
If there is a bug, please let me know how I can esclate it.
Regards,
Pradeep
On 8/1/06, Anne Thomas Manes < [EMAIL PROTECTED] > wrote:
> I thought it was fixed in 1.4, but recent postings to the list make
> think that it wasn't.
> The bug is that Axis uses the same element name for both the array
> wrapping element and the array items. e.g.,
>
> <arrayofFoo>
> <arrayofFoo>...</arrayofFoo>
> <arrayofFoo>...</arrayofFoo>
> </arraryofFoo>
>
> instead of
>
> <arrayofFoo>
> <foo>...</foo>
> <foo>...</foo>
> </arrayofFoo>
>
> One way to work around this problem is to use unwrapped arrays.
>
> Anne
>
> On 7/31/06, Pradeep Reddy <[EMAIL PROTECTED]> wrote:
> > Anne,
> >
> > Thanks for your quick reply.
> >
> > I looked up JIRA and found this issue.
> > http://issues.apache.org/jira/browse/AXIS-2267
> > PublishedAsset is a subclass but I don't have any mixed type arrays. So
this
> > might not be the bug that you are referring to.
> > I applied the patch to this issue to the
> > org.apache.axis.encoding.SerializationContext and ran
into
> > the same issue again.
> >
> > Was this bug fixed in axis 1.4?
> >
> > Regards,
> > Pradeep
> >
> >
> > On 7/31/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
> > >
> > This is a bug in the way Axis 1.3 manages arrays.
> >
> >
> > On 7/31/06, Pradeep Reddy <[EMAIL PROTECTED]> wrote:
> > > Hi all,
> > > I am using Axis 1.3.
> > >
> > > My webservice is sending back a response that is similar to this for
> > couple
> > > of contained objects.
> > > ....
> > > <iv_contactInfo>
> > > ...
> > > <iv_contactInfo>
> > > ...
> > >
> > > However, .NET is expecting
> > > ..
> > > <ContactInfo>
> > > <iv_contactInfo>
> > > ....
> > > <iv_contactInfo>
> > > <ContactInfo>
> > > ..
> > > and returns null values for ContactInfo objects.
> > >
> > > ContactInfo is the type of object that client builds after recieving
the
> > > response.
> > > Please note that Contactinfo is returned as part of a larger object
> > > PublishedAsset.
> > >
> > > PublishedAsset
> > > -- ArrayOfAssetContact
> > > --AssetContact
> > > ---ContactInfo
> > >
> > > Has anyone seen this issue before? Any help would be greatly
appreciated.
> > >
> > > Thanks,
> > > Pradeep
> > >
> > >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
[EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
[EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
