Hi Dims, I can help out. Agreed on the point to keep it simple.
One of the points that was raised during the discussion thread was that having a services.xml will defeat the purpose of annotations. JSR181 has only a very basic set of annotations and if we write a services.xml then it makes the annotations completely redundent as the services.xml has all the information that needs to do the job. Thats why I took the hard way.
Specifies say Jsr181MessageReceiver as the MR
We can easily use the RPCMessageReceivers (or RPCInOnlyMR if @OneWay). So IMHO we don't need a special MR. But as Nick points out how can we know if this service is a JaxWsEndpoint or a Axis2Endpoint ?? thats why we suggested an additional axis2 annotation.
Don't want any listeners/notifications/peeking-thru-the-jars.
hehe ... As for the ASM scanner, it was to figure out which classes are marked with @WebServie Dims Either way count me in for support :) Regards, Rajith On 11/16/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
Rajith, I went thru the patch, and i went thru the current code in JAXWS. So it was a loaded question :) I think we need to define the simplest case. IMHO, the simplest deployment case should work exactly like our RPC*MessageReceiver. - User writes a services.xml - Specifies say Jsr181MessageReceiver as the MR - Specifies a class with a @WebService as the ServiceClass Don't want any listeners/notifications/peeking-thru-the-jars. basically KISS [1]. Do you have some cycles to help with this? thanks, dims [1] http://en.wikipedia.org/wiki/KISS_principle On 11/16/06, Rajith Attapattu <[EMAIL PROTECTED]> wrote: > hmm.... I haven't comitted the patch yet. > Nick can I start putting things together now ?? I hope you are done with the > refactoring you were planning to do. > > Dims, here is the basic idea. > The user can drop a jar file containing the class files marked with > @WebService and we use ASM to figure out which classes are marked and then > we load it. We use WSM to fill in the data and then we convert that to a > Axis2Service. > > the current concensus (after the Axis2 BoF at ApacheCon and mailing list > discussions) is to have some further annotations to help in the following > To mark wether it's a JAXWSEndpoint or Axis2Endpoint. > If JAXWsEndpoint then the MR is the JaxWsMessageReceiver and if not we do a > RPC(InOnly)MessageMessage reciver depending whether it's marked @Oneway or > not. > > We also have an idea to supplement the services.xml features by introducing > a few more annotations. [If it's not JAXWS endpoint] > For example @EnagageModule to leverage the module concept in Axis2 > @MessageReceiver if we want to use an Asyn MR .. etc > > Regards, > > Rajith > > Btw, I need to add a listener to the Deployment Engine to receive > notification if a file has been droped. This way I can move the code inside > JAX-WS module and keep the kernal module clean. Also this avoids us > rewriting the deployment code for monitoring the repo. > > > On 11/16/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > > > > Nick, Team, > > > > Hows does a end user deploy say "A service class with just @WebService > > annotation"? in current jaxws implemenation on svn HEAD? > > > > -- dims > > > > -- > > Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
