Even if they come with the distribution, you have to take care of them.
Additional issues?
Well, personally I dont like it to use annotations for nearly everything.
And seam would like to solve too much. For example JSF has some issues
with redirects, e.g. it looses all FacesMessages added so far. The next
page wont display them.
Seam solve this with an @In annotation. But this is a JSF defect, so it
needs to be solved on JSF level.
In MyFaces we solved it too, but the user do not have to learn any new
paradigm, just use JSF as you know it.
Also the "start on GET request" is a problem JSF has (aka bookmarkable),
we should find a solution which works outside of any heavyweight new
framework.
I think seam is getting too complex - way too much to read, no?
http://docs.jboss.com/seam/latest/reference/en/html/index.html
All this injection, bijection, multiple roles for beans ....
But ok, at all maybe no real issues - and I am biased, I am the
developer of the conversation tag and I like it to have small pieces of
code which tries to solve a single problem - and not to save the world ;-)
Thanks a lot! These explanations are very important.
--
Yours truly (Atenciosamente),
Rogério
