axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian De Pradine <>
Subject Re: Axis2 Roadmap questions
Date Fri, 14 Sep 2007 14:05:42 GMT

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.


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 <> 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 ;-))! 
> tells me Grizzly must be Sounds like 
> 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 
> needed in order to scale well.
> > 4. If Axis2 will ever provide full duplex streaming support (I can 
> > the input stream via XMLStreamReader in my handler class but can't 
> > to the output stream while processing XML events).
> It does provide full duplex streaming; it does that now for generated 
> 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 
> 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 
> 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 
> message context to get at the incoming message too.
> Hope this helps,
> Sanjiva.
> -- 
> Sanjiva Weerawarana, Ph.D.
> Founder & Director; Lanka Software Foundation;
> Founder, Chairman & CEO; WSO2, Inc.;
> Member; Apache Software Foundation;
> Visiting Lecturer; University of Moratuwa;
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

View raw message