Well that explains that problem. If I use "anyType", I'll need some way to specify a deserializer for the element.
The actual deserializer is trivial, just return the MessageElement, but is there an easy way to map the deserializer to that element? Actually it would be ok to treat all "anyType" the same. I'd like to generate everything from the WSDL definition as part of our build process and not have to modify the resulting wsdd to add typeMapping entries. Sam > -----Original Message----- > From: Jeff Greif [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 15, 2004 6:18 PM > To: [EMAIL PROTECTED] > Subject: Re: Element with type="xsd:any" > > xsd:any is not a defined type. You probably mean xsd:anyType. > ----- Original Message ----- > From: "Samuel Solon" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, December 15, 2004 3:08 PM > Subject: Element with type="xsd:any" > > > I'm using WSDL to define messages that have one (or more) elements > containing arbitrary XML and I'm running into problems. > > I tried: > > <xsd:complexType name="AddContact"> > <xsd:sequence> > <xsd:element name="UserId" type="xsd:string"/> > <xsd:element name="AbookId" type="xsd:string"/> > <xsd:element name="Contact" type="xsd:any"/> > </xsd:sequence> > </xsd:complexType> > >
