Discussion:
[seam-dev] Seam 2.3 migration review available
Marek Novotny
2012-09-18 11:32:44 UTC
Permalink
Hi Seam devs,

I committed a new documentation chapter into SVN -
http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/MigrationGuide.xml.
This is for Seam 2.2 to 2.3 migration

Could you review it, please? /attached is generated PDF.

It is not too long and it should cover all important points/steps which
is required for using Seam 2.3.0.Final if you already have existing Seam
2.2 application.

Cheers,

- --
Marek Novotny
- --
WFK and Seam Product Lead

Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
Marek Novotny
2012-09-18 12:11:35 UTC
Permalink
I have mangled a little the $SUBJECT with my previous email :-/

one additional note - migration guide is chapter 4
Post by Marek Novotny
Hi Seam devs,
I committed a new documentation chapter into SVN -
http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/MigrationGuide.xml.
This is for Seam 2.2 to 2.3 migration
Could you review it, please? /attached is generated PDF.
It is not too long and it should cover all important points/steps which
is required for using Seam 2.3.0.Final if you already have existing Seam
2.2 application.
Cheers,
--
Marek Novotny
--
WFK and Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
_______________________________________________
seam-dev mailing list
https://lists.jboss.org/mailman/listinfo/seam-dev
- --
Marek Novotny
- --
WFK and Seam Product Lead

Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
Jason Porter
2012-09-18 22:12:21 UTC
Permalink
I like what's here, however, I am afraid that it makes the migration look
too easy. By far the largest chunk is going to be migrating to JSF 2. No
matter which component suite you use there isn't one (that I'm aware of)
that can be used on JSF 1.x and 2.x.

Components will be renamed or replaced, layouts may change, etc. At the
very least we should probably tell people to look for a migration guide for
the component suite they're using.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have mangled a little the $SUBJECT with my previous email :-/
one additional note - migration guide is chapter 4
Post by Marek Novotny
Hi Seam devs,
I committed a new documentation chapter into SVN -
http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/MigrationGuide.xml
.
Post by Marek Novotny
This is for Seam 2.2 to 2.3 migration
Could you review it, please? /attached is generated PDF.
It is not too long and it should cover all important points/steps which
is required for using Seam 2.3.0.Final if you already have existing Seam
2.2 application.
Cheers,
--
Marek Novotny
--
WFK and Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
_______________________________________________
seam-dev mailing list
https://lists.jboss.org/mailman/listinfo/seam-dev
- --
Marek Novotny
- --
WFK and Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iEYEARECAAYFAlBYZPcACgkQU4HO8G8hNxU6qACg57rA8Tj45ssm3fCPgGCT3Mmg
zmwAn2fmLGN66GMiJBqL0mR8WuFSbRz/
=TVZ9
-----END PGP SIGNATURE-----
_______________________________________________
seam-dev mailing list
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
Flavio Costa
2012-09-19 02:04:42 UTC
Permalink
Simple question, can one choose not to upgrade to JSF 2 but still upgrade
to Seam 2.3?

As Jason pointed out, that seemed the most problematic part of the
migration.
Post by Jason Porter
I like what's here, however, I am afraid that it makes the migration look
too easy. By far the largest chunk is going to be migrating to JSF 2. No
matter which component suite you use there isn't one (that I'm aware of)
that can be used on JSF 1.x and 2.x.
Components will be renamed or replaced, layouts may change, etc. At the
very least we should probably tell people to look for a migration guide for
the component suite they're using.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have mangled a little the $SUBJECT with my previous email :-/
one additional note - migration guide is chapter 4
Post by Marek Novotny
Hi Seam devs,
I committed a new documentation chapter into SVN -
http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/MigrationGuide.xml
.
Post by Marek Novotny
This is for Seam 2.2 to 2.3 migration
Could you review it, please? /attached is generated PDF.
It is not too long and it should cover all important points/steps which
is required for using Seam 2.3.0.Final if you already have existing Seam
2.2 application.
Cheers,
--
Marek Novotny
--
WFK and Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
_______________________________________________
seam-dev mailing list
https://lists.jboss.org/mailman/listinfo/seam-dev
- --
Marek Novotny
- --
WFK and Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iEYEARECAAYFAlBYZPcACgkQU4HO8G8hNxU6qACg57rA8Tj45ssm3fCPgGCT3Mmg
zmwAn2fmLGN66GMiJBqL0mR8WuFSbRz/
=TVZ9
-----END PGP SIGNATURE-----
_______________________________________________
seam-dev mailing list
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
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Flávio Coutinho da Costa
Jason Porter
2012-09-19 02:37:47 UTC
Permalink
I'm pretty sure an upgrade to Seam 2.3 is also an upgrade to JSF2. I know some of the bugs that were fixed for CR required JSF2.

Sent from my iPhone
Simple question, can one choose not to upgrade to JSF 2 but still upgrade to Seam 2.3?
As Jason pointed out, that seemed the most problematic part of the migration.
I like what's here, however, I am afraid that it makes the migration look too easy. By far the largest chunk is going to be migrating to JSF 2. No matter which component suite you use there isn't one (that I'm aware of) that can be used on JSF 1.x and 2.x.
Components will be renamed or replaced, layouts may change, etc. At the very least we should probably tell people to look for a migration guide for the component suite they're using.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have mangled a little the $SUBJECT with my previous email :-/
one additional note - migration guide is chapter 4
Post by Marek Novotny
Hi Seam devs,
I committed a new documentation chapter into SVN -
http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/MigrationGuide.xml.
This is for Seam 2.2 to 2.3 migration
Could you review it, please? /attached is generated PDF.
It is not too long and it should cover all important points/steps which
is required for using Seam 2.3.0.Final if you already have existing Seam
2.2 application.
Cheers,
--
Marek Novotny
--
WFK and Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
_______________________________________________
seam-dev mailing list
https://lists.jboss.org/mailman/listinfo/seam-dev
- --
Marek Novotny
- --
WFK and Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iEYEARECAAYFAlBYZPcACgkQU4HO8G8hNxU6qACg57rA8Tj45ssm3fCPgGCT3Mmg
zmwAn2fmLGN66GMiJBqL0mR8WuFSbRz/
=TVZ9
-----END PGP SIGNATURE-----
_______________________________________________
seam-dev mailing list
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
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Flávio Coutinho da Costa
Marek Novotny
2012-09-19 08:19:28 UTC
Permalink
Yes, majority of bugs are for upgrading to JSF2, EJB 3.1 and running on
JBoss AS 7.x.
There are minority number of bugs from previous 2.x versions.
Post by Jason Porter
I'm pretty sure an upgrade to Seam 2.3 is also an upgrade to JSF2. I
know some of the bugs that were fixed for CR required JSF2.
Sent from my iPhone
Simple question, can one choose not to upgrade to JSF 2 but still upgrade to Seam 2.3?
As Jason pointed out, that seemed the most problematic part of the migration.
I like what's here, however, I am afraid that it makes the
migration look too easy. By far the largest chunk is going to be
migrating to JSF 2. No matter which component suite you use there
isn't one (that I'm aware of) that can be used on JSF 1.x and 2.x.
Components will be renamed or replaced, layouts may change, etc.
At the very least we should probably tell people to look for a
migration guide for the component suite they're using.
On Tue, Sep 18, 2012 at 6:11 AM, Marek Novotny
I have mangled a little the $SUBJECT with my previous email :-/
one additional note - migration guide is chapter 4
Hi Seam devs,
I committed a new documentation chapter into SVN -
http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/MigrationGuide.xml.
This is for Seam 2.2 to 2.3 migration
Could you review it, please? /attached is generated PDF.
It is not too long and it should cover all important
points/steps which
is required for using Seam 2.3.0.Final if you already have
existing Seam
2.2 application.
Cheers,
--
Marek Novotny
--
WFK and Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
_______________________________________________
seam-dev mailing list
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Marek Novotny
--
WFK and Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
_______________________________________________
seam-dev mailing list
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
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Flávio Coutinho da Costa
- --
Marek Novotny
- --
WFK and Seam Product Lead

Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
Marek Novotny
2012-09-19 08:17:45 UTC
Permalink
Post by Flavio Costa
Simple question, can one choose not to upgrade to JSF 2 but still
upgrade to Seam 2.3?
No, that is not an option. Seam 2.3.x is about upgrade of parts of Java
EE5 to EE6.

If you want to use JSF1.2 you should stay still on Seam 2.2.x.
Post by Flavio Costa
As Jason pointed out, that seemed the most problematic part of the
migration.
I like what's here, however, I am afraid that it makes the migration
look too easy. By far the largest chunk is going to be migrating to
JSF 2. No matter which component suite you use there isn't one (that
I'm aware of) that can be used on JSF 1.x and 2.x.
Components will be renamed or replaced, layouts may change, etc. At
the very least we should probably tell people to look for a
migration guide for the component suite they're using.
I have mangled a little the $SUBJECT with my previous email :-/
one additional note - migration guide is chapter 4
Post by Marek Novotny
Hi Seam devs,
I committed a new documentation chapter into SVN -
http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/MigrationGuide.xml.
Post by Marek Novotny
This is for Seam 2.2 to 2.3 migration
Could you review it, please? /attached is generated PDF.
It is not too long and it should cover all important
points/steps which
Post by Marek Novotny
is required for using Seam 2.3.0.Final if you already have
existing Seam
Post by Marek Novotny
2.2 application.
Cheers,
--
Marek Novotny
--
WFK and Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
_______________________________________________
seam-dev mailing list
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Marek Novotny
--
WFK and Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
_______________________________________________
seam-dev mailing list
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
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Flávio Coutinho da Costa
- --
Marek Novotny
- --
WFK and Seam Product Lead

Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
Marek Novotny
2012-09-19 08:13:34 UTC
Permalink
Post by Jason Porter
I like what's here, however, I am afraid that it makes the migration
look too easy. By far the largest chunk is going to be migrating to JSF
2. No matter which component suite you use there isn't one (that I'm
aware of) that can be used on JSF 1.x and 2.x.
I think the migration is not too tough, as we did these migration steps
in Seam examples included in Seam distribution. The painful is JSF 2
component libraries like Richfaces 3.3->4.x migration or Icefaces 1.x ->
3.x. And the latter is not really prepared Seam 2.3 as it is described
in https://issues.jboss.org/browse/JBSEAM-5022, which is regression from
Icefaces 1.6.
Post by Jason Porter
Components will be renamed or replaced, layouts may change, etc. At the
very least we should probably tell people to look for a migration guide
for the component suite they're using.
I think that I am trying to say in section 4.2.2

<blockquote>
Depending on what JSF components that you use like Richfaces or
Icefaces, there may be some differences when upgrading from JSF 1.x to
JSF 2.x. You may need to upgrade libraries entirely. Consult any
component framework documentation on those changes. This migration
doesn't cover these migration steps.
</blockquote>

I will change
"You may need to upgrade libraries entirely."
to
"You have to need to upgrade libraries entirely."

If you think we need enhance this paragraph more, I am open to
suggestion ;-).
Post by Jason Porter
I have mangled a little the $SUBJECT with my previous email :-/
one additional note - migration guide is chapter 4
Post by Marek Novotny
Hi Seam devs,
I committed a new documentation chapter into SVN -
http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/MigrationGuide.xml.
Post by Marek Novotny
This is for Seam 2.2 to 2.3 migration
Could you review it, please? /attached is generated PDF.
It is not too long and it should cover all important points/steps
which
Post by Marek Novotny
is required for using Seam 2.3.0.Final if you already have
existing Seam
Post by Marek Novotny
2.2 application.
Cheers,
--
Marek Novotny
--
WFK and Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
_______________________________________________
seam-dev mailing list
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Marek Novotny
--
WFK and Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
_______________________________________________
seam-dev mailing list
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>
- --
Marek Novotny
- --
WFK and Seam Product Lead

Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
Gunvaldson, John
2012-09-19 14:50:20 UTC
Permalink
<!--
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
Raphael Lacerda
2012-09-28 17:29:15 UTC
Permalink
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
Post by Jason Porter
<!--
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
https://lists.jboss.org/mailman/listinfo/seam-dev
Jason Porter
2012-09-28 17:51:49 UTC
Permalink
Seam 2.3 is the same Seam that you're used to from Seam 2.2. The only
difference is that it supports JSF2, JPA2 and runs out of the box on AS7.
It doesn't have anything to do with CDI or Seam 3.
Post by Raphael Lacerda
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
Post by Jason Porter
<!--
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
https://lists.jboss.org/mailman/listinfo/seam-dev
_______________________________________________
seam-dev mailing list
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
Raphael Lacerda
2012-09-28 18:11:10 UTC
Permalink
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 <
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.
Post by Raphael Lacerda
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
Post by Jason Porter
<!--
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
https://lists.jboss.org/mailman/listinfo/seam-dev
_______________________________________________
seam-dev mailing list
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Daniel Hinojosa
Programmer, Instructor, and Consultant
http://www.evolutionnext.com
http://www.abqjug.org
Jason Porter
2012-09-28 18:15:32 UTC
Permalink
Exactly.
Post by Raphael Lacerda
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.
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 <
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.
Post by Raphael Lacerda
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
Post by Jason Porter
<!--
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
https://lists.jboss.org/mailman/listinfo/seam-dev
_______________________________________________
seam-dev mailing list
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Daniel Hinojosa
Programmer, Instructor, and Consultant
http://www.evolutionnext.com
http://www.abqjug.org
_______________________________________________
seam-dev mailing list
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
Daniel Hinojosa
2012-09-28 18:49:00 UTC
Permalink
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.
Post by Jason Porter
Exactly.
Post by Raphael Lacerda
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.
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 <
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.
Post by Raphael Lacerda
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 <
Post by Jason Porter
<!--
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
https://lists.jboss.org/mailman/listinfo/seam-dev
_______________________________________________
seam-dev mailing list
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Daniel Hinojosa
Programmer, Instructor, and Consultant
http://www.evolutionnext.com
http://www.abqjug.org
_______________________________________________
seam-dev mailing list
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
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Daniel Hinojosa
Programmer, Instructor, and Consultant
***@evolutionnext.com
http://www.evolutionnext.com
http://www.abqjug.org
Raphael Lacerda
2012-09-28 18:58:14 UTC
Permalink
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 <
Post by Daniel Hinojosa
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.
Post by Jason Porter
Exactly.
Post by Raphael Lacerda
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.
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 <
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.
Post by Raphael Lacerda
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 <
Post by Jason Porter
<!--
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
https://lists.jboss.org/mailman/listinfo/seam-dev
_______________________________________________
seam-dev mailing list
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Daniel Hinojosa
Programmer, Instructor, and Consultant
http://www.evolutionnext.com
http://www.abqjug.org
_______________________________________________
seam-dev mailing list
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
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Daniel Hinojosa
Programmer, Instructor, and Consultant
http://www.evolutionnext.com
http://www.abqjug.org
Marek Novotny
2012-10-01 12:42:14 UTC
Permalink
Actually we recommend to use Arquillian and JUnit, but that is not too
scary to migrate as we proved that in our Seam integration testsuite and
also examples' tests.
Post by Raphael Lacerda
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
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
Exactly.
On Fri, Sep 28, 2012 at 12:11 PM, Raphael Lacerda
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.
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
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
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
<!--
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
https://lists.jboss.org/mailman/listinfo/seam-dev
_______________________________________________
seam-dev mailing list
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Daniel Hinojosa
Programmer, Instructor, and Consultant
http://www.evolutionnext.com
http://www.abqjug.org
_______________________________________________
seam-dev mailing list
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
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Daniel Hinojosa
Programmer, Instructor, and Consultant
http://www.evolutionnext.com
http://www.abqjug.org
_______________________________________________
seam-dev mailing list
https://lists.jboss.org/mailman/listinfo/seam-dev
- --
Marek Novotny
- --
WFK and Seam Product Lead

Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno

Loading...