Comments on: Getting Started with JSF 2.0 and CDI part 3 – Events

By: Pageraz

Pageraz — Wed, 23 Feb 2011 11:52:23 +0000

Thank you very much Andy for this amazing article about CDI
i just read about it in netbeans site
i think it’s the first perfect tutorial which describe the CDI features
i just linked it in my Java EE Professional Articles group on facebook

thankx

By: Christina S

Christina S — Thu, 20 Jan 2011 01:08:05 +0000

Thank you so much your awesome tutorial. You saved me a lot of frustration!! Seriously, thank you!!

By: DonM

DonM — Wed, 13 Oct 2010 18:56:03 +0000

Nice 3 parts … Learning by example and trying out the code is only way to get a firm grip on some of this stuff. Will there be a part 4, part 5, etc?

By: Andy Gibson

Andy Gibson — Sun, 22 Aug 2010 03:27:32 +0000

Thanks Bob, glad you liked it,

If you want to look at more Weld/JSF samples take a look at the Knappsack maven archetypes (they are available in the central maven repo)

There are two demo apps there, one that is servlet based with Jetty and another for Java EE 6 application servers.

See http://www.andygibson.net/blog/news/knappsack-archetypes-are-now-in-the-maven-central-repository/ for more details

Cheers,

Andy Gibson

By: BobM

BobM — Sat, 21 Aug 2010 22:37:16 +0000

After finding and finishing your 3-part tutorial, let me add my thanks for a great piece of work. Now both annotations and bean management have snapped into focus.
Using your work, I was inspired to check out the Weld – JSR-299 Reference Implementation document and use it’s Chapter 3 example to cobble together a NB project which mostly worked (once I remembered the beans.xml keystone).
One JSF/Weld element didn’t work: proper EL resolution from for “currentUser” that was set up with a @Produces method in the “login” session bean. That identifier is not on the JSF EL-resolver’s radar when rendering as Weld suggests it will:
“Or we can reference the current user in a JSF view:”


   signed in as #{currentUser.username}

Were the currentUser reference was produced by:

@Produces @LoggedIn User getCurrentUser() { return user; }

I wish you luck with next opus with more elaborate JSF/Weld cooperation. Thanks again.

By: Andy Gibson

Andy Gibson — Tue, 15 Jun 2010 03:54:23 +0000

Well that would work, but that would make the bean Dependent scoped which is probably the wrong thing to do, especially if they are used in other placed in the app where they might need request or conversation scopes.

Here’s the Jira issue for it :

https://jira.jboss.org/browse/WELD-15

It seems it is fixed, however, if you are using Glassfish, last I looked they are still using the old versions of Weld so its a matter of waiting for them to upgrade it (there was a change in the API so it means that it is a bit more involved that just building and replacing the osgi bundle).

By: GabiC

GabiC — Thu, 03 Jun 2010 15:20:07 +0000

Hey Andy,

Thanks for the great example.
On the ScheduledProcessor part I was getting some errors when the scheduled job was executing. My idea was to comment out the @RequestScoped annotations, as it is not web based anymore and it seems it works fine.
Was this the right/best thing to do?

Thanks,
Gabriel

By: Andy Gibson

Andy Gibson — Sat, 20 Mar 2010 14:38:27 +0000

Hey Cornelius, the save and invalidated annotations are your own qualifiers, something like :

@Retention(RetentionPolicy.RUNTIME)
@Target({FIELD,METHOD,PARAMETER,TYPE})
@Qualifier
public @interface Invalidated {}

Looking at the code, I don’t believe the @save annotation is needed, it probably got pulled into the source as I was looking at another kind of example that never made it into the final document (possibly, some mechanism to inject the file error handler by marking the injection point with the save annotation).

Cheers,

Andy

By: cornelius

cornelius — Sat, 20 Mar 2010 13:06:57 +0000

@Save ant @Invalidated are unknown…
What library I need?

By: Andy Gibson

Andy Gibson — Mon, 08 Feb 2010 06:32:03 +0000

That would be a tall order. Getting Seam running with JPA, Facelets, Validator and EJB 3.1 should be doable just by deploying a Seam app on the latest version of glassfish (AFAIK JBoss 6 m1 doesn’t support EJB 3.1) . Getting CDI incorporated would be difficult as well as ill defined (are you trying to use CDI conversations and injection?). Seam 3 will be built on CDI and all that good stuff and come in a more standards friendly manner.

Cheers,

Andy