Hi David, I think you're refering to the way the JAXWS MessageReceiver will reflects on the implementation class when the first message is received. If so, you are absolutely right. It is using a deprecated method in the DescriptionFactory and is only there to drive some unit testing.
What needs to be done is integrate the building of the JAXWS description hierachy (i.e. the annotation processing) into the Axis2 deployment processing. I think this needs to be done as some sort of pluggable mechanism in the Axis2 deployment processing. I think Roy Wood has been looking into doing that. Thanks, Jeff IBM Software Group - WebSphere Web Services Development Phone: 512-838-4587 or Tie Line 678-4587 Internet e-mail and Sametime ID: [EMAIL PROTECTED] Brian De Pradine <[EMAIL PROTECTED]> 09/18/2007 05:20 AM Please respond to axis-dev@ws.apache.org To axis-dev@ws.apache.org cc Subject Re: Axis2 Roadmap questions Jeff, In axis2 we will require some form of deploy-time processing of annotations. The current mechanism of lazily processing the annotations when the first message arrives for a JAX-WS web service will not be sufficient to support the new web service feature concept of JAX-WS 2.1. Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do it right the first time, where will you find the time to do it again? Jeff Barrett <[EMAIL PROTECTED]> wrote on 17/09/2007 19:30:40: > David, > > I think Geronimo does things differently. I think they process the DDs in > advance, then modify the annotation values (possibly in the > DescriptionBuilderComposite they create) based on the DDs, then persist > everything out. At application startup, they read in the persisted > information and build everythign up that way. > > Since they are already EE5 compliant (I believe), they must not need the > DD support to be in JAXWS. I don't think JSR-109 and associated DD > support is optional in EE5. > > After studying JSR-109, I think the approach of building the DBCs based on > the annotations then modifying those DBCs based on the Deployment > Descriptors is the best approach, as opposed to putting JSR-109 support > into JAXWS. > > Thanks, > Jeff > > IBM Software Group - WebSphere Web Services Development > Phone: 512-838-4587 or Tie Line 678-4587 > Internet e-mail and Sametime ID: [EMAIL PROTECTED] > > > > "David Illsley" <[EMAIL PROTECTED]> > 09/17/2007 12:47 PM > Please respond to > axis-dev@ws.apache.org > > > To > axis-dev@ws.apache.org > cc > > Subject > Re: Axis2 Roadmap questions > > > > > > > Jeff, > Presumably Geronimo will need 109 v2 support at some point, or is it > optional for EE5 and EE6? Maybe that support (if it exists) could be > used by anyone wanting it with Axis2... > David > > On 14/09/2007, Jeff Barrett <[EMAIL PROTECTED]> wrote: > > Hi Dims, > > > > I believe the deployment descriptor is defined by JSR-109, not by > JAX-WS. > > > > I could be wrong, but I don't think anyone was planning on adding > JSR-109 > > support (and thus DDs) into the JAXWS (and associated metadata) module. > > > > Thanks, > > Jeff > > > > IBM Software Group - WebSphere Web Services Development > > Phone: 512-838-4587 or Tie Line 678-4587 > > Internet e-mail and Sametime ID: [EMAIL PROTECTED] > > > > > > > > "Davanum Srinivas" <[EMAIL PROTECTED]> > > 09/14/2007 09:27 AM > > Please respond to > > axis-dev@ws.apache.org > > > > > > To > > axis-dev@ws.apache.org > > cc > > > > Subject > > Re: Axis2 Roadmap questions > > > > > > > > > > > > > > Brian, > > > > Quick question about 2.1. does it define a descriptor for deploying > > services? i remember seeing all the test cases in current trunk use > > the services.xml with jaxws messagereceiver. hence wondering.. > > > > thanks, > > dims > > > > On 9/14/07, Brian De Pradine <[EMAIL PROTECTED]> wrote: > > > > > > Hello, > > > > > > Yes, I am currently working on JAX-WS 2.1 support. It should be almost > > ready > > > to be moved across to the trunk, but I need to do some more testing > > first. I > > > will also have to start raising JIRAs for the remaining bits of work, > so > > > that others can join in the fun. > > > > > > Cheers > > > > > > Brian DePradine > > > Web Services Development > > > IBM Hursley > > > External +44 (0) 1962 816319 Internal 246319 > > > > > > If you can't find the time to do it right the first time, where will > > you > > > find the time to do it again? > > > > > > > > > Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote on 13/09/2007 > > 19:48:19: > > > > > > > > > > Yadav, Yogendra (IT) wrote: > > > > > Hi Axis2 developers, > > > > > > > > > > I am interested to know the axis2 roadmap, I could not find this > > > > > information on the Axis2 web site. I am particularly interested > in > > the > > > > > following: > > > > > 1. Support for Spring based configuration. > > > > > > > > We have some support but it can be improved radically if there's a > > need. > > > > What do you have in mind? > > > > > > > > > 2. Support for JAX-WS 2.1. > > > > > > > > In progress .. I'm not sure exactly where we are; Brian, are you > the > > one > > > > working on it? > > > > > > > > > 3. Jetty and/or Grizzly based HTTP transports for Axis2. > > > > > > > > There's a Jetty transport that was written for WSO2 WSAS which is > > > > available. I've never heard of Grizzly (except in Yellowstone ;-))! > > > Google > > > > tells me Grizzly must be https://grizzly.dev.java.net/. Sounds like > > > that's > > > > what we should be using instead of straight Jetty now? > > > > > > > > If you're looking for NIO with Jetty 6, then we have a > > better-than-Jetty > > > > NIO transport that's based on the HTTP Core project! That was > > developed > > > > for Synapse but its a raw HTTP transport for Axis2 and is now > > committed > > > > here. It'll be great to do a perf eval of that vs. Jetty 6 and see > > how > > > > they compare! The reason I said "better-than-Jetty" is because this > > > > transport does NIO for both reading and writing .. something that > > Synapse > > > > needed in order to scale well. > > > > > > > > > 4. If Axis2 will ever provide full duplex streaming support (I > can > > read > > > > > the input stream via XMLStreamReader in my handler class but > can't > > > write > > > > > to the output stream while processing XML events). > > > > > > > > It does provide full duplex streaming; it does that now for > generated > > ADB > > > > classes. This is done using OMSourcedElement .. which is basically > a > > way > > > > of deferring Java object -> XML serialization until its absolutely > > > > necessary. At that time, the Java object can straight write itself > to > > the > > > > XML stream. > > > > > > > > Note that it has to be done this way because its necessary for > Axis2 > > to > > > > write the Envelope element etc. before asking the application to > > write > > > out > > > > the payload. If the application wants to defer reading some of the > > input > > > > until it starts writing the output that's possible thru the same > > > > technique- you have an OMSourcedElement impl which hangs onto the > > > incoming > > > > message context to get at the incoming message too. > > > > > > > > Hope this helps, > > > > > > > > Sanjiva. > > > > -- > > > > Sanjiva Weerawarana, Ph.D. > > > > Founder & Director; Lanka Software Foundation; > > http://www.opensource.lk/ > > > > Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/ > > > > Member; Apache Software Foundation; http://www.apache.org/ > > > > Visiting Lecturer; University of Moratuwa; > http://www.cse.mrt.ac.lk/ > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: > > > [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > ________________________________ > > > > > > > > > > > > > > > Unless stated otherwise above: > > > IBM United Kingdom Limited - Registered in England and Wales with > > number > > > 741598. > > > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire > PO6 > > 3AU > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > Davanum Srinivas :: http://davanum.wordpress.com > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > David Illsley - IBM Web Services Development > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
