On 8/10/05, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: <snip>
> 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. > > 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. i'm a big xmlbeans fan and think it's a good match for axis2. there are a couple of use cases where i think it (and most start-from-schema binders) are weak: 1 when faced with a unexpressive schema 2 fast prototyping especially when adding a web service interface onto an existing application and in particular by developers with strong java backgrounds but weak xml. IMHO start-from-java is a better match for these cases. (though in the second, it would probably be replaced later by a generative solution.) so, maybe there'd be some reason why people might want to use a start-from-java binder even if it turns out to be better to directly port the old style stuff. opinions? - robert
