Thanks Dan,
So should I should change the method signature to get(String,Element)?
I just want to confirm that if an element is defined as a simple type
(no matter what pattern is used to define it), the Java method signature
should specify a simple type, not an Element. I can do trial-and-error,
but it's time consuming to confirm all cases.
 

-----Original Message-----
From: Daniel Jemiolo [mailto:[EMAIL PROTECTED] 
Sent: Friday, January 05, 2007 5:11 PM
To: [email protected]
Subject: RE: wsdl2java

Vinh is right - they are equivalent - but Baseer is also right -
wsdl2java doesn't cover every possible XSD/WSDL possibility/equivalence
there is. 
There were just too many in too short a time. The WSDL conventions in
the reference manual are meant to clarify which things are
covered/preferred and which aren't.

Dan





"Baseer Khan \(bakhan\)" <[EMAIL PROTECTED]>
01/05/2007 07:29 PM
Please respond to
[email protected]


To
<[email protected]>
cc

Subject
RE: wsdl2java






I guess since String is a Standard Java Type for which Muse has a
serializer, the signature reflects it. The rule is that all
Non-recongnizable types will be shown as Element in the Java method
signature.


--Baseer 

-----Original Message-----
From: Vinh Nguyen (vinguye2) 
Sent: Friday, January 05, 2007 4:24 PM
To: [email protected]
Subject: wsdl2java

I have the following wsdl elements:
  <xs:element name="QueryArguments" type="tns:ObjectType"/>
  <xs:element name="GetRequest">
    <xs:complexType>
      <xs:sequence>
        <xs:element name="QueryName" type="xs:string"/>
        <xs:element ref="tns:QueryArguments" minOccurs="0"
maxOccurs="unbounded"/>
      </xs:sequence>
    </xs:complexType>
  </xs:element>

This generates the Java method signature:
  public Element get(String param0, Element param1) throws Exception()
 
But, if I change the wsdl slightly to:
  <xs:element name="QueryName" type="xs:string"/>
  <xs:element name="QueryArguments" type="tns:ObjectType"/>
  <xs:element name="GetRequest">
    <xs:complexType>
      <xs:sequence>
        <xs:element ref="tns:QueryName"/>
        <xs:element ref="tns:QueryArguments" minOccurs="0"
maxOccurs="unbounded"/>
      </xs:sequence>
    </xs:complexType>
  </xs:element>

It will generate a different Java method signature:
  public Element get(Element param0, Element param1) throws Exception()
 
My question is: Aren't both wsdl patterns the same for the QueryName
element?  If so, why are the generated methods different?
 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to