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.
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.
Created: 18. Jan 2008, 18:40 America/New_York (Christian Bauer)
Last Modified: 16. Sep 2011, 08:10 America/New_York (Shane Bryzak)
Revisions: (Initial Revision)
Diff
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
you can use both its your(developer) choice. ROR is not scalable. For complex apps or enterprise apps use jboss seam with jboss 5.
After 1 year of develop with Seam I can reply:
Does seam replace the RoR ?
LOL!! :-)
Seam obviously does not replace RoR b/c you can deploy both Seam and RoR apps on JBoss 5 AS...
The myth that is just that: a myth.
Anybody who claims that this is true has never actually used Rails in any serious context, and probably doesn't know xing.com, twitter.com or yellowpages.com (just to name a few).
There's room for all of us, guys, stop spreading FUD.
Funny, after a year or so, I've read ruby DID have scaling issues in most of those companies you listed.