1) I'm ready to commit spring support. I got a question on how to improve the receiver implemention, but its working for me. I just have an In / out receiver until I can get some feedback. Once I get a better receiver implementation, if possible, I was planning on writing the tests. I do have example code.
Should I commit the spring module? My idea is we can tweak the build once its in. One news item: I was able to eliminate the 2MB spring jar, with 4 smaller jars that add up to 500K.
2) XMLBeans is broken in the 1.0 release, but I believe Ajith just resolved the issue.
Comments?
Robert
http://www.braziloutsource.com/
On 5/15/06, Sanjiva Weerawarana <
[EMAIL PROTECTED]> wrote:
On Mon, 2006-05-15 at 09:58 +1200, Dennis Sosnoski wrote:
> What do people want to do about the next Axis2 release? I have some
> features I want to make sure I can get into the next release, but it
> makes a difference on how I handle things if that release is going to be
> a 1.0.1 at the end of May vs. a 1.1 sometime in July-August (for
> example). My own preference would probably be for a 1.0.1 release around
> the end of this month, given the number of problems that have been found
> (and many already fixed) in the 1.0 release.
Given that we haven't found any show stopper bugs I'd rather not rush a
1.0.1 right now.
I'd rather focus on a 1.1 in time for ApacheCon .. end of June. Key
things I'd like to see in it:
- unwrap support in codegen
- improve adb
- add direct serialization support to axiom for perf improvement
- "spring support"
- get Rajith's cluster support integrated
- wsdl 2.0 support (for the CR)
(And of course general improvement of docs and other stuff that make
people unhappy ..)
What else? Maybe that's too much already ..
Sanjiva.
