Replace @ManagedBean with @Named

[agoncal]

In your JSF example, you use the JSF @ManagedBean and @RequestScoped annotations. Both have been pruned in Java EE 7 and should be deprecated in next version. Instead you should use the CDI @Named and the CDI @RequestScoped.

[TheCoder4eu]

Hi Antonio,
thank you very much for pointing this out, I'll change it ASAP!

[stephanrauh]

Bonsoir Antonio,

first of all I'm glad you discovered our project!

As for your suggestion: actually, I had thought quite a few minutes about which annotations to choose. You know, the old JSF annotations may have been deprecated in Java EE 7, but there's no @deprecated in the JSF 2.2 source code, so Eclipse won't tell me about it. BTW, BootsFaces is also targeted at JSF 2.0 and 2.1, both of which don't support CDI. As a consequence, the dependency tree of our showcase project doesn't include the javax.inject.jar.

Another consideration is Spring. Personally, I'm very fond of CDI, but I didn't want to drive the Spring developers away, so I decided to use the old annotations. But maybe you're right: these days Spring supports @nAmed and @Inject, too.

Best regards
Stephan

[stephanrauh]

Funny thing is my new PollDemoBean accidentially uses the CDI annotations. So much for "I've thought about it thoroughly" :).

[agoncal]

Yes, Spring uses @Named and @Inject. Unfortunately it doesn't support the CDI @RequestScoped. Java EE being built more and more on CDI, and Spring that doesn't support it... I think that, unfortunately, both programming model will start to shift and you will have to choose one or the other :o(

[stephanrauh]

Maybe we should think about a pull request enhancing the SpringBeanAwareELResolver. It's not difficult to add the view scope to Spring, let alone the CDI request scope (see ViewScope and faces-config.xml).

[TheCoder4eu]

The classes using @ManagedBean are:

src/java/org/primefaces/showcase/view/input/CalendarView.java:@ManagedBean
src/java/net/bootsfaces/demo/BarcodeBean.java:@ManagedBean
src/java/net/bootsfaces/demo/LoremIpsumBean.java:@ManagedBean
src/java/net/bootsfaces/demo/SettingsBean.java:@ManagedBean
src/java/net/bootsfaces/demo/InformBean.java:@ManagedBean
src/java/net/bootsfaces/demo/TestBean.java:@ManagedBean(name = "testBean")
src/java/net/bootsfaces/demo/ClockBean.java:@ManagedBean
src/java/net/bootsfaces/demo/ItemBean.java:@ManagedBean
src/java/net/bootsfaces/demo/SemaphoreBean.java:@ManagedBean
src/java/net/bootsfaces/demo/DateBean.java:@ManagedBean(name = "dateBean")
src/java/net/bootsfaces/demo/CarBean.java:@ManagedBean
src/java/net/bootsfaces/issues/issue78/SoccerTeamBean.java:@ManagedBean

The classes using @RequestScoped are:

src/java/net/bootsfaces/demo/LoremIpsumBean.java:@RequestScoped
src/java/net/bootsfaces/demo/SettingsBean.java:@RequestScoped
src/java/net/bootsfaces/demo/InformBean.java:@RequestScoped
src/java/net/bootsfaces/demo/TestBean.java:@RequestScoped
src/java/net/bootsfaces/demo/ClockBean.java:@RequestScoped
src/java/net/bootsfaces/demo/ItemBean.java:@RequestScoped
src/java/net/bootsfaces/demo/DateBean.java:@RequestScoped

[TheCoder4eu]

Btw, Antonio, I see you have made a presentation titled "To inject or not to inject: CDI is the question":
choosing the right annotation is not always straightforward in JEE...

[agoncal]

"choosing the right annotation is not always straightforward in JEE". Yes, I agree. I'll think of something simple... maybe a matrice with service == annotation (eg. transaction == @transactional, injection == @Inject). Something to blog about ;o)

[zhedar]

I would like to resurrect this issue, because as of JSR 330 CDI is part of Java EE 6, which is the minmal version BootsFaces supports. So using CDI should be an option for everyone who uses JSF 2.0+, since it's part of the same JEE specification.
The only part of CDI, which requires JSF 2.2 and therefore Java EE 7 is CDI's missing support of JSF's ViewScoped.

If we like to keep supporting JSF 2.0 in this showcase, we might just use OmniFaces' ViewScoped implementation, which offers CDI ViewScoped support in both JSF 2.0 and 2.1. We have a dependency to OmniFaces anyway, so might as well use that.

[stephanrauh]

BootsFaces supports Java 6, not JavaEE 6 :). Modern application servers have become very good, but there are still a couple of developers using a pure Tomcat or even Spring with JSF.

[zhedar]

I misinterpreted BootsFaces is targeted at Java EE 6/7 and requires a Java 1.6 or later VM. in the requirements then, my bad. I just know, that PrimeFaces requires the jee6-spec and therefore it would be something, that most libraries do.

However shouldn't be those limitation only be applied to the project itself? I just thought CDI won't hurt the showcase. But I also somehow understand the decision to keep things minimal.