Yee CN schrieb:
Hi James,
Thanks for sharing your experience. I am not against ejb3 as such – I am
using hibernate, just not ready to consider ejb3 yet. From your
description – hibernate is actually quite close to ejb3 then – at least
operationally?
Yes, actually the EJB3 API is sort of a cleaned up Hibernate 3.1 api,
with some stuff differently named (the session handler now is called
entity manager which makes more sense, and the weird lock, merge,
persist etc.. api, is somewhat streamlined into fewer functions)
Also the JBoss implementation is based upon Hibernate 3.1 while the
reference implementation from Sun is based upon Toplink, already 2-3
other implementations exists as we write this. One huge sign that this
stuff is here to stay, especially since it can run outside of EJB
containers as well, and probably will become a standard javax extension
outside of j2ee.
Also how difficult is it to migrate from pure JSF to SEAM? My body of
work is building – so I do hope the migration is not too painful. I will
need to make a decision pretty quickly anyway.
Well from the small project I have done, you basically can take all your
JSF knowledge with you, Seam is an extension which simplifies many
things in JSF. For instance you do not define any backing beans in xml
anymore, just a class which you then annotation as session bean etc...
The hardest part of seam is to get the project structure and deployment
in place the rest is "seamless"
- Re: Shale and MyFaces Werner Punz
-
