Tom, Was talking about everyone else :) We need to come up with a consolidated list and negotiate on what we can do and when :)
Seriously, WSDL2.0 is not on my plate for 1.0 release. because Woden is not ready. their next milestone is in november. Unless you can help them push it along we can't deliver on that. native databinding support - Am all for it. rpc/encoded client support - Yes, if someone signs up for doing the work. WSDL generation from java code - Am all for WSDL 1.1. But *not* WSDL 2.0. thanks, dims On 9/30/05, Tom Jordahl <[EMAIL PROTECTED]> wrote: > Dims wrote: > > Key phrase is ------>>>>>>>> "until Axis2 is feature complete". Eran > > keeps asking for feedback and don't get any :( > > I gave him some (full WSDL 2.0 support)! :-) I didn't say he (or > Sanjiva) liked it. > > I would also like to see: > - native databinding support > - rpc/encoded client support (good enough to replace Axis1) > - WSDL generation (1.1 and 2.0) from Java code. > > If you are going to replace Axis1 (and make no mistake, this *is* one of > the things you have to do), you have to do most everything it does - > only better. > > -- > Tom Jordahl > Macromedia Server Development > > > -- Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform
