"bsmithjj" wrote:
We like the Seam framework a lot but we don't want to be in the business of maintaining frameworks. We are, however, paying customers of JBoss (now Red Hat) - we even sent a good number of people to JBoss world for 2 years in a row (no JBoss world this past summer :-( ) - so from my perspective, we're doing our part to be payed customers - we're not looking for a free ride. I think I would be less willing to put my vote in for Seam-specific support after watching the 1.3.0 Alpha disappear - just too much volatility in how it evolves.
We understand that. What Christian was trying to say is basically that, you can be assured to have a supported version of Seam 1.2 for X years (I think it's the typical 3+2, but it needs to be checked) as part of the JBoss Enterprise Application Platform.
As a project team however we still have to group our task force where we think it will be most valuable for our customers and users as a whole. With that in mind and because of the support for Seam 1.2 in JEAP, we decided to rebrand 1.3 to 2.0 and make compatibility changes for a better future. Looking at the feature set of Seam 2, I think there is no need to regret Seam 1.3.
cheers
