Hi Glen, > All of that stuff is about a) RPC encoded support, and b) easy > interoperability/usage for Java coders. Both of which were discussed at > the last f2f, and agreed to by the team.
I'm not opposed to them .. its a question of where it goes only. > I couldn't disagree more, Sanjiva. Axis2 is quite different from Axis1 > in any number of ways already - let me just list a few: :) > Disabling simple "code-first" use cases and the ability to map basic > schemas to code in friendly ways would, IMHO, be a silly thing to do. > Why wouldn't you want Axis2 to be as easy to use out of the box as GLUE > or WASP? Just because people want to use that stuff doesn't mean that > the engine doesn't still a) benefit from the speed/architecure > improvements, and b) allow for the XML-centric use cases as well. +1. > > I know there are many people in the world who *still* want to use Web > > services to SOAP enable RPC stuff. If that's what you want to do then > > Axis1 does one hell of a job of doing that; please keep using it .. the > > code works fine and many smart people have put in a lot of effort on it. > > ...and people also want to do this stuff with the benefits of Axis2. +1. > First, the data binding doesn't have anything to do with the MEP, I'm > not sure where that comes from...? Not directly, but RPC style (in-out MEP) encourages the view that data binding is core to the world because of the method-call style programming model with statically typed parameters which is natural there. > Second, this really hinges around what "core" means. If you mean > "should it be in the distribution", my answer is an EMPHATIC "yes". If > you mean "should it be in the axis-core.jar file", then I'm open to > discussion - I'm perfectly fine with having this framework be a > "standard extension" in a separate jar which can still be easily used > out-of-the-box without downloading other packages. So in your view, are these all v1 features? If yes, I don't agree- I think the core of Axis2 is quite useful in its own right without requiring all these additional features. I have no problem with future releases of the Axis2 distribution having these standard extensions (and more). > I think we should do the work to produce something that does this work, > whether using JiBX/XStream or building it ourselves, and I think it > needs to come with the download. Aside from that, I'm +1 to having it > be pluggable or not used at all by XML-puritans. +1. Sanjiva.
