• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • paul wheaton
  • Jeanne Boyarsky
  • Ron McLeod
Sheriffs:
  • Paul Clapham
  • Liutauras Vilda
  • Devaka Cooray
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
Bartenders:

Decoupling service name with wsdl file name in JAX-WS

 
Greenhorn
Posts: 25
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All,

I am working on a project to migrate JAX-RPC web services to JAX-WS services. Following are the service details from JAX_RPC wsdl file.

<wsdl:service name="AuthenticationWebServiceService">

<wsdl:port binding="impl:AuthenticationWebServiceSoapBinding" name="AuthenticationWebService">

<wsdlsoap:address location="https://localhost:9080/SSIWebServices/services/AuthenticationWebService"/>

</wsdl:port>

</wsdl:service>

Here service name has got 2 'service' words in service name. When I change this web service to JAX-WS, it takes "wsdl:service name" attribute and creates location as "https://localhost:9445/SSIWebServices/services/AuthenticationWebServiceService". and the wsdl files as AuthenticationWebServiceService.wsdl.

The problem here is that in existing jax-rpc clients service name is consumed as AuthenticationWebServiceService but wsdl name is AuthenticationWebService.wsdl. Because of which the client does not recognize the service. Is there a way to decouple service name with wsdl name.


Thanks in advance.
Rajesh Srivastava
 
Nothing up my sleeve ... and ... presto! A tiny ad:
Smokeless wood heat with a rocket mass heater
https://woodheat.net
reply
    Bookmark Topic Watch Topic
  • New Topic