Title: Message
Sagar,
So you recieve dynamic WSDL's and then have to generate the service endpoint interface and implementation on your server, is this correct?
 
This is a little different than what I was talking about.  When generating the WSDL the param names are lost unless you specify the impl (must already exist with the methods and param names).
 
I believe that if using Wrapped Literal and the parameters are named in the WSDL that they are used in generating the interface and implementation.  WSDL2java seems to take the element name (for the complex type) and the individual element names that make up the complexType and concatenates them.
 
Takes the following the wsdl:

<element name="echoString">

<complexType>

    <sequence>

        <element name="inputMyString" type="xsd:string"/>

        <element name="inputMyName" type="xsd:string"/>

    </sequence>

</complexType>

 
and creates parameters as follows:
echoString(Sting echoStringInputMyString, String echoStringInputMyName)
 
 
Marcus
 
-----Original Message-----
From: Sagar Pidaparthi [mailto:[EMAIL PROTECTED]
Sent: Friday, October 08, 2004 8:55 AM
To: [EMAIL PROTECTED]
Subject: RE: Java2WSDL ant task not keeping method param names

Can you elaborate on this please. 

 

I face the same problem.  In a message earlier, I was told that I can see the parameter names if I compile my classes using debug and then wsdl2java will be able to get the parameter names. 

 

I run my wsdl2java on dynamically available wsdls from a running server.  I can't run my production system with debug jars.  So how do I get around this problem and get parameter names in my proxies?

 

The implementation class that you mention should be on my server, which in my case is the same class available in my jars.  Do I create a separate class? 

At the moment I delete the String "SOAPBindingSkeleton" from my server-config.wsdd file and restart my server, because there is no such file on my server.

 

Regards

 

Sagar

 

 

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, October 08, 2004 8:47 AM
To: [EMAIL PROTECTED]
Subject: RE: Java2WSDL ant task not keeping method param names

 

To have java2wsdl use the method parameter names you need to supply the implementation class.  It reads the param names from the implementation.

 

marcus

-----Original Message-----
From: Curt P. Stanton [mailto:[EMAIL PROTECTED]
Sent: Friday, October 08, 2004 7:47 AM
To: AxisList
Subject: Java2WSDL ant task not keeping method param names

I am using ant 1.6.1 in eclipse 3.0

 

Here is the task I am running

 

I have tried this with axis 1.1 and 1.2alpha

It seems that no matter what I try, I cannot get the method names to be supplied. 

I am not sure if it is no storing the debug info properly when compiling or if the java2wsdl task isn't reading it properly.

 

Any help would be greatly appreciated.

 

Thanks in advance,

Curt Stanton

 

   <target name="compile" depends="init" description="compile the source ">

      <!-- Compile the java code from ${src} into ${build} -->

      <javac srcdir="${src}" destdir="${build}" target="1.4" debug="true" />

   </target>

 

   <target name="all" depends="compile" description="generate the wsdl">

      <!-- Create the distribution directory -->

      <mkdir dir="${dist}" />

      <path id="axis.classpath">

         <fileset dir="${axis.home}/lib">

            <include name="**/*.jar" />

         </fileset>

      </path>

 

      <taskdef resource="axis-tasks.properties" classpathref="axis.classpath" />

 

      <axis-java2wsdl classname="${package}.${classname}"

                      location="${location}"

                      namespace="${namespace}"

                      output="${dist}/${outputfile}"

                      style="wrapped"

                               use="literal">

         <mapping namespace="${namespace}" package="${package}" />

         <classpath>

            <pathelement path="${build}" />

         </classpath>

      </axis-java2wsdl>

   </target>

Reply via email to