WSDLGen not generating usable WSDL

[Former Member]

Hello Experts.

WSDLGen on MII 12.1.5 Build 93 returns WSDL we can use to generate a Model, however same transaction on MII 12.1.8 Build 30 or MII 12.1.9 (Build 109) does not.

We followed this message without success.

WSDLGen Sample from 12.1.5 Build 93

- <s:complexType name="Row">
- <s:sequence id="RowSequence">
  <s:element maxOccurs="1" minOccurs="1" name="SO_HANDLE" type="s:string" /> 
  <s:element maxOccurs="1" minOccurs="1" name="WORK_CENTER" type="s:string" /> 
  <s:element maxOccurs="1" minOccurs="1" name="ITEM" type="s:string" /> 
  <s:element maxOccurs="1" minOccurs="1" name="CYCLE_TIME" type="s:string" /> 
  <s:element maxOccurs="1" minOccurs="1" name="PLAN_UPTIME" type="s:string" /> 
  <s:element maxOccurs="1" minOccurs="1" name="SUM_OF_CYCLES" type="s:double" /> 
  <s:element maxOccurs="1" minOccurs="1" name="NUM_TIRES" type="s:double" /> 
  <s:element maxOccurs="1" minOccurs="1" name="STATUS" type="s:string" /> 
  </s:sequence>
  </s:complexType>

WSDLGen Sample from 12.1.9 (Build 109)

- <s:complexType name="Row">
- <s:sequence id="RowSequence">
  <s:any maxOccurs="132" minOccurs="1" type="s:string" /> 
  </s:sequence>
  </s:complexType>

Regards

Amrik

[salvatore_castro]

Amrik,

Do you have a default XML set in the transaction property definition in one of the examples and not the other?

Also, have you tried assigning an XSD reference to the XML node?

Regards,

Sam

[Former Member]

Hi Sam,

The transaction is the same in both, though we tried assigning default XML without success.

We have not tried the XSD approach. Is there a blog or article on this as we are not familiar with this

Thanks

Amrik

[salvatore_castro]

Amrik,

I have confirmed with development that it was a bug in MII 12.1 SP9 and that it was fixed in SP9 patch 2.

Sam