Comments on: Getting Started with JSF 2.0 and CDI in JEE 6 part 1

By: Paul Vincent

Paul Vincent — Sun, 14 Mar 2010 19:31:02 +0000

Thank’s Andy Gibson, for this preview of two of the best players actually : Seam, an evolution of JEE, transformed in the JSR-299, and Facelets, now the default view of JSF2.0.
Thank you very much, Seam (Gavin)

By: Andy Gibson

Andy Gibson — Mon, 08 Feb 2010 06:38:15 +0000

Apologies Daniel, I thought I had replied to your comment.

If it is the thing I think you are seeing, I believe this is an NPE on redeploy where it cannot restore the session state so the session data prior to the redeploy is lost. While this might be an error, its not one I care about to much since the redeploy works just fine, just the session information is lost which I can live with for the things I do with it. In short the answer is, no I don’t have a work around, it seems to be fixed though, but even if it isn’t in your current version, don’t worry about it unless having a reset session state on redeploy is a big deal.

Cheers,

Andy

By: Daniel

Daniel — Sun, 24 Jan 2010 06:01:49 +0000

How were you able to work around the problem one of your other readers submitted here: https://jira.jboss.org/jira/browse/WELD-350 (NPE on redeploy).

There is a comment 13/1 to say that it is fixed in trunk. Did you need to patch your GlassFish installation?

I have tried starting GlassFish with a different weld-osgi-bundle I found here:
http://oss.sonatype.org/content/groups/jboss/org/jboss/weld/weld-osgi-bundle/1.0.1-SNAPSHOT/

By: GlassFish v3 Resources and Links – Part 2 | Developer @ UniUrs

GlassFish v3 Resources and Links – Part 2 | Developer @ UniUrs — Sat, 16 Jan 2010 01:09:38 +0000

[...] Getting Started with JSF 2.0 and CDI in JEE 6 part 1 [...]

By: uberVU - social comments

uberVU - social comments — Sun, 27 Dec 2009 09:30:28 +0000

Social comments and analytics for this post…

This post was mentioned on Twitter by yigitdarcin: Nice article on JSF2.0 and CDI http://www.andygibson.net/blog/index.php/2009/12/16/getting-started-with-jsf-2-0-and-cdi-in-jee-6-part-1/...

By: Getting Started with CDI part 2 – Injection | Andy Gibson

Getting Started with CDI part 2 – Injection | Andy Gibson — Tue, 22 Dec 2009 18:44:31 +0000

[...] Articles « Getting Started with JSF 2.0 and CDI in JEE 6 part 1 [...]

By: Andy Gibson

Andy Gibson — Mon, 21 Dec 2009 19:14:56 +0000

Ah great stuff David, I really like the JSF support in Netbeans 6.8 and am looking forward to the new CDI support.

I think Netbeans 6.8 is providing better support and features for Java EE 6 than it has for any of the previous versions making it a really attractive environment for a really attractive platform.

By: David Konecny

David Konecny — Sun, 20 Dec 2009 22:46:47 +0000

Agreed, it is a shame auto completion does not work for CDI beans. I’m a member of NetBeans team which works on Java EE 6 support and I will make sure we fix it ASAP. CDI specification changed several times and we could not include support for CDI in NetBeans 6.8 because of time and resource constraints. I don’t know exact date when NetBeans CDI support module will be available, especially with coming Christmas break, but what I know is that it has already some other cool features like navigation from injection point to class being injected. Also the need to create beans.xml should be simplified by the IDE if not done automatically.

Thanks for your feedback,
David

By: Andy Gibson

Andy Gibson — Sat, 19 Dec 2009 19:37:59 +0000

Geraldo, yes, it’s a shame the auto completion in Netbeans doesn’t have CDI beans included which I’ve also mentioned in other posts. It’s a shame that just as standard JSF gets some nice auto completion, every is moving to (or should be moving to) CDI.

Ignacio, no idea on the error, it may depend on something else in your code as I haven’t experienced it. There are a number of examples (in the docs and I think on Gavins blog) about setting up a producer method to make a persistence context available in any CDI bean. Off the top of my head, it is as simple as creating a bean into which you put the persistence context and mark the getEntityManager() method as a producer. (something like that).

By: Ignacio de Córdoba

Ignacio de Córdoba — Sat, 19 Dec 2009 00:33:38 +0000

Maybe it’s related to the severe warning shown when using javax.ejb.Singleton (Weld javax.inject.Singleton doesn’t show that error) Any idea why?

Anyway, I can also get JEE injection services (@PersistenceContext for example) when using @ManagedBean. @Named annotation will just return an instance of the class without any JEE services.
symbol: TYPE location: class com.cervatoh2.elaphus.ejb.ElaphusManagerBean