Werner Keil wrote on 10/17/11 17:12:
> * Deprecate JSF @ManagedBean -- the redundancy right now is very
> confusing for developers.
> * Deprecate Java EE 6 @ManagedBean -- it's hardly ever used and creates
> a lot of confusion.
>
>
> As a matter of policy, we don't deprecate anything except for the most
> serious errors. We can update the docs to make it clear what you should
> and should not use, but we're not likely to deprecate them.
>
>
> EE8 and beyond with true modularity will require a different approach to that,
> by declaring something "optional", thus allowing an app to function properly
> without having to use or load it.
> So unless something was crucial now in EE 7 I would probably postpone other
> cases and think about a good and reasonable module structure and profiles then.
Even with true modularity, we're trying to only make entire specs optional.
With a few exceptions, finer grained optionality will be harder for
developers to understand.