Invalid diagnostic on a field in a managed bean

[turkeylurkey]

Description:

The fix for issue #444 introduced a new diagnostic but this behaviour is not required by the spec.

Specification:

The specification states:

If a managed bean has a non-static public field, it [the managed bean] must have scope @Dependent. If a managed bean with a non-static public field declares any scope other than @Dependent, the container automatically detects the problem and treats it as a definition error.

We should not generate a diagnostic for a field with a scope declaration. The second sentence in the quote above is not a separate rule, it specifies the container behaviour when the rule of the first sentence is broken.

Type of language feature proposed:

Select all that apply

• diagnostic
• quick-fix
• snippet
• other, please specify: