Exactly. On Fri, Sep 28, 2012 at 12:11 PM, Raphael Lacerda <lacerdaph(a)gmail.com&gt;wrote: > Tnks Jason and Daniel. > > That was exactly what i was hopping to hear it. > > I think that it's a huge step to help the developers to migrate their > applications. > > So, the natural step from Seam 2.x user's would be: > > 1 - Seam 2.3, with JSF2, JPA2, Richfaces 4.x or Primefaces 3.x > 2 - The next step would be moving to CDI. > 3 - Then, on the near future, add Apache DeltaSpike > > > Do you guys agree? > > > > Raphael Lacerda > > > > On Fri, Sep 28, 2012 at 2:56 PM, Daniel Hinojosa < > dhinojosa(a)evolutionnext.com&gt; wrote: > >> I personally can't see Seam 3.x modules being used in Seam 2.3 unless >> you instantiate all the relevant classes in your components.xml and wire >> them that way. I am not aware of any bridge and maybe Marek can address >> some more specifics to that, or maybe correct my statement. >> >> On Fri, Sep 28, 2012 at 11:29 AM, Raphael Lacerda <lacerdaph(a)gmail.com&gt;wrote: >> >>> Ok.. Great news about Seam 2.3! i'm looking for to try it! >>> But i've a dummy question.. >>> >>> Seam 3 is about modules that provide support for JSF2 and CDI. It >>> suffered a lot out criticism/misunderstanding ( >>> http://in.relation.to/Bloggers/SeamNextAnnouncement) because the seam >>> developers were used to a fully integrated framework, not pluggable modules. >>> >>> So, did Seam 2.3 come to provide a fully integrated framework instead >>> of modules? >>> How it's gonna be? >>> Will I be able to use Seam 2.3 with some Seam 3.x's modules? Or all >>> Seam3.x's features will be already available in Seam 2.3? >>> >>> >>> >>> Raphael Lacerda >>> >>> >>> >>> >>> On Wed, Sep 19, 2012 at 11:50 AM, Gunvaldson, John < >>> jgunvaldson(a)ucsd.edu&gt; wrote: >>> >>>> <!-- >>>> By far the largest chunk is going to be migrating to JSF 2 >>>> --> >>>> And by far, the greatest opportunity for advancing your Seam 2.2 >>>> applications into the future. Finally, a migration path to JSF 2 is >>>> available without a huge rewrite. IE 9 problems relating to old Richfaces >>>> libraries can be attended to (instead of just patched). I am so looking >>>> forward to moving out of Richfaces 3.3 into 4+, as well as leveraging the >>>> JSF 2 enhanced templating features, so much more. The opportunity to move >>>> our Jboss application server version forward to 7, in itself, is hugely >>>> appreciated. >>>> >>>> Thank You Marek! >>>> >>>> John Gunvaldson >>>> San Diego, CA >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> seam-dev mailing list >>>> seam-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/seam-dev >>>> >>> >>> >>> _______________________________________________ >>> seam-dev mailing list >>> seam-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/seam-dev >>> >>> >> >> >> -- >> Daniel Hinojosa >> Programmer, Instructor, and Consultant >> dhinojosa(a)evolutionnext.com >> http://www.evolutionnext.com >> http://www.abqjug.org >> >> > > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev > > -- Jason Porter http://lightguard-jp.blogspot.com http://twitter.com/lightguardjp Software Engineer Open Source Advocate Author of Seam Catch - Next Generation Java Exception Handling PGP key id: 926CCFF5 PGP key available at: keyserver.net, pgp.mit.edu _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

Yeah.. The tests i believe will suffer some changes because Seam 2.3 are gonna be based on Arquillian rather than JBoss Embedded TestNG right? Raphael Lacerda On Fri, Sep 28, 2012 at 3:49 PM, Daniel Hinojosa <dhinojosa(a)evolutionnext.com <mailto:dhinojosa@evolutionnext.com>> wrote: Believe so...and if your project is clean and testable then code should not change, only the meta-data (annotations, etc). Score another for clean code. Of course I don't have a crystal ball, but I anticipate that that's what will be experienced. On Fri, Sep 28, 2012 at 12:15 PM, Jason Porter <lightguard.jp(a)gmail.com <mailto:lightguard.jp@gmail.com>> wrote: Exactly. On Fri, Sep 28, 2012 at 12:11 PM, Raphael Lacerda <lacerdaph(a)gmail.com <mailto:lacerdaph@gmail.com>> wrote: Tnks Jason and Daniel. That was exactly what i was hopping to hear it. I think that it's a huge step to help the developers to migrate their applications. So, the natural step from Seam 2.x user's would be: 1 - Seam 2.3, with JSF2, JPA2, Richfaces 4.x or Primefaces 3.x 2 - The next step would be moving to CDI. 3 - Then, on the near future, add Apache DeltaSpike Do you guys agree? Raphael Lacerda On Fri, Sep 28, 2012 at 2:56 PM, Daniel Hinojosa <dhinojosa(a)evolutionnext.com <mailto:dhinojosa@evolutionnext.com>> wrote: I personally can't see Seam 3.x modules being used in Seam 2.3 unless you instantiate all the relevant classes in your components.xml and wire them that way. I am not aware of any bridge and maybe Marek can address some more specifics to that, or maybe correct my statement. On Fri, Sep 28, 2012 at 11:29 AM, Raphael Lacerda <lacerdaph(a)gmail.com <mailto:lacerdaph@gmail.com>> wrote: Ok.. Great news about Seam 2.3! i'm looking for to try it! But i've a dummy question.. Seam 3 is about modules that provide support for JSF2 and CDI. It suffered a lot out criticism/misunderstanding (http://in.relation.to/Bloggers/SeamNextAnnouncement) because the seam developers were used to a fully integrated framework, not pluggable modules. So, did Seam 2.3 come to provide a fully integrated framework instead of modules? How it's gonna be? Will I be able to use Seam 2.3 with some Seam 3.x's modules? Or all Seam3.x's features will be already available in Seam 2.3? Raphael Lacerda On Wed, Sep 19, 2012 at 11:50 AM, Gunvaldson, John <jgunvaldson(a)ucsd.edu <mailto:jgunvaldson@ucsd.edu>> wrote: <!-- By far the largest chunk is going to be migrating to JSF 2 --> And by far, the greatest opportunity for advancing your Seam 2.2 applications into the future. Finally, a migration path to JSF 2 is available without a huge rewrite. IE 9 problems relating to old Richfaces libraries can be attended to (instead of just patched). I am so looking forward to moving out of Richfaces 3.3 into 4+, as well as leveraging the JSF 2 enhanced templating features, so much more. The opportunity to move our Jboss application server version forward to 7, in itself, is hugely appreciated. Thank You Marek! John Gunvaldson San Diego, CA _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org <mailto:seam-dev@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/seam-dev _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org <mailto:seam-dev@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/seam-dev -- Daniel Hinojosa Programmer, Instructor, and Consultant dhinojosa(a)evolutionnext.com <mailto:dhinojosa@evolutionnext.com> http://www.evolutionnext.com http://www.abqjug.org _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org <mailto:seam-dev@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/seam-dev -- Jason Porter http://lightguard-jp.blogspot.com http://twitter.com/lightguardjp Software Engineer Open Source Advocate Author of Seam Catch - Next Generation Java Exception Handling PGP key id: 926CCFF5 PGP key available at: keyserver.net <http://keyserver.net>;, pgp.mit.edu <http://pgp.mit.edu> _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org <mailto:seam-dev@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/seam-dev -- Daniel Hinojosa Programmer, Instructor, and Consultant dhinojosa(a)evolutionnext.com <mailto:dhinojosa@evolutionnext.com> http://www.evolutionnext.com http://www.abqjug.org _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBpj6YACgkQU4HO8G8hNxURjQCgs+b4nRtY7aMa9iNoZ+xz8sdl qM0AoM1pkeU6PuAZo0cBLGyyMSCL36Iz =olOH -----END PGP SIGNATURE-----