Attribute Order in generated WSDL

Question

Hi,
Is it possible to have autotype or servicegen maintain the order of my attributes as defined in my input schema? The WSDL file generated by the weblogic tasks is alphabitizing the input attributes and this is leading to an interoperatiblity issue with a .NET client that is calling my service.
My input schema is defined as follows:
<xs:element name="Response">
<xs:annotation>
<xs:documentation>Comment describing your root element</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="SessionID" type="xs:int"/>
<xs:element name="LoanRegistration" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="LoanID" type="LoanID_Type" />
<xs:element name="PropertyID" type="ID_Type" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="ContactID" type="ID_Type" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="RateLock" minOccurs="0"/>
<xs:element name="TradeAuthorizationComplete" minOccurs="0"/>
<xs:element name="GeneralUpdate" minOccurs="0"/>
<xs:element name="ApprovedByCreditCommittee" minOccurs="0"/>
<xs:element name="ApplicationIssued" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
This is translating into the following response as defined in the WSDL:
- <xsd:complexType name="Response">
- <xsd:sequence>
<xsd:element type="xsd:anyType" name="applicationIssued" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:anyType" name="approvedByCreditCommittee" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:anyType" name="generalUpdate" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="stns:LoanRegistration" name="loanRegistration" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:anyType" name="rateLock" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:int" name="sessionID" minOccurs="1" maxOccurs="1" />
<xsd:element type="xsd:anyType" name="tradeAuthorizationComplete" minOccurs="1" nillable="true" maxOccurs="1" />
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
Thanks much for any assistance!
Regards,
Michaelp

Answer 1

Hi
Which order should I use for the index? Someone said it should be (C2, C1)
because of the smaller cardinality of C2, but since we use C1 for an equi-join
(right word?) I wonder if (C1, C2) might be better.If substr(A.C2) is an option (does that really makes sense?) the index (C2, C1) will not be used by the query optimizer. Therefore, I see only (C1, C2) as option.
To complicate things there is also a column C3 in both tables, which will be
used for partitioning (so no index necessary?) and might be used in the
where-condition as well, if it helps.If the indexes are local when also C3 is specified partition pruning will be used in addition to the index lookup. This can only improve the performance.
HTH
Chris