• 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
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Can we have more than one WSDL file for same service

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

I have created a stateless EJB and have exposed it as a webservice, note that i m using WSAD5.1 & WAS5.1 for development and deployment purposes.

My EJB remote interface contains two remote methods 1) displayMessage 2) getAccountBalance

Now the problem is that once we deployed this webservice successfully over WAS5.1, we gave the client single WSDL file having two operation , but the client wants two different WSDLs for different operations, so i manually broke down One WSDL into 2.

But, Though we got two different WSDLs but still have the same <port:location> tags, Not the client wants us to have different URLs for two different WSDLs.

Could you please help me to solve the same?

Any suggestion/advise would be a great help.

Thanks
Abhishek khandelwal
 
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Welcome to JavaRanch!

Originally posted by abhi khan:
Not the client wants us to have different URLs



I'm not aware of any trick that will let you split the endpoint interface over two endpoints (it really doesn't make any sense).

At this point I would abandon exposing the SLSB as a web service. Instead I would create two servlet-based endpoints, each with one operation. The servlets would then simply delegate any calls to the SLSB - both servlet-based endpoints can have there own URL.
reply
    Bookmark Topic Watch Topic
  • New Topic