Developing in Seam and RichFaces is such a pain!

[mulation]

1, hot deploy not working, any little change of Java code will result in a re-build, re-deploy, that's 5 minutes.

2, Poor documented methods, any body tell me what's the difference of FacesMessages and FacesMessage and StatusMessages and StatusMessage?

   Have to guess what it was? and remember every guess will need a deploy

3, See, how poor is this forum's performance, so ugly, so slow..... is this year 1995?

After wasting 2 months of life, will retreat to GWT or ExtJS

Can we call this one a technical version Ponzi scheme!

[mulation]

Things goes insanely complicated, what's the benefit can this complexity give us?

better design?
better performance?
efficiency in development?

or just selling more books, gaining more client to consult with u?

[niox.nikospara.yahoo.com]

2. (a) There is no FacesMessage class in Seam, only in JSF. FacesMessages is A Seam component that propagates FacesMessages across redirects and interpolates EL expressions in the message string. From the Javadocs, and clear enough for me.

(b) StatusMessages is Abstract base class for providing status messages. View layers should provide a concrete implementation.. From the Javadocs again. Also, the Javadocs clearly show that FacesMessages is a concrete subclass, the implementation for the JSF view layer. The Wicket view layer would have a different one. And StatusMessage is a single message, handled by the underlying StatusMessages mechanism.

You obviously haven't done your homework regarding point 2.

In my opinion Seam does offer better design options, without adding unnecessary complexity. It IS complex, because it needs to solve more complex cases (eg the conversation).

Number 3 is serious though.

[oguzyalcin.oguzhanyalcin.gazi.edu.tr]

C'mon Tanner it tooks nearly a minute to deploy an ERP app :D
It seems it is time to retire your computer.

Number 3, it is really errrr... we all agree on it :)