ISSUE-116: Is dependency injection for HttpSessionBindingListener possible?

http://www.osoa.org/jira/browse/JAVA-116

Dave Booz

STSM, BPM and SCA Architecture

Co-Chair OASIS SCA-Policy TC and SCA-J TC

"Distributed objects first, then world hunger"

Poughkeepsie, NY (845)-435-6093  or  8-295-6093

e-mail:

C Vamsi ---12/12/2008 05:19:40 AM---TARGET: sca-jee-1.1-spec-wd05.doc Section 6.4 Using Web Modules as Implementation Types

From:

C Vamsi <>

To:



Date:

12/12/2008 05:19 AM

Subject:

[sca-j-jee] NEW ISSUE: Is dependency injection for HttpSessionBindingListener possible?

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.

++Vamsi

Apache Tuscany Committer  http://tuscany.apache.org

Apache Geronimo Committer and Member of PMC  http://geronimo.apache.org

---------------------------------------------------------------------

To unsubscribe from this mail list, you must leave the OASIS TC that

generates this mail.  Follow this link to all your TCs in OASIS at:

https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php