-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 19.9.2012 00:12, Jason Porter wrote:
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.
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 ;-).
On Tue, Sep 18, 2012 at 6:11 AM, Marek Novotny <mnovotny(a)redhat.com
<mailto:mnovotny@redhat.com>> wrote:
I have mangled a little the $SUBJECT with my previous email :-/
one additional note - migration guide is chapter 4
On 18.9.2012 13:32, Marek Novotny wrote:
> Hi Seam devs,
> I committed a new documentation chapter into SVN -
http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/seam-refe....
> 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
> seam-dev(a)lists.jboss.org <mailto:seam-dev@lists.jboss.org>
>
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
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>
- --
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/
iEYEARECAAYFAlBZfq4ACgkQU4HO8G8hNxWJcgCffj0DTHD12YJPcetVurI8Vk0P
4IkAoItMF2wwBR7byTpQshQ0Q6fKOL8y
=A3f2
-----END PGP SIGNATURE-----