JAXWS service name

[Benson Margulies <bi...@gmail.com>]

Service is launching as

Creating Service {http://smws.basistech.com/}RLPSharedMemoryImplService from
class com.basistech.smws.RLPSharedMemory

Even though the implementation class has an endpointInterface in the
@WebService. Shouldn't that cause it to be named after the SEI, not the
implementation?

This is configured from spring with a # reference to the implementation in a
jaxws:endpoint.

Re: JAXWS service name

[Daniel Kulp <dk...@apache.org>]

No, this is one of the bizzarre issues I have with the JWS/JAX-WS specs.    
The name of the Service and the port names in the service come from the 
concrete implementation class, not the SEI.    Since you cannot have the 
Service/Port without the concrete instance, that is where they come from.

To get them named differently, you need to add the appropriate attributes to 
the @WebService annotation of the Impl.

Dan


On Fri May 1 2009 9:08:04 am Benson Margulies wrote:
> Service is launching as
>
> Creating Service {http://smws.basistech.com/}RLPSharedMemoryImplService
> from class com.basistech.smws.RLPSharedMemory
>
> Even though the implementation class has an endpointInterface in the
> @WebService. Shouldn't that cause it to be named after the SEI, not the
> implementation?
>
> This is configured from spring with a # reference to the implementation in
> a jaxws:endpoint.

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog