Re: RFC: Dynamic [de]serializer mappings

[Aleksander Slominski <as...@cs.indiana.edu>]

Mark Swanson wrote:

> Hello,
>
> I'm quite pleased that I can now use end-end XSD/POJOs with Axis 1.3 
> via XmlBeans!
>
> However, the manual method of specifying your [de]serializers imposed 
> by Axis makes this power virtually impossible to wield. Just think of 
> a large collection of quickly evolving XSD documents and having to 
> manually maintain their [de]serializer mappings in code. (In code 
> because I've read that the mappings in the wsdd don't seem to work) 
> Arg...
>
> Does anyone have any ideas how to solve this?
> I'm thinking it would be nice to say, "Anything in package 
> x.y.xbeans.* is an XmlBean and the XmlBeans [de]serializers must be 
> used.". This would sure make it easy. What would the implementations 
> details of a regex definition like this look like?
>
> Thoughts?
>
>
if your POJO already uses XmlBeans you do not need this as XmlBeans 
generated classes have enough metadata embedded in them to get XML 
Schema type info necessary to do all (de)serialization.

so IMHO optimal solution is to write your POJO/XmlBeans and then drop 
into any SOAP container and after minimal  configuration (Java or XML) 
you have service exposed and client that wants to use such service 
should just get reference to java interface to this POJO/XmlBeans and 
use it. BTW: tis kind of code mobility and SOAP toolkit independence was 
the aim of WS/XSUL2 [1] :)

thanks,

alek
[1] http://www.extreme.indiana.edu/xgws/xsul

-- 
The best way to predict the future is to invent it - Alan Kay