Thanks David, I will try your approach. -----Original Message----- From: David Jencks [mailto:[EMAIL PROTECTED] Sent: Sunday, April 08, 2007 4:31 PM To: [EMAIL PROTECTED] Subject: Re: xs:any problem with WS-Enumerations
I think if you try to figure out what the accessor should be you might figure out why xmlbeans doesn't generate one. I think you want xmlObject.selectChildren and get the QName set something like this: itemList.selectChildren(ItemListType.type.qnameSetForWildcardElements ()); hope this helps david jencks On Apr 4, 2007, at 6:19 PM, Vinh Nguyen ((vinguye2)) wrote: > Hi all, > There is a problem with the way XmlBeans handles certain definitions > in the WS-Enumeration-2004_09.xsd. > > For example, the xsd contains this element: > > <xs:complexType name="ItemListType"> > <xs:sequence maxOccurs="unbounded"> > <xs:any namespace="##other" processContents="lax" minOccurs="0" > maxOccurs="unbounded"/> > </xs:sequence> > </xs:complexType> > > XmlBeans can't seem to handle the <xs:any namespace="##other"> > element. So it generates an ItemListType object that has no methods > to set or get a value(s) in it. The same behavior happens for all > other complexTypes that has the <xs:any namespace="##other"> element. > > As a result, for the Pull() operation, I am not able to pass back > enumeration results via the ItemListType object as needed in the > PullResponse. > > Any ideas how to get around this problem? Or do I need to edit this > xsd and remove the attributes in <xs:any> that XmlBeans can't handle? > I'd perfer to not edit the xsd since it comes from a standards > organization. > > --------------------------------------------------------------------- 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]
