This week's book giveaway is in the Agile and Other Processes forum. We're giving away four copies of Real-World Software Development: A Project-Driven Guide to Fundamentals in Java and have Dr. Raoul-Gabriel Urma & Richard Warburton on-line! See this thread for details.
Hi. Well, I don't want to start such a religious thread but do you prefer Seam or Shale ? Seam looks cool to me, it is created by Gavin King under JBoss umbrella with a lot of cool features for Ajax and BPM. Why Seam ? Shale on the other hand, created by Apache folks (I like this foundation). Like other Apache projects, Shale equibed with many powerful features (my favorite is Clay which reminds me of Tapestry). So, what to learn ? Yes, maybe each framework is suitable for some kinds of applications but did you tried them ? What is your impression ? JSF frameworks: Shale and Seam
Originally posted by John Todd: .. prefer Seam or Shale ?
Seam, by far!
I have evaluated both. I started with Shale, played with it a bit then I switched over to Seam and never looked back.
Seam is very aggressive in their releases. They have new updated releases out with major features (requested by users) every month. Shale is VERY VERY slow in getting their releases out. Seam support for conversational model is the main key for me, and something I can't go back to. Shale uses something similar called dialogs, but I find the basic implementation a little buggy. As well, Seam supports other useful features like atomic conversations, persistence-managed contexts, JSF-hibernate validations integration, etc. It's really a no-brainer.
Do Seam has a long learning curve ? JBoss products are cool, but they are lacking some good online documentation (JBoss AS, jBPM).
posted 13 years ago
As if Apache Shale have any *good* documentation. Their user forum is not even that active--they get about 2 to 3 unique posts a day.
Seam's documentation is pretty good IMO. The reference documentation was all I used to get started. But most of the knowledge was found in the source code. Seam comes with like 10 examples out of the box. Took me about a week to figure everything out.
As for JBoss AS, it's pretty easy to get your apps running on it so you should just start with that instead of worrying about tuning it. Seam comes with a utility call seam-gen that does all the generating and deploying of your application to JBoss AS.
As I expected, it is hard to start using and developing Seam application (at the level of knowing what are the required libs, deploying on Tomcat through the embedded EJB3 support). JBoss software is complex !
Why is the word "abbreviation" so long? And this ad is so short?