6:27 p.m.
With Seam 3.0.0 on the horizon, it's time to get serious about putting
together the Seam 2 to Seam 3 migration guide. The purpose of this thread is
to capture requirements for this guide.
For a migration guide to be useful, it must be rooted in practical
procedures rather than theoretical correlations. Therefore, before drafting
a single paragraph, it’s important to capture the requirements for migration
from the user community. We'll then seek to answer those questions in the
guide. Once we have addressed those questions, we can fill-in the guide with
more generalized mappings for completeness.
So I ask, "what's your vision of an ideal migration guide?"
We don't have to answer the questions in this guide, though if you feel
compelled to answer a question, feel free to do so. Let's just try to stay
focused on identifying your concerns and questions, then we can discuss the
answers while reviewing the guide drafts.
Fire the requirements away. If you've already written requirements somewhere
on the web, you can just link to them.
-Dan
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://www.google.com/profiles/dan.j.allen#about
http://mojavelinux.com
http://mojavelinux.com/seaminaction
6:29 p.m.
I'll seed the discussion by posting requirements sent to me by Hamzah
Zineddin <hamza_zz(a)yahoo.com>
For the migration, below are some areas of concern that would be great to
have some answers for. Ideally, it would be great if there is a tool that
would read a Seam 2 project folder and list the changes that should be made.
1. What should be changed from view layer (in my case Richfaces)?
Currently xhtml files use Seam 2 schema. We have some quite complicated
components and pages and make heavy usage of Ajax. JSF 2 adds a lot of
functionality for Ajax and it'll be good to know which UI components should
be updated/changed.
2. How to migrate navigation and pages.xml to Seam 3 and CDI to work with
JSF 2 properly? What about page parameters migration if any.
3. URL rewrite migration.
4. How to migrate bean and deployment configuration from Seam 2 to CDI
and Seam 3. For example, components.xml and other config files like
hibernate or persistence.
5. How to migrate tests:
1. UI tests with SeamTest. I noticed there is not a good way of doing
UI tests in Seam 3 unless I'm missing something.
2. Integration tests that use an in-memory db. I know Arquillian in
Seam 3 would take of this.
6. How to migrate from Seam 2 specific areas to Seam 3. For example, in
my project we use email templates heavily from Seam 2.
7. Localization and internationalization migration. For example, what
happens to message bundles and StatusMessages from Seam 2.
8. Security migration, I use authenticate-method and did not find its
equivalent in Seam 3. Seam 3 Beta release is missing security documentation.
9. How to migrate the integration with open ID from Seam 2 to work in
Seam 3 and CDI. Open Id support in Seam 2 was lacking and did not support
important features like attribute exchange. People had to write custom code
and it'll be good to know how to migrate custom code to Seam 3 and CDI.
10. How to migrate components that deal with external services. For
example, my project integrates with Facebook using Facebook java API which
depends on Servlet (not java script API). What would be the
migrationplan? It would be even better if Seam 3 would offer a way to
integrate with
common services like Facebook.
11. How to migrate outjected objects. CDI uses @Produces annotation but
having few concrete examples part of migration guide would make
developer's lives much easier.
12. How to migrate conversational and transactional components? Again,
having few concrete examples would great to accomplish this.
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://www.google.com/profiles/dan.j.allen#about
http://mojavelinux.com
http://mojavelinux.com/seaminaction
7:35 p.m.
Dan,
Migration is one thing, but at some point we were talking about a
"compatibility" module
Is this module still in the plans?
That module could (at least try to) "automagically" translate seam 2 calls into
CDI/Seam 3 calls... But I don't know if it is
feasable as Seam 3 drags JSF 2.0, RF 4, etc with it and the paradigm may be different
(differences in scopes etc.) ...
Also I don't know if there is a real need for it as Seam 2 apps should run as-is in
JEE 6 containers..
Denis
On 02/24/2011 07:29 PM, Dan Allen wrote:
I'll seed the discussion by posting requirements sent to me by
Hamzah Zineddin <hamza_zz(a)yahoo.com <mailto:hamza_zz@yahoo.com>>
For the migration, below are some areas of concern that would be great to have some
answers for. Ideally, it would be great if
there is a tool that would read a Seam 2 project folder and list the changes that should
be made.
1. What should be changed from view layer (in my case Richfaces)? Currently xhtml
files use Seam 2 schema. We have some quite
complicated components and pages and make heavy usage of Ajax. JSF 2 adds a lot of
functionality for Ajax and it'll be good
to know which UI components should be updated/changed.
2. How to migrate navigation and pages.xml to Seam 3 and CDI to work with JSF 2
properly? What about page parameters
migrationif any.
3. URL rewrite migration.
4. How to migrate bean and deployment configuration from Seam 2 to CDI and Seam 3. For
example, components.xml and other config
files like hibernate or persistence.
5. How to migrate tests:
1. UI tests with SeamTest. I noticed there is not a good way of doing UI tests
in Seam 3 unless I'm missing something.
2. Integration tests that use an in-memory db. I know Arquillian in Seam 3 would
take of this.
6. How to migrate from Seam 2 specific areas to Seam 3. For example, in my project we
use email templates heavily from Seam 2.
7. Localization and internationalization migration. For example, what happens to
message bundles and StatusMessages from Seam 2.
8. Security migration, I use authenticate-method and did not find its equivalent in
Seam 3. Seam 3 Beta release is missing
security documentation.
9. How to migrate the integration with open ID from Seam 2 to work in Seam 3 and CDI.
Open Id support in Seam 2 was lacking and
did not support important features like attribute exchange. People had to write
custom code and it'll be good to know how to
migrate custom code to Seam 3 and CDI.
10. How to migrate components that deal with external services. For example, my project
integrates with Facebook using Facebook
java API which depends on Servlet (not java script API). What would be the
migrationplan? It would be even better if Seam 3
would offer a way to integrate with common services like Facebook.
11. How to migrate outjected objects. CDI uses @Produces annotation but having few
concrete examples part of migrationguide
would make developer's lives much easier.
12. How to migrate conversational and transactional components? Again, having few
concrete examples would great to accomplish this.
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://www.google.com/profiles/dan.j.allen#about
http://mojavelinux.com
http://mojavelinux.com/seaminaction
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
5066
days inactive
5066
days old
2 comments
2 participants
participants (2)
-
Dan Allen -
Denis Forveille