JBossDeveloper

Hi Alexandr,
What is the errors? I know many people use it with primefaces3.0 and work fine.

Hi,

3 February 2011: ...I hope It will be done this month..... We are in June now

I really hate is was right with my estimations.....

Leo

Hello He Youlin,
I'm certainly willing to try your modifications and report the results. Is there any write-up that describes the process, or is it a matter of simply using your new jars?  

Hi Robert, Just do not add seam-debug.jar to your classpath and do not use richfaces3. You can use jsf2.0 or above,richfaces4 and primefaces2 above.

It need jsr303 beanvalidator also. You can use hibernate3.6,hibernate validator4.2

Hate to keep asking, but has all Seam2 development stopped?  This thread hasn't had a response since early May, and considering Seam 3 isn't ready for prime time some of us need to seriously consider taking a different development path.  Seam is a great product, but it doesn't appear Redhat is truly behind it.  This is very disappointing.

Hi Robert,

I have the same problem! Are we taken serious or what?

Leo

Robert,

Could you elaborate on the reasons that you feel Seam 3 is not ready for prime time?

Ken

I'v always understand it like Seam 2.2 is for JSF 1.2 and Seam 3 for JSF 2.X

Don't see the Problem. Seam is workin greate, much more stable and faster then Seam 2 does. Well it is a little bit hard gettin in it, but after learnin it is really more fun than Seam 2 (What I'v really liked but better live in future...)

Hi all,

I try to be open minded, but I can't. It's all about productivity, efficiency etc. I consider Seam 3 production ready when there is a full set of documentation, only smaller issues (eq bugs), excellent development tools etc. etc.

I agree that Seam 3 is a huge improvement, but there are a lot of customers out there who are not able or willing to make the switch. And be honest: do you really consider Seam Forge (beginning) user fiendly and would you rather have a decent Eclipse plugin? I would.

Leo

P.S. The Seam 3 forum has a comparable thread: Is Seam 3 production ready.

Leo

What about the current documentation for Seam 3 means it isn't a full set?  Let us know where there are gaps and we can look to fill them.

In what ways do you feel Seam Forge could be made more user friendly?

In terms of Eclipse, the latest JBoss Tools plugins with excellent CDI/Seam 3 support are now available for those preferring tools in the IDE.  Note that you can also run Seam Forge from within Eclipse using JBoss Tools.

Just trying to understand more specifically where the gaps are that need to be filled.

Ken

Florian,
That understanding may be true today, but that was not the official line several months or a year ago.  The claims were that Seam 2 supported JSF 2.  Then that changed.  Then it was going to support it.  Now, there's just silence.  And that's really the issue.  If the plan is to support JSF2, then do it.  It appears to be a solvable issue since He Youlin claims to have solved it.  Just scroll up to see his comments.  Given my clients, I would feel better if the modifications were part of an official release (no offense to Youlin). 

Robert Morse wrote on Jun 29, 2011 07:55:


Hate to keep asking, but has all Seam2 development stopped?  This thread hasn't had a response since early May, and considering Seam 3 isn't ready for prime time some of us need to seriously consider taking a different development path.  Seam is a great product, but it doesn't appear Redhat is truly behind it.  This is very disappointing.

Sorry, but I was on vacations and then I was catching with my working duties, Seam 2.3 is stil in WIP.

There is migrated git branch with experimental jsf2 support - experimental JSF2 support if you want to try it.

I announced migration to maven build system in our SVN branch at migrated SVN branch in May, this is the base for other things like jsf2 support.

Stay tuned,there will be also prepared some migration path on JBoss AS 7, which will be a BIG jump in productivity.

Leo van den Berg wrote on Jun 29, 2011 09:38:


Hi all,

I try to be open minded, but I can't. It's all about productivity, efficiency etc. I consider Seam 3 production ready when there is a full set of documentation, only smaller issues (eq bugs), excellent development tools etc. etc.

I agree that Seam 3 is a huge improvement, but there are a lot of customers out there who are not able or willing to make the switch. And be honest: do you really consider Seam Forge (beginning) user fiendly and would you rather have a decent Eclipse plugin? I would.

Leo

P.S. The Seam 3 forum has a comparable thread: Is Seam 3 production ready.

Hmm, if you would like to switch to Java EE 6, you have to learn the differences between Java EE 5 and Java EE 6. And Seam 2 migration to Seam 3 is the same in that.

For customers which want to stay with older Seam 2 in production, they still are not alone. Redhat supports it and will be at least for next 4 years. JSF2 support is different case still only community focus, I will work on it and welcome all help with that.

Finally don't forget that community projects like Seam2 and Seam3 are about community effort. Seam3 project is much better in growing and attracting community than Seam2 was and you can expect that some missing parts in documentation or missing integrations which was in Seam2 will be filled very soon by community members. Look for instance at Seam23MigrationHowToStart .

To sum up the current state, Seam 2.3 will try to fill a gap between old Seam 2 and new Seam 3 project, but only as a temporary bridge to some Java EE 6 things like JSF2 or now running on JBoss AS 7.

Ken Finnigan wrote on Jun 29, 2011 08:52:


Robert,

Could you elaborate on the reasons that you feel Seam 3 is not ready for prime time?

Ken

I like to upgrade to Seam 3, but Seam 3 still doesn't support Seam 2's mail and framework (e.g. EntityHome).