'Allow unspecified fields' not working in WSDL for Document Refs in latest Designer?

, ,
1

Hi,

We have a document, IngestDetails, that is used by a number of services in our Web Service Descriptor. The document contains a number of fields, including in particular a privateInfo field which is a document reference to a PrivateInfo document. The privateInfo field is to allow additional as yet unknown data to be set, and has the ‘Allow unspecified fields’ flag set to true.

The problem is this. Previously the WSDL generated contained the following:
<xsd:complexType name=“PrivateInfo”>
xsd:sequence
<xsd:any processContents=“lax”/>
</xsd:sequence>
<xsd:anyAttribute processContents=“lax”/>
</xsd:complexType>

However, since upgrading to the latest Designer (8.2.1.0000) and Integration Server (8.2.1.0), the generated WSDL now contains this snippet instead:
[SIZE=2]

[/size][COLOR=black] <xsd:complexType name=“PrivateInfo”[SIZE=2][SIZE=2]>

[/size][/SIZE][/color][SIZE=2]

[/size][SIZE=2][SIZE=2] xsd:sequence

[/size][/SIZE][SIZE=2]

[/size][SIZE=2][SIZE=2] </xsd:sequence>

[/size][/SIZE] </xsd:complexType>

The ‘any’ field has been lost, making it difficult for our generated java client to access any contents of the PrivateInfo it receives.

Has anyone else come across this problem, or any ideas how to solve it?

Thanks,
Dan

2

Anyone?

3

Edit the generated XSD to add in the any declaration. Not the nicest approach perhaps but relying solely on generated XSDs, WSDLs, code is sometimes not doable/advisable. I think WSDL/XSD-first style of development is generally viewed as a better approach than generating those from code.

4

Thanks for the tip.
Dan