[weld-dev] JSF + CDI: @Named diff behaviour than @ManagedBean

Dan Allen dan.j.allen at gmail.com
Tue Dec 21 10:28:57 EST 2010


If you are using CDI, please do not use the JSF managed bean annotations
(@javax.faces.bean.*). JSF managed beans do not have any integration with
CDI because that spec was not properly aligned with the platform.

The CDI annotations give you everything you need as a drop-in replacement.
That was the original goal of CDI (it has become a lot more, thankfully).

If you are concerned that you'll accidentally use the JSF managed bean
annotations without realizing it, you can either:

- exclude the javax.faces.bean package from the allowed imports in your IDE
- use Seam Faces or MyFaces CODI, which both alias the JSF managed bean
annotations to CDI annotations (effectively intergrating the two
technologies).

I strongly recommend that you checkout the Weld reference guide for more
tips on how to use CDI beans and scopes.

Hope that helps,

- Dan Allen

Sent from my Android-powered phone:
An open platform for carriers, consumers
and developers.

On Dec 21, 2010 5:48 AM, "Sebastian E. Ovide" <sebastian.ovide at gmail.com>
wrote:

adding implements Serializable fixes that exception... but now it cannot
find the methods of the managed (named) bean...

I guess that must be another way to inject CDI into JSF...



On Tue, Dec 21, 2010 at 12:43 AM, Sebastian E. Ovide <
sebastian.ovide at gmail.com> wrote:
>
> no. It...
-- 
Sebastian E. Ovide





_______________________________________________
weld-dev mailing list
weld-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/weld-dev/attachments/20101221/1efd0fef/attachment.html 


More information about the weld-dev mailing list