Rajith/Dims, Sorry for the late response here. I'll do my best to be more responsive here so we can make progress on this issue.
As far as what's available for use right now, I'll let Jeff comment on the specifics since he's (and Roy) have been the ones pushing that work. I think the general structure is there, but there's still a last bit of refactoring required to be able to start using the metadata framework with Axis2 endpoints. I took a little bit and cleaned up the wiki the we'd started a while back to discuss the annotations that you'd mentioned below. Do you mind if we use that page to continue to define how this will work (what annotations will be introduced, how the deployment/processing will be kicked off)? http://wiki.apache.org/ws/FrontPage/Axis2/JAX-WS/JSR-181 It's a first pass at the information included below and a brief summary of our earlier discussions. We can use this to come to some consensus on the approach and then whoever is interested in doing the work can pick it up with adequate information. Regards, Nicholas Gallardo WebSphere - WebServices Development [EMAIL PROTECTED] Phone: 512-838-1182 Building: 901 / 5G-016 "Rajith Attapattu" <[EMAIL PROTECTED]> 11/16/2006 05:16 PM Please respond to [email protected] To [email protected], [EMAIL PROTECTED] cc Subject Re: [Axis2][jaxws] deploying jsr 181 service 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]
