Glen Daniels wrote:
(adding [axis2] prefix)
Am talking about all 5 interop tests
(http://java.sun.com/webservices/interop/soapbuilders/index.html). BUT
only those that are rpc/lit or doc/lit.
I disagree, dims - I think we should do them all including RPC/enc
(RPC/enc is a goal for 1.0). There is already some support for SOAP
encoding (1.1 and 1.2) in the databinding stuff I started working on,
and it should work fine. Arrays will still need some tweaking, but
multirefs are already working.
What we need is simply to tie the XMLSchema model into generated
classes which supply TypeDesc metadata
(org.apache.axis2.databinding.metadata), then make sure to use the
RPCInOutMessageReceiver in ..axis2.rpc.
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.
On a somewhat related note - what do people think about making the
default databinding "none" instead of XMLBeans? In other words, when
you point WSDL2Java at a WSDL, it should generate stubs by default
that simply take/return OMElements. If you want databinding at all,
you set up an option (command line, config file in current dir, config
file in home dir) to do it.
+1
-Eric.
