URL to be a link.
Maybe making the "Classic Seam 2" Column wider.
That's my 2 cents.
2012/7/5 Pete Muir <pmuir(a)redhat.com>
All,
Please review -
http://www.jboss.org/jdf/stage/migrations/get-started/
Pete
On 28 Jun 2012, at 23:29, Pete Muir wrote:
> One thing I picked up at Summit was that whilst people really appreciate
the migration guides, they also want more advice on when (/whether) they
should migrate, and what they should migrate too. We have the story pretty
much sorted:
>
> * if you have an app that works, and you want to keep running it on Seam
2.2, then great. We'll support that for X more years on EAP. Stay where you
are.
> * if you want to stay on Seam 2, but want to take advantage of the new
features of Java EE 6, then you can take a look at Seam 2.3, which is
currently beta quality. We haven't decided yet whether this will enter the
supported product arena.
> * if you want to take advantage of Java EE, you need to do a bit of
analysis of your app:
> ** if you have all the features you need in Java EE 6 (and look at
TicketMonster, you can achieve a lot!) then migrate to Java EE 6
> ** if you don't, but you can find them in DeltaSpike, and like living on
the edge, then you can take the path of adding DeltaSpike to Java EE 6. But
we don't have a well trodden path here, with guides for you to follow
> ** otherwise, take a look at the jdf roadmap to see when the features
you need will enter jdf, will all the goodness of the stack and guides
>
> Comments? I'll get this written up for
http://www.jboss.org/jdf/migrations/get-started/ next week.
> _______________________________________________
> jdf-dev mailing list
> jdf-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jdf-dev
_______________________________________________
jdf-dev mailing list
jdf-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jdf-dev