Hi Eric!
Just to see if I've got a handle on this, the two approaches suggested are:* Support XML Schema mapping insofar as it avoids excessive complexity in generated code. In other words, simplicity above all else. A reasonable position, in that Axis 2.0 is supposed to be the lightweight, responsive, better designed version of Axis 1.X * Support the full set of test cases. Also a reasonable position, in that people expect Axis 2.0 to be more capable than Axis 1.X.My take is the first option sounds like the appropriate project scope. Axis 2.0 explicitly sets out the premise that its databinding is pluggable. I don't think users expect the Axis 2.0 project itself to cover the full problem without the help of something else.
It's just a question of how "full" the "full set" is. I definitely think if Axis2 cannot pass at least rounds 1-3 of the soapbuilders tests out of the box, we have a serious problem. And yes, we could do this by just digging through raw XML, but I'd like databinding at least to this level to work so that we can be somewhere close to what Axis 1.X gets you. Round 4, group I is the tricky one, since it tests some of the more interesting schema constructs. It still doesn't do anything really weird like substitution groups, and I do think we should be able to handle anything in there with our stuff. However, I'd be fine if we could only do rounds 1-3 for 1.0.
--Glen
