Hi all!
Sorry I'm a little late to this discussion...
Sanjiva Weerawarana wrote:
On Tue, 2005-08-09 at 20:51 +0100, robert burrell donkin wrote:
i've been wonder whether it might not be easier and quicker to use an
existing dynamic start-from-java binder. a lot of progress has been
made in the last year or so on these. i suspect that it might be
possible to attract developers from outside the core axis team to do
the coding (though probably some help with design would be needed) and
so free up some core axis committer time. might make some sense in the
medium term as well: one less non-core technology for the axis team to
support but...
Robert - can you give me an example? Are you talking about packages
like Beck (http://beck.sourceforge.net/)?
i guess whether it's worth it depends on how much work's already been
done and how close it is to being finished...
I've got some framework in my sandbox which I'll commit after 0.91 goes
out. It's indeed fairly like some of the stuff in Axis1, with a
DeserializationContext and a SerializationContext which keep track of
multirefs, an RPC MessageReciever which knows how to turn
<method><arg1/><arg2/></method> into a call to method(arg1, arg2),
simple serialization/deserialization framework based on the typemappers, etc
It's not that close to being finished yet, though.
Actually, even if Glen's doing an "old style" data binder, I would say
that does not in any way preclude doing a dynamic start-from-java binder
in any way. If yours comes out better we can figure out how to make it
be default.
+1. Let's continue discussion, and Robert and others can take a look at
where I'm headed once I commit.
Also, IIUC Glen's working on the simple type stuff to make rpc/lit type
stuff work nicely for simple typed parts. Right now the XMLBeans stuff
does everything but if you give a simple type you get ugly stuff- so
he's working to fix that so "String echoStr (String)" can be generated.
Correct. Whatever "simple" db framework we include must be able to:
1) Do rpc/lit AND rpc/enc
2) Handle WSDL 1.1 "wrapped" style method calls
3) Handle SOAP 1.1 and SOAP 1.2 data encoding (arrays, mrefs)
4) Handle WSDL 2.0 RPC style (once we're handling WSDL 2.0 :))
It would be nice if the framework could handle pulling the XML events
during deserialization in such a way that no OM caching needs to be done
(a little tricky when multirefs are involved).
Did I miss anything?
--Glen
