Hi Ed,
Am 16.08.2012 um 16:12 schrieb Edward Burns:
>>>>>> On Mon, 13 Aug 2012 12:16:15 -0400, Kito Mann <kito.mann_at_virtua.com> said:
>
> KM> On Thu, Aug 9, 2012 at 9:50 AM, Edward Burns <edward.burns_at_oracle.com>wrote:
>
> 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?
>
> Because I plan to deprecate javax.faces.beans at some point after 2.2.
Will we then require CDI? If someone doesn't use CDI and wants a ViewScope, she will have to use deprecated API, right?
Ciao Frank
>
> Ed
>
> --
> | edward.burns_at_oracle.com | office: +1 407 458 0017
> | homepage: | http://ridingthecrest.com/
>