You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by "Attharkar, Asmita" <aa...@telcordia.com> on 2008/07/18 22:51:27 UTC

javatowsdl and wsdl filename ant task

3 questions actually:

Question1: What is that attribute which can specify the wsdl file name if you don't want the service class's name as the default filenamce for generated approach? I am doing service class first and wsdl later approach.

Question2: Does the wsdl filename identifies the name of the service or the name attribute in services.xml specifies the name of the approach?

Question 3:

There are three things :
1. wsdl filename
2. Name of service published
3. Name of the class name which defines the service
Do they all need to be same? I want to have the classname different from the wsdl filename and name of service; name of service being same the wsdl file name.

Thanks Asmita

RE: javatowsdl and wsdl filename ant task

Posted by "Attharkar, Asmita" <aa...@telcordia.com>.
Hello Madhav,

I am looking only for ant task by which I can have separate wsdl file name

Thanks,
Asmita

________________________________
From: Madhav [mailto:rrmadhav@gmail.com]
Sent: Monday, July 21, 2008 3:52 AM
To: axis-user@ws.apache.org
Subject: Re: javatowsdl and wsdl filename ant task

as the output of command java2wsdl shows:

Usage: java2wsdl [options] -cn <fully qualified class name>

where [options] include:
  -o <output location>                    output directory
  -of <output file name>                  output file name for the WSDL
  -sn <service name>                      service name
......
......

You could provide service name and output wsdl file name independently.

Also, in services.xml you could define service name and the actual service class independently.

<serviceGroup>
    <service name="StatisticsService">
        <parameter name="ServiceClass">
            sample.service.StatisticsService
        </parameter>
        <operation name="getStats">
            <actionMapping>urn:getStats</actionMapping>
            <messageReceiver
                class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
        </operation>
    </service>
</serviceGroup>

In the above xml, you could provide any service class

Thanks,
Madhav

On Sat, Jul 19, 2008 at 2:21 AM, Attharkar, Asmita <aa...@telcordia.com>> wrote:

3 questions actually:



Question1: What is that attribute which can specify the wsdl file name if you don't want the service class's name as the default filenamce for generated approach? I am doing service class first and wsdl later approach.



Question2: Does the wsdl filename identifies the name of the service or the name attribute in services.xml specifies the name of the approach?



Question 3:



There are three things :

1. wsdl filename

2. Name of service published

3. Name of the class name which defines the service

Do they all need to be same? I want to have the classname different from the wsdl filename and name of service; name of service being same the wsdl file name.



Thanks Asmita



--
-Madhav

Re: javatowsdl and wsdl filename ant task

Posted by Madhav <rr...@gmail.com>.
as the output of command java2wsdl shows:

Usage: java2wsdl [options] -cn <fully qualified class name>

where [options] include:
  -o <output location>                    output directory
  -of <output file name>                  output file name for the WSDL
  -sn <service name>                      service name
......
......

You could provide service name and output wsdl file name independently.

Also, in services.xml you could define service name and the actual service
class independently.

<serviceGroup>
    <service name="StatisticsService">
        <parameter name="ServiceClass">
            sample.service.StatisticsService
        </parameter>
        <operation name="getStats">
            <actionMapping>urn:getStats</actionMapping>
            <messageReceiver

class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
        </operation>
    </service>
</serviceGroup>

In the above xml, you could provide any service class

Thanks,
Madhav


On Sat, Jul 19, 2008 at 2:21 AM, Attharkar, Asmita <aa...@telcordia.com>
wrote:

>  3 questions actually:
>
>
>
> *Question1:* What is that attribute which can specify the wsdl file name
> if you don't want the service class's name as the default filenamce for
> generated approach? I am doing service class first and wsdl later approach.
>
>
>
> *Question2:* Does the wsdl filename identifies the name of the service or
> the name attribute in services.xml specifies the name of the approach?
>
>
>
> *Question 3:*
>
>
>
> There are three things :
>
> 1. wsdl filename
>
> 2. Name of service published
>
> 3. Name of the class name which defines the service
>
> Do they all need to be same? I want to have the classname different from
> the wsdl filename and name of service; name of service being same the wsdl
> file name.
>
>
>
> Thanks Asmita
>



-- 
-Madhav