[webbeans-dev] How does JSF deal with managed beans when Web Beans/299 is present?

[Dan Allen]

On Wed, Aug 5, 2009 at 6:44 AM, Pete Muir <pmuir at redhat.com> wrote:

>
> On 5 Aug 2009, at 00:16, Dan Allen wrote:
>
>
>> I think it's better to address this by disabling JSF managed beans when
>> 299 is present, rather than by creating extra rules about how the two
>> interact. Any reason to take the latter approach?
>>
>> My only concern here is that someone writes an application that they have
>> been deploying to Tomcat or Jetty and then they turn around and deploy it to
>> JBoss AS for production (or pre-production). All of a sudden, the playing
>> field changes. This seems like a very realistic scenario, especially for
>> people migrating.
>>
>
> Why would 299 come into play in this scenario. They would have to alter
> their app and add beans.xml surely?


Doh! You are right.

Then I agree, if JSR-299 is active then JSF managed beans become disabled.
That is much better than having to add both a beans.xml and changing some
configuration setting in JSF because it eliminates error.


>
> Or do you mean they were using Web Beans and JSF in Tomcat too? We fully
> intend to support the same behavior in Tomcat (disabling JSF managed beans).
>

Yes, very good.

-Dan

-- 
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://in.relation.to/Bloggers/Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/weld-dev/attachments/20090805/5a58854c/attachment.html