I created a WSDL for an EJB, for it to be used as a WebService. I used the SOAP/HTTP protocol.
Now, what I understand ( I am a newbie to WebServices), that the endpoint for the WebService is the Remote Interface of the bean. That is, if I have a bean named myPackage.Sample and the various bean classes as:
Supply the Component Interface (implementing javax.ejb.EJBObject; note that this will automatically implement javax.rmi.Remote. Theoretically a component interface could serve as an endpoint interface)
I am using WSAD v5.1 to create the WebServices out of an EJB. And I am not able to set the Local Interface of my bean as the SEI for the WebService.
Also, using the IDE to create my WebServices, a whole bunch of files are created (eg: webservices.xml, webservicesclient.xml, etc). Though I know and have understaood what these files individually stand for, what I have not been able to relate is how all these components come together when a client initiates a request to the WebService.
Pardon me if this questions sounds very basic but I am new to the WebServices world. Using IDE, though reduces the work during development time, it really has not helped me to understand the concept of WebServices as a whole and the exact path of execution when a client calls a WebService using SOAP/HTTP.
Any pointers in this directions would be of great help (books, documents, etc).
Thanks in adavnce. Pratul Chakre
Joined: Aug 19, 2005
Originally posted by Pratul Chakre: Using IDE, though reduces the work during development time, it really has not helped me to understand the concept of WebServices as a whole and the exact path of execution when a client calls a WebService using SOAP/HTTP. Any pointers in this directions would be of great help (books, documents, etc).
A good IDE doesn�t necessarily help you learn a new area, but it should increase the productivity of the developer that is already competent in that area � this is a point that seems to be lost on some people. There are many technical endeavors that are much easier learned by getting your hands dirty � at least initially, and in my personal opinion Web Services is one of them. It doesn�t help that each vendor puts their own spin on things by changing deployment descriptor names, filenames, etc. from what they are in the initial specifications.
You may want to check out this topic (ignore the title � and yes the suggestions are heavily slanted toward SCDJWS preparation, so just pick what you like).