[JBoss JIRA] Created: (JBCACHE-697) PojoCache Collection sub-field when detached will revert back to the original reference
by Ben Wang (JIRA)
PojoCache Collection sub-field when detached will revert back to the original reference
---------------------------------------------------------------------------------------
Key: JBCACHE-697
URL: http://jira.jboss.com/jira/browse/JBCACHE-697
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: PojoCache
Reporter: Ben Wang
Assigned To: Ben Wang
Fix For: POJOCache
In PojoCache 1.4, when a Pojo has a Collection sub-object, it will dynamically replace the reference with a corresponding ClassProxy one such that we can intercept the Collection APIs. This is in attached state. When the POJO is detached, we would simply keep the ClassProxy reference but rather point the interceptor to the original reference. This works fine except when the POJO is meant for remoting as ClassProxy is not Serializable and not for direct manipulation.
The solution is when a POJO is detached, it will dynamically swap back the original reference and discard the ClassProxy. This way, it is semantically similar to a regular POJO as well. There will be no issue of Remoting, as an example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 10 months
[JBoss JIRA] Created: (JBAS-3720) Change structure of ClusteredSSO data in tree cache to avoid lock issues
by Brian Stansberry (JIRA)
Change structure of ClusteredSSO data in tree cache to avoid lock issues
------------------------------------------------------------------------
Key: JBAS-3720
URL: http://jira.jboss.com/jira/browse/JBAS-3720
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Clustering, Web (Tomcat) service
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.CR1
For each SSO entry, their should be child node per server where the SSO has been used. This is different from the current where all the session data for an SSO is in one node. The data map in each child node would hold the session ids of the sessions active on that server.
This kind of structure avoids most lock contention between different servers.
Can't do this in 4.0.x as it prevents interoperation with earlier releases.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 10 months