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?
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).