1 Reply Latest reply: Nov 14, 2012 1:39 PM by Maurice G RSS

    wsdlcvt : undestanding and rectifying the error/warning

    915367
      When we run
      wsdlcvt -i <our.wsdl> -o <output file name>
      we get the following warnings.
      WSDLCVT:17
      WSDLCVT:22
      WSDLCVT:2

      Can somebody explain the meaning and implications of these messages that we get?
      Or point us to a location of documentation that would tell us about these warnings and how to rectify these?

      After doing tmloadrepos and wsloadcf and successfully starting the TMMETADATA and GWWS servers with the generated mif, fml32, xsds
      executing a tpcall on gives us the following int he ULOG

      actvenrl.13682.1.0: TRACE:at: { tpcall("somthingOp", 0x330fd0, 0, 0xffbfd8f4, 0xffbfd8f8, 0x0)
      GWWS.12805.11.0: TRACE:ms:SCO[4095] FSM State Transition: WAKEUP>Created
      GWWS.12805.11.0: TRACE:ms:SCO[4095] FSM State Transition: Outbound>DeTuxedoQ
      GWWS.12805.11.0: TRACE:ms:SCO[4095] FSM State Transition: OK>Tux2XML
      *GWWS.12805.11.0: TRACE:ms:SCO[4095] FSM State Transition: OBFail>Error*
      GWWS.12805.11.0: TRACE:ms:SCO[4095] FSM State Transition: Outbound>EnTuxedoQ
      GWWS.12805.11.0: TRACE:ms:SCO[4095] FSM State Transition: Default>PutToCallingQ
      GWWS.12805.11.0: TRACE:ms:SCO[4095] FSM State Transition: WAKEUP>EnTuxedoQ
      actvenrl.13682.1.0: TRACE:at: } tpcall = -1 [tperrno TPEOTYPE]
      GWWS.12805.11.0: TRACE:ms:SCO[4095] FSM State Transition: WAKEUP>ReadyDeletion
      GWWS.12805.11.0: TRACE:ms:SCO[4095] FSM State Transition: OK>Delete
      ourprocess.13682.1.0: Call failed: For Reason TPEOTYPE - type and/or subtype do not match buffer's or unknown


      WSDL Warning:
      file:///oracle/tuxedo11gR1/udataobj/salt/wsdl2mif.xsl; Line #1109; Column #18; WSDLCVT:17:WARNING: Ignore unsupported attribute "nillable" of element "RRQ_MessageID".
      file:///oracle/tuxedo11gR1/udataobj/salt/wsdl2mif.xsl; Line #1020; Column #19; WSDLCVT:22:WARNING: Tuxedo param "RRQ_MessageID" is based on "xsd:string" with additional restriction.
      ...
      file:///oracle/tuxedo11gR1/udataobj/salt/wsdl2mif.xsl; Line #1109; Column #18; WSDLCVT:17:WARNING: Ignore unsupported attribute "nillable" of element "RRQ_NumberOfAccounts".
      file:///oracle/tuxedo11gR1/udataobj/salt/wsdl2mif.xsl; Line #1020; Column #19; WSDLCVT:22:WARNING: Tuxedo param "RRQ_NumberOfAccounts" is based on "xsd:unsignedShort" with additional restriction.
      file:///oracle/tuxedo11gR1/udataobj/salt/wsdl2mif.xsl; Line #1109; Column #18; WSDLCVT:17:WARNING: Ignore unsupported attribute "nillable" of element "RRQ_AdditionalRequestDate1".
      file:///oracle/tuxedo11gR1/udataobj/salt/wsdl2mif.xsl; Line #1698; Column #21; WSDLCVT:2:WARNING: Element type "date" is mapped to Tuxedo FML32 string field. Please serialize/deserialize the value by yourself
      file:///oracle/tuxedo11gR1/udataobj/salt/wsdl2mif.xsl; Line #1020; Column #19; WSDLCVT:22:WARNING: Tuxedo param "RRQ_AdditionalRequestDate1" is based on "xsd:date" with additional restriction.



      wsdl file snippet:
      <definitions targetNamespace="http://www.somthing.com" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:reqns="http://www.something.Request.com" xmlns:resns="http://www.something.Response.com" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://www.something.com"
      xmlns:hdrns="http://somethingelse.com">
      <types>
      <xsd:schema attributeFormDefault="qualified" elementFormDefault="qualified"
      targetNamespace="http://somethingelse.com"
      xmlns:hdrns="http://somethingelse.com"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <xsd:import namespace="http://somethingelse.com" schemaLocation="OurHeader.xsd"/>
      </xsd:schema>
      <xsd:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://www.somthing.Request.com" xmlns:tns="http://www.something" xmlns:xsd="http://www
      .w3.org/2001/XMLSchema">

      <xsd:complexType abstract="false" block="#all" final="#all" mixed="false" name="ProgramInterface">
      <xsd:sequence>
      <xsd:element name="RRQ_something" nillable="false">
      <xsd:complexType mixed="false">
      <xsd:sequence>
      <xsd:element name="RRQ_somethingRequest" nillable="false">
      <xsd:complexType mixed="false">
      <xsd:sequence>

      ...

      <xsd:element name="RRQ_MessageID" nillable="false" minOccurs="0">
      <xsd:simpleType>
      <xsd:annotation>
      <xsd:appinfo source="http://www.ibm.com/software/htp/cics/annotations">#Wed Sep 30 09:34:32 EDT 2009
      com.ibm.cics.wsdl.properties.charlength=fixed
      com.ibm.cics.wsdl.properties.synchronized=false
      </xsd:appinfo>
      </xsd:annotation>
      <xsd:restriction base="xsd:string">
      <xsd:maxLength value="24"/>
      <xsd:whiteSpace value="collapse"/>
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>

      ...

      <xsd:element name="RRQ_NumberOfAccounts" nillable="false" minOccurs="0">
      <xsd:simpleType>
      <xsd:annotation>
      <xsd:appinfo source="http://www.ibm.com/software/htp/cics/annotations">#Wed Sep 30 09:34:32 EDT 2009
      com.ibm.cics.wsdl.properties.synchronized=false
      </xsd:appinfo>
      </xsd:annotation>
      <xsd:restriction base="xsd:unsignedShort">
      <xsd:maxInclusive value="99"/>
      <xsd:minInclusive value="0"/>
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>

      ...

      <xsd:element name="RRQ_AdditionalRequestDate1" nillable="false" minOccurs="0">
      <xsd:simpleType>
      <xsd:annotation>
      <xsd:appinfo source="http://www.ibm.com/software/htp/cics/annotations">#Fri Oct 24 11:35:13 EDT 2008
      com.ibm.cics.wsdl.properties.charlength=fixed
      com.ibm.cics.wsdl.properties.synchronized=false
      </xsd:appinfo>
      </xsd:annotation>
      <xsd:restriction base="xsd:date">
      <xsd:whiteSpace value="collapse"/>
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>

      ...

      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      <xsd:element name="RRQ_somthingOperation" nillable="false" type="tns:ProgramInterface"/>
      </xsd:schema>
      ....
      RESPONSE SCHEMA GOES HERE...
      ...


      Generated mif:
      ############
      # SERVICE: * somethingOperation
      ############
      service=somethingOperation
      tuxservice=somethingOp
      export=y
      servicetype=service
      servicemode=webservice
      inbuf=FML32
      outbuf=FML32
      errbuf=FML32
      ...
      param=RRQ_somethingOperation
      access=in
      paramschema=XSD_E:RRQ_somethingOperation@http://www.something.Request.com
      type=fml32
      (
      param=RRQ_something
      access=in
      paramschema=XSD_E:RRQ_something@http://www.something.Request.com
      type=fml32
      (
      param=RRQ_somethingRequest
      access=in
      paramschema=XSD_E:RRQ_somethingRequest@http://www.something.Request.com
      type=fml32
      (
      param=RRQ_MessageID
      access=in
      paramschema=XSD_E:RRQ_MessageID@http://www.something.Request.com
      type=string
      primetype=string

      ...

      param=RRQ_NumberOfAccounts
      access=in
      paramschema=XSD_E:RRQ_NumberOfAccounts@http://www.something.Request.com
      type=short
      primetype=unsignedShort


      param=RRQ_AdditionalRequestDate1
      access=in
      paramschema=XSD_E:RRQ_AdditionalRequestDate1@http://www.something.Request.com
      type=string
      primetype=date

      ...
        • 1. Re: wsdlcvt : undestanding and rectifying the error/warning
          Maurice G
          Hello,

          some of these warnings are there to indicate that there is no actual processing done on them by GWWS. For example for the unsigned short type restriction like you have (value between 0 and 99) no check will be done.

          About "nillable", the setting is ignored because the gateway again does not validate against it.

          But it doesn't mean things aren't supported.

          I could not find the documentation for the message catalogs, I will see to it that it gets fixed.

          What I suspect is happening is that the message may not be formatted properly going from the client program to GWWS, i.e. GWWS expects a certain formatting and is getting something else (it might be subtle... but it has to match). This is what the TPEOTYPE error means.

          Can you provide a print out of the fml32 buffer before you perform tpcall()? We can make sense of things if we also have the full MIF and/or WSDL as well. If that is not practical in these forums please get in touch with Customer Support and forward the information to them we'll take a look (make sure you indicate version of Tuxedo/SALT etc.). In the meantime you may want to carefully check the fml32 formatting against the MIF description and ensure that they match.

          Thank you,

          Maurice