You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Jason Dillon <jd...@apache.org> on 2006/06/01 00:37:47 UTC
Retrotranslator KICKS ASS!!!
I'm giddy... Retrotranslator kicks so much ass... its awesome.
I just added a retro assembly to GShell (which requires 1.5 to build)
and verified that it works as expected after being retrotranslated
with a 1.4.2 JVM (Apple's).
Granted, GShell isn't doing all that much (yet), but it is using new
enums, autoboxing, generics, new for loop, varags, and if I can find
any more use for the new 1.5 goodness I will put that in too.
Anyways, was so excited I had to share.
Cheers,
--jason
Re: Retrotranslator KICKS ASS!!!
Posted by James Strachan <ja...@gmail.com>.
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 <gu...@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 <ja...@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/
Re: Retrotranslator KICKS ASS!!!
Posted by Guillaume Nodet <gu...@worldonline.fr>.
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 <ja...@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.
>
Re: Retrotranslator KICKS ASS!!!
Posted by James Strachan <ja...@gmail.com>.
On 6/2/06, Jason Dillon <ja...@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.
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/
Re: Retrotranslator KICKS ASS!!!
Posted by Jason Dillon <ja...@planet57.com>.
Do you happen to know of any examples where Retrotranslation fails?
--jason
-----Original Message-----
From: "James Strachan" <ja...@gmail.com>
Date: Thu, 1 Jun 2006 12:03:44
To:dev@geronimo.apache.org
Cc:tarasp@users.sourceforge.net
Subject: Re: Retrotranslator KICKS ASS!!!
On 5/31/06, Jason Dillon <jd...@apache.org> wrote:
> I'm giddy... Retrotranslator kicks so much ass... its awesome.
+1000
Getting JAXB2 RI to work on 1.4 is pretty amazing.
James
> I just added a retro assembly to GShell (which requires 1.5 to build)
> and verified that it works as expected after being retrotranslated
> with a 1.4.2 JVM (Apple's).
>
> Granted, GShell isn't doing all that much (yet), but it is using new
> enums, autoboxing, generics, new for loop, varags, and if I can find
> any more use for the new 1.5 goodness I will put that in too.
>
> Anyways, was so excited I had to share.
>
> Cheers,
>
> --jason
>
--
James
-------
http://radio.weblogs.com/0112098/
Re: Retrotranslator KICKS ASS!!!
Posted by James Strachan <ja...@gmail.com>.
On 5/31/06, Jason Dillon <jd...@apache.org> wrote:
> I'm giddy... Retrotranslator kicks so much ass... its awesome.
+1000
Getting JAXB2 RI to work on 1.4 is pretty amazing.
James
> I just added a retro assembly to GShell (which requires 1.5 to build)
> and verified that it works as expected after being retrotranslated
> with a 1.4.2 JVM (Apple's).
>
> Granted, GShell isn't doing all that much (yet), but it is using new
> enums, autoboxing, generics, new for loop, varags, and if I can find
> any more use for the new 1.5 goodness I will put that in too.
>
> Anyways, was so excited I had to share.
>
> Cheers,
>
> --jason
>
--
James
-------
http://radio.weblogs.com/0112098/