You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Jim Marino (JIRA)" <ji...@apache.org> on 2006/03/02 09:33:41 UTC

[jira] Commented: (TUSCANY-51) Tomcat integration should provide Session scope context

    [ http://issues.apache.org/jira/browse/TUSCANY-51?page=comments#action_12368458 ] 

Jim Marino commented on TUSCANY-51:
-----------------------------------

Do you mean provide integration for session event notification? There is a servlet filter that does this which has code that could be re-used.  It actually does lazy-access of session id's so a session is not created if session-scoped services are not accessed during a request. Another touchpoint could be for state replication. I think we should look at a general change-tracking mechanism for the runtime internals (possible based on SDO using a binary diff format) to do this as well as implement a "Tuscany" binding. 

> Tomcat integration should provide Session scope context
> -------------------------------------------------------
>
>          Key: TUSCANY-51
>          URL: http://issues.apache.org/jira/browse/TUSCANY-51
>      Project: Tuscany
>         Type: Bug
>     Reporter: Jeremy Boynes

>
> This function is currenty not performed by the integration. One way to implement this is to check for a session in the TuscanyValve on each request. A more efficient way would be to integrate the HttpSessionScopeContext with Tomcat itself (perhaps as a custom Manager implementation)

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