You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Amila Suriarachchi <am...@gmail.com> on 2007/06/28 08:07:48 UTC

WSDL2java default stub generation.

hi all,
currently wsdl2java generate stubs for all the ports in all the services
unless user has restricted to generate the code for a particular service or
a particular port. As a result of this generated stub names are long and it
seems a lot of people don't happy with this.

For this problem paul has suggested a solution in [1].

For an example lets say we have two services like this,

   <service name="Service1">
        <port name="Port1" binding="Soap12"/>
        <port name="Port2" binding="Soap11"/>
    </service>
    <service name="Service2">
        <port name="Port1" binding="Soap12"/>
        <port name="Port2" binding="Soap11"/>
    </service>

for this currently we have

Service1Port1Stub.java
Service1Port2Stub.java
Service2Port1Stub.java
Service2Port2Stub.java

And the new proposal suggest to generate only
Service1Stub.java --> for Port1 in Service1
Service2Stub.java --> for Port1 in Service2

(here I assume it is reasonable to generate a Stub for each service although
it is not explicitly specified in the proposal)

the priority order for pick a port within the service is depends on the
ports binding type.
the order is Soap12, Soap11 and http.

And give a seperate -all option to generate code as in now if user requried.

Please comment on this. If someone dose not oppose I'll go ahead and do this
change.

thanks,
Amila.

[1] https://issues.apache.org/jira/browse/AXIS2-2831

-- 
Amila Suriarachchi,
WSO2 Inc.

Re: WSDL2java default stub generation.

Posted by Amila Suriarachchi <am...@gmail.com>.
On 7/1/07, Alexey Zavizionov <al...@exoplatform.com.ua> wrote:
>
> Hello,
> I think that by default should be generated all ports for all services.
> And with option you may choose which ports for wich services will be
> generated.


Sorry for late reply. Actually I had done this change before one day to your
reply.  Any way you can use -ap option.  The main problem lot of people
pointed out was the length of the generated classname.
this would confuse an new commer to an axis2.

thanks,
Amila.

Thanks,
> Alexey
>
> On 6/28/07, Amila Suriarachchi <am...@gmail.com> wrote:
> > hi all,
> > currently wsdl2java generate stubs for all the ports in all the services
> > unless user has restricted to generate the code for a particular service
> or
> > a particular port. As a result of this generated stub names are long and
> it
> > seems a lot of people don't happy with this.
> >
> > For this problem paul has suggested a solution in [1].
> >
> > For an example lets say we have two services like this,
> >
> >    <service name="Service1">
> >         <port name="Port1" binding="Soap12"/>
> >         <port name="Port2" binding="Soap11"/>
> >     </service>
> >     <service name="Service2">
> >         <port name="Port1" binding="Soap12"/>
> >         <port name="Port2" binding="Soap11"/>
> >     </service>
> >
> > for this currently we have
> >
> > Service1Port1Stub.java
> > Service1Port2Stub.java
> > Service2Port1Stub.java
> > Service2Port2Stub.java
> >
> > And the new proposal suggest to generate only
> > Service1Stub.java --> for Port1 in Service1
> > Service2Stub.java --> for Port1 in Service2
> >
> > (here I assume it is reasonable to generate a Stub for each service
> although
> > it is not explicitly specified in the proposal)
> >
> > the priority order for pick a port within the service is depends on the
> > ports binding type.
> > the order is Soap12, Soap11 and http.
> >
> > And give a seperate -all option to generate code as in now if user
> requried.
> >
> > Please comment on this. If someone dose not oppose I'll go ahead and do
> this
> > change.
> >
> > thanks,
> > Amila.
> >
> > [1] https://issues.apache.org/jira/browse/AXIS2-2831
> >
> > --
> > Amila Suriarachchi,
> > WSO2 Inc.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>


-- 
Amila Suriarachchi,
WSO2 Inc.

Re: WSDL2java default stub generation.

Posted by Alexey Zavizionov <al...@exoplatform.com.ua>.
Hello,
I think that by default should be generated all ports for all services.
And with option you may choose which ports for wich services will be generated.


Thanks,
Alexey

On 6/28/07, Amila Suriarachchi <am...@gmail.com> wrote:
> hi all,
> currently wsdl2java generate stubs for all the ports in all the services
> unless user has restricted to generate the code for a particular service or
> a particular port. As a result of this generated stub names are long and it
> seems a lot of people don't happy with this.
>
> For this problem paul has suggested a solution in [1].
>
> For an example lets say we have two services like this,
>
>    <service name="Service1">
>         <port name="Port1" binding="Soap12"/>
>         <port name="Port2" binding="Soap11"/>
>     </service>
>     <service name="Service2">
>         <port name="Port1" binding="Soap12"/>
>         <port name="Port2" binding="Soap11"/>
>     </service>
>
> for this currently we have
>
> Service1Port1Stub.java
> Service1Port2Stub.java
> Service2Port1Stub.java
> Service2Port2Stub.java
>
> And the new proposal suggest to generate only
> Service1Stub.java --> for Port1 in Service1
> Service2Stub.java --> for Port1 in Service2
>
> (here I assume it is reasonable to generate a Stub for each service although
> it is not explicitly specified in the proposal)
>
> the priority order for pick a port within the service is depends on the
> ports binding type.
> the order is Soap12, Soap11 and http.
>
> And give a seperate -all option to generate code as in now if user requried.
>
> Please comment on this. If someone dose not oppose I'll go ahead and do this
> change.
>
> thanks,
> Amila.
>
> [1] https://issues.apache.org/jira/browse/AXIS2-2831
>
> --
> Amila Suriarachchi,
> WSO2 Inc.

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org