[
https://jira.jboss.org/jira/browse/JBAS-5945?page=com.atlassian.jira.plug...
]
Brian Stansberry commented on JBAS-5945:
----------------------------------------
Change is a bit more complex than what's in the JIRA description. What's going on
in initAfterLoad() is really three things:
1) Storing refs to the session Manager and some of its components. This is eliminated; the
session no longer drops its refs via serialization, so it already has them.
2) populateAttributes(). Moved into update(), with real work actually done in the
ha-server-cache layer.
3) Activation notifications. This is still called by JBossCacheManager, but we just use
the existing notifyDidActivate method.
Make JBossCacheClusteredSession.initAfterLoad() part of an override
of update()
-------------------------------------------------------------------------------
Key: JBAS-5945
URL:
https://jira.jboss.org/jira/browse/JBAS-5945
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Clustering, Web (Tomcat) service
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Minor
Fix For: JBossAS-5.0.0.GA
This method is called after update(...) is called and its functionality can be made part
of that call rather than having JBossCacheManager call it separately.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira