8.5.1 "In a Java EE 5 environment, the Web Bean manager is not
required to support an active event context during timeout method
Probably should say request context
2.5.1 All standard Web Beans defined by this specification, and
provided by the Web Bean manager, are defined using the @Standard
deployment type. For example, the Conversation object defined in
Section 8.5.4, “Conversation context life- cycle” and the Manager
object defined in Section 4.8, “The Manager object” have this
deployment type. No Web Bean may be declared with the deployment
type unless explicitly required by this specification.
Maybe state what happens if one is?
2.5.5 Default deployment type
Doesn't explicitly say what the default deployment type of a non-XML-
defined Web Bean is.
2.7.1 Defining new stereotypes
Most of these statements say that a DefinitionException is thrown when
if the stereotype doesn't meet these rules, apart from
A stereotype may declare at most one scope type.
A stereotype may declare at most one deployment type.
184.108.40.206 Declaring a Web Beans constructor
If a simple Web Bean defined using annotations does not explicitly
declare a constructor using @Initializer, the constructor that
accepts no parameters is the Web Bean constructor.
It is possible to call constructors by reflection on inner classes,
but it requires you to rely on the (AFAIK unspecified) behaviour that
the inner class instance holds a reference to it's parent instance in
the "this$<x>" field, where
x = (level-of-nesting - 1)
3.6 An injected field is a non-static, non-final field of a Web Bean
implementation class, of a Servlet, or of any EJB session, singleton
or message driven bean class.
Maybe should state what the behaviour is if you put a binding
annotation on a static or final field? e.g. undefined.