[OASIS Issue Tracker] Commented: (SCAJ-17) SCA JEE Is dependency injection for HttpSessionBindingListener possible?

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/SCAJ-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=29616#action_29616 ] 

Anish Karmarkar commented on SCAJ-17:
-------------------------------------

This is OSOA JIRA issue 116

Original email at:
http://lists.oasis-open.org/archives/sca-j/200812/msg00067.html

opened Aug 21 2009 telecon

resolved with proposal in JIRA - Aug 21 2009 telecon

applied in WD06: http://www.oasis-open.org/committees/download.php/34200/sca-jee-1.1-spec-wd06.pdf


> SCA JEE Is dependency injection for HttpSessionBindingListener possible?
> ------------------------------------------------------------------------
>
>                 Key: SCAJ-17
>                 URL: http://tools.oasis-open.org/issues/browse/SCAJ-17
>             Project: OASIS Service Component Architecture / J (SCA-J) TC
>          Issue Type: Bug
>          Components: Java EE Integration Specification 
>    Affects Versions: 1.1
>            Reporter: Anish Karmarkar
>             Fix For: 1.1
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira