This week's book giveaway is in the OCPJP forum. We're giving away four copies of OCA/OCP Java SE 7 Programmer I & II Study Guide and have Kathy Sierra & Bert Bates on-line! See this thread for details.
I'm new to Seam and I know this is heresy, but I'm wondering if Seam as a technology is too important for JBoss to "own"?
Just consider the multitude of questions about JBoss 4.2.0.GA and Seam 1.2.1.GA. JBoss released the 4.2.0.GA app server without any regard to the Seam examples working on it - just when developers are really starting to tune into Seam.
Furthermore, I'm sure the other app server vendors would love to promote Seam as a technology, but are hesitant to do so for fear of undercutting their own app server offering. I have no doubt Seam-clones will soon start appearing under more generic open source umbrellas. (Some might argue Seam borrows a lot from other open source offerings like Spring 2.x.)
I know Gavin King, creator of Seam, now works for JBoss, but am worried that Seam may become too closely associated with JBoss, the app server.
-- jj [ June 05, 2007: Message edited by: J.J. Jackson ]
Exactly, Seam is not owned by JBoss, Seam is open source and fully complies with the LGPL as Michael puts it.
You can always look at it as an association between Seam and AS, but know that you are making that up. How do you feel about Hibernate, Are all the other vendors running away from Hibernate because it is under the JBoss umbrella. No, and they would be stupid if they did run away.
More importantly, we have always intended Seam as a way to advance the standards. Somebody has to develop the technology that tomorrow's standards are based on, right? Seam has already had a huge impact on EJB3 (many things in EJB3 were designed the way they were specifically to support the ideas Gavin had for Seam). We have spearheaded big changes in JSF and in the next round of EE 5 specs. And, of course, don't forget about the WebBeans JSR.
So yes, Seam is too big for just JBoss. We've never seen this a proprietary technology (think spring) but as something that will pave the way for future EE standards.