Was there any consensus reach on what to do for this? There was a few emails
about it, the last one:
http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200612.mbox/[EMAIL
PROTECTED]
It wasn't very clear to me what the "resetting the object into the servlet
context if state change occurs on a session-scoped object" was about?
...ant
On 12/6/06, Jim Marino (JIRA) <tuscany-dev@ws.apache.org> wrote:
[
http://issues.apache.org/jira/browse/TUSCANY-973?page=comments#action_12456118]
Jim Marino commented on TUSCANY-973:
------------------------------------
This needs to implement semantics similar to conversational persistence
and not just use the ServletContext as a container for replication to work
properly. At a certain point, the servlet engine needs to be notified of a
series of changes through setAttribute. This is the same pattern we have
with conversational scope. We should also have a mechanism based on intents
that specify whether a particular instance should failover, otherwise, we
don't need to store it in the Servlet context.
> HttpSessionScopeContainer should use the HttpSession for session
persistance
>
----------------------------------------------------------------------------
>
> Key: TUSCANY-973
> URL: http://issues.apache.org/jira/browse/TUSCANY-973
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core
> Affects Versions: Java-M2
> Reporter: ant elder
> Assigned To: ant elder
> Fix For: Java-Mx
>
>
> The HttpSessionScopeContainer should use the HttpSession for session
persistance instead of the HashMap it currently uses
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
