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 Isuru Suriarachchi <is...@gmail.com> on 2011/01/17 10:18:38 UTC

Attaching the PortName to the name of the AxisService in JAX-WS services

Hi All,

Currently in the Axis2 JAX-WS implementation, a PortName is attached to the
name of the AxisService when the service is being deployed. Is there any
special reason for doing this? Isn't it wrong to do this? Here, the wsgen
tool generates only one port in the WSDL. But there can be more than one
port in a WSDL depending on the existing bindings. So if there's no special
reason, shall we remove this and keep the AxisService name equal to the WSDL
service name?

This is reported as an issue in [1].

Thanks,
~Isuru

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

-- 
Technical Lead,
WSO2 Inc. http://wso2.org/
Blog : http://isurues.wordpress.com/

Re: Attaching the PortName to the name of the AxisService in JAX-WS services

Posted by Isuru Suriarachchi <is...@gmail.com>.

Can we agree on this?

Thanks,
~Isuru

On Mon, Jan 17, 2011 at 2:48 PM, Isuru Suriarachchi <is...@gmail.com>wrote:

> Hi All,
>
> Currently in the Axis2 JAX-WS implementation, a PortName is attached to the
> name of the AxisService when the service is being deployed. Is there any
> special reason for doing this? Isn't it wrong to do this? Here, the wsgen
> tool generates only one port in the WSDL. But there can be more than one
> port in a WSDL depending on the existing bindings. So if there's no special
> reason, shall we remove this and keep the AxisService name equal to the WSDL
> service name?
>
> This is reported as an issue in [1].
>
> Thanks,
> ~Isuru
>
> [1] https://issues.apache.org/jira/browse/AXIS2-2477
>
> --
> Technical Lead,
> WSO2 Inc. http://wso2.org/
> Blog : http://isurues.wordpress.com/
>



-- 
Technical Lead,
WSO2 Inc. http://wso2.org/
Blog : http://isurues.wordpress.com/