• 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Devaka Cooray
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Knute Snortum
  • Bear Bibeault
Saloon Keepers:
  • Ron McLeod
  • Tim Moores
  • Stephan van Hulst
  • Piet Souris
  • Ganesh Patekar
Bartenders:
  • Frits Walraven
  • Carey Brown
  • Tim Holloway

Generating WebService Problem

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,

I'm missing something very big when generating a web service either from WSAD or from the command line tool EJB2WebService. Here is the situation:

I create a stateless EJB (say HelloWorldEJB) with WSAD. I test the EJB and it works fine. I generate a WebService from Hi all,

I'm missing something really big when generating a web service either from WSAD Web Service wizard or from the EJB2WebService command line tool. Here is the situation:

- I can create a stateless EJB (let's say HelloWorldEJB) with WSAD. I test the EJB and it works fine.
- Then, I can wrap the session bean in a web service using the WSAD wizards. This creates a new web module (let's call it HelloWorldEJBRouter) that handles the parsing and routing of SOAP requests. I test this within WSAD and it still works great.
- But when I look into the generated module I can't see any binaries. I don't understand why it runs at all, the HelloWorldEJBRouter module only contains the WSDL file (twice in different places), but no servlets or classes.
- The result is exactly the same if I use the EJB2WebServices tool. It generates a new EAR file with the HelloWorldEJBRouter module, but again except for the WSDL files it�s empty.

According the documentation, it should at least include a router servlet pointing to com.ibm.ws.webserices.engine.transport.http.WebServicesServlet.

I'm desperate because I feel that I'm missing something really big (aircraft carrier size), but I cannot figure it out. Any help will be greatly appreciated.

Thanks
 
Ranch Hand
Posts: 548
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
ngel- Even thoug I haven't replicated your case but my problem http://www.coderanch.com/t/76195/Websphere/Unable-consume-AXIS-EJB-WEBSPHERE is similiar to yours. May be you can help. Please suggest ....
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!