Help

Built with Seam

You can find the full source code for this website in the Seam package in the directory /examples/wiki. It is licensed under the LGPL.

FAQ Category:

No, Seam has something much more powerful: a conversation context. The Seam conversation context is propagated across redirects (even when no long-running conversation is in progress), so you can use the conversation context to store success messages and the like.

Furthermore, Seam manages a page context for each JSF page, which allows you to store objects across JSF POSTbacks without even starting a long-running conversation. This is the ideal context for short-lived AJAX operations, which often need to propagate state through several form submits.

3 comments:
28. Apr 2008, 17:25 CET | Link
shreekanth patil

Hi,

Am a Ruby on Rails developer, i was java developer also... will you please clarify me, want to know what makes java developer to use RoR, or a RoR developer to use jboss Seam ?

please clarify...

Thanks, Shreekanth patil

ReplyQuote
16. May 2008, 09:04 CET | Link
Brain
Brain wrote on Apr 28, 2008 05:25 PM:
Hi, Am a Ruby on Rails developer, i was java developer also... will you please clarify me, want to know what makes java developer to use RoR, or a RoR developer to use jboss Seam ? please clarify... Thanks, Brain

Click HELP for text formatting instructions. Then edit this text and check the preview.

ReplyQuote
18. Oct 2008, 15:00 CET | Link
rabi

you can use both its your(developer) choice. ROR is not scalable. For complex apps or enterprise apps use jboss seam with jboss 5.

ReplyQuote
Post Comment