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

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

By: VENKAT

VENKAT — Mon, 01 Feb 2010 11:08:30 +0000

Hi
Can you also provide an example Using jboss seam framework which uses CDI, JPA ,Facelets, Validator and EJB 3.1

By: Daniel

Daniel — Fri, 15 Jan 2010 13:39:11 +0000

my Junit test that tests fireing CDI events fails with pure JavaSE. But maybe I did something wrong. Thanks for the Arquillian hint, I will check this out.

Daniel

By: Andy Gibson

Andy Gibson — Fri, 15 Jan 2010 03:38:26 +0000

Thank Daniel,

I’m currently working on a larger tutorial application for JSF/CDI and I hope to make testing a part of that.
Off the top of my head, CDI code can run in Java SE so you should be able to bootstrap CDI and execute methods in CDI beans.

If you use EJBs it gets a little more tricky because then you also need to involve an EJB container such as the JBoss micro-container.

The JBoss Arquillian project may be of interest to you as it lets you test your code inside the container. You are right though, some of this stuff is a little unclear. I’ll make a note to make sure I cover it in the future,

Thanks again,

Cheers,

Andy Gibson

By: Daniel

Daniel — Thu, 14 Jan 2010 20:30:17 +0000

Hi Andy,

thank you very much for your awesome CDI examples. You are really doing a great job!
I am sure CDI will play a very important role in JavaEE 6. However, has anyone thought of how to test CDI code with simple Junit Tests? Do you have any idea?