BTW Guillaume pointed me to this thread on IRC - there's a limitation
and workaround when using JAXB2 RI

http://sourceforge.net/forum/forum.php?thread_id=1493919&forum_id=513539

On 6/5/06, Guillaume Nodet <guillaume.nodet@worldonline.fr> wrote:
> The only problem is when one wants to introspect generic arguments.
> This is the main problem that happened with jaxb2.
> For example in the following construct,
>    List<MyBean>
> the MyBean type is not available at runtime.
> When using JAXB2 RI, you have to generate your beans with additional
> informations in annotations so that this information can be retrieved.
>
> Of course, this also applies to JAXWS (which uses JAXB2 marshalling)
>
> James Strachan wrote:
>
> > On 6/2/06, Jason Dillon <jason.dillon@planet57.com> wrote:
> >
> >> Do you happen to know of any examples where Retrotranslation fails?
> >
> >
> > There were some incremental errors getting JAXB2 to work which both
> > the JAXB2 RI team and Taras (the founder of retrotranslator) helped
> > fix.
> >
> > Certainly most things like generics, enums, annotations, reflection
> > and java-util-concurrent all work fine now. There could be a gap here
> > or there - such as AFAIK there is no backport of the new UUID class.
>
> AFAIK, the UUID has been backported and is available in 1.0.4 release
> of retrotranslator (at least).
>
> Cheers,
> Guillaume Nodet
>
> >
> > So I'd recommend folks run their unit tests on the backported code
> > just to be sure things all work.
> >
>


-- 

James
-------
http://radio.weblogs.com/0112098/