Hello:
I figured out why I had the problem and it is because in the latest version I had used axis java2wsdl to get the .wsdd and wsdl files and that contained element names to be in0, in1.

Wondering what should be done when the java2wsdl is invoked to print the parameter names as userId, password etc instead of in0, in1. Somehow both the wsdl and the deploy.wsdd containes in0, in1 instead of the field names of each element . Would appreciate if someone could give some pointers on this.

Thanks,
Ravi

Ravi Krishnamurthy wrote:
Could someone give some pointers on this.

Thanks,
Ravi
Ravi Krishnamurthy wrote:
Could someone give some pointers on this.

Thanks,
Ravi

Ravi Krishnamurthy wrote:
Hello;
I had published the same webservice in axis 1.2.1 ans now trying it out with axis 1.4

The wsdl in 1.2.1 says for a complex type as below in 1.2.1
<element name="connect">
   <complexType>
       <sequence>
           <element name="userId" type="xsd:string"/>
           <element name="password" type="xsd:string"/>
       </sequence>
  </complexType>
</element>

in 1.4 it shows as below:

<element name="connect">
   <complexType>
       <sequence>
           <element name="in0" type="xsd:string"/>
           <element name="in1" type="xsd:string"/>
       </sequence>
   </complexType>
</element>

What should be done in the service deployment to make sure the element name is shown as userId and not as in0, in1 etc

Thanks for your help,
regards,
Ravi


---------------------------------------------------------------------
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]




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

Reply via email to