Reported by Vamsi

TARGET: sca-jee-1.1-spec-wd05.doc
Section 6.4 Using Web Modules as Implementation Types

DESCRIPTION:
The table after line 716 lists
javax.servlet.http.HttpSessionBindingListener as one of the event listeners
that must be supported for dependency injection.
HttpSessionBindingListener is different from other listeners in that
HttpSessionBindingListener need not be specified in web.xml.
HttpSessionBindingListener gets activated automatically when an object of
that type (implementing HttpSessionBindingListener actually) is bound to
HttpSession. Other listeners are specified in web.xml and their
instantiation is done by the web container. Since web.xml does not specify
HttpSessionBindingListeners, at deployment time, the web module builder
does not even know if there is any HttpSessionBindingListener that it
should process to support dependency injection. In other words,
HttpSessionBindingListeners are not managed objects and only things that
can plausibly have container mediated dependency injection are the objects
the container creates.

PROPOSAL: From the table after line 716, remove
javax.servlet.http.HttpSessionBindingListener from the list of artifacts
that are supported for dependency injection.