>>>>> On Fri, 17 Aug 2012 20:26:49 +0200, Frank Caputo <frank_at_frankcaputo.de> said:
EB> The use of CDI for all things managed bean was decided long ago, when
EB> CDI and JSF were both included in the JavaEE Web Profile. That decision
EB> cannot be revisited. JSF will still keep the practice of running just
EB> fine in straight up Tomcat, but features that use CDI, such as flows and
EB> the new @ViewScoped annotation (also in the flow package) will only work
EB> if CDI is present.
EB> The same is true for Bean Validation, the features that use Bean
EB> Validation only work if Bean Validation is present.
EB>
KM> That makes sense, but why do we need a new annotation? Can't we just have
KM> ViewScope be picked up by CDI if it's in the classpath?
EB> Because I plan to deprecate javax.faces.beans at some point after 2.2.
FC> Will we then require CDI? If someone doesn't use CDI and wants a
FC> ViewScope, she will have to use deprecated API, right?
I'll say this instead. One must use the JavaEE Web Profile to use the
new @ViewScoped feature, otherwise, one must use the deprecated API.
Ed
--
| edward.burns_at_oracle.com | office: +1 407 458 0017
| homepage: | http://ridingthecrest.com/