[JBoss JIRA] Created: (JBCACHE-1024) Move component construction out of Cache into Configuration to allow for better configurability
5:48 p.m.
Move component construction out of Cache into Configuration to allow for better
configurability
-----------------------------------------------------------------------------------------------
Key: JBCACHE-1024
URL: http://jira.jboss.com/jira/browse/JBCACHE-1024
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Elias Ross
Assigned To: Manik Surtani
There's a lot of logic embedded in CacheImpl.start() and create() as to what specific
object instances are created. For example, the JGroups Channel, or the
InterceptorChainFactory are directly constructed here and users have no control on this. A
bunch of other objects are also created based on class names and whatnot; these are
configurable to some extent but why does the CacheImpl need to know how to build these?
What really should be done is allow the Configuration class to play the role as factory
class, and take out all factory details from the Cache itself.
--
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
3:20 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1024) Move component construction out of Cache into Configuration to allow for better configurability
[ http://jira.jboss.com/jira/browse/JBCACHE-1024?page=all ]
Manik Surtani updated JBCACHE-1024:
-----------------------------------
Fix Version/s: 2.1.0.GA
Description:
There's a lot of logic embedded in CacheImpl.start() and create() as to what specific
object instances are created. For example, the JGroups Channel, or the
InterceptorChainFactory are directly constructed here and users have no control on this. A
bunch of other objects are also created based on class names and whatnot; these are
configurable to some extent but why does the CacheImpl need to know how to build these?
What really should be done is allow the Configuration class to play the role as factory
class, and take out all factory details from the Cache itself.
was:
There's a lot of logic embedded in CacheImpl.start() and create() as to what specific
object instances are created. For example, the JGroups Channel, or the
InterceptorChainFactory are directly constructed here and users have no control on this. A
bunch of other objects are also created based on class names and whatnot; these are
configurable to some extent but why does the CacheImpl need to know how to build these?
What really should be done is allow the Configuration class to play the role as factory
class, and take out all factory details from the Cache itself.
Move component construction out of Cache into Configuration to allow
for better configurability
-----------------------------------------------------------------------------------------------
Key: JBCACHE-1024
URL: http://jira.jboss.com/jira/browse/JBCACHE-1024
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Elias Ross
Assigned To: Manik Surtani
Fix For: 2.1.0.GA
There's a lot of logic embedded in CacheImpl.start() and create() as to what specific
object instances are created. For example, the JGroups Channel, or the
InterceptorChainFactory are directly constructed here and users have no control on this. A
bunch of other objects are also created based on class names and whatnot; these are
configurable to some extent but why does the CacheImpl need to know how to build these?
What really should be done is allow the Configuration class to play the role as factory
class, and take out all factory details from the Cache itself.
--
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
1:18 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1024) Move component construction out of Cache into Configuration to allow for better configurability
[ http://jira.jboss.com/jira/browse/JBCACHE-1024?page=all ]
Manik Surtani updated JBCACHE-1024:
-----------------------------------
Fix Version/s: 3.0.0
(was: 2.1.0.GA)
Move component construction out of Cache into Configuration to allow
for better configurability
-----------------------------------------------------------------------------------------------
Key: JBCACHE-1024
URL: http://jira.jboss.com/jira/browse/JBCACHE-1024
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Elias Ross
Assigned To: Manik Surtani
Fix For: 3.0.0
There's a lot of logic embedded in CacheImpl.start() and create() as to what specific
object instances are created. For example, the JGroups Channel, or the
InterceptorChainFactory are directly constructed here and users have no control on this. A
bunch of other objects are also created based on class names and whatnot; these are
configurable to some extent but why does the CacheImpl need to know how to build these?
What really should be done is allow the Configuration class to play the role as factory
class, and take out all factory details from the Cache itself.
--
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
9:58 a.m.
New subject: [JBoss JIRA] Resolved: (JBCACHE-1024) Move component construction out of Cache into Configuration to allow for better configurability
[ http://jira.jboss.com/jira/browse/JBCACHE-1024?page=all ]
Manik Surtani resolved JBCACHE-1024.
------------------------------------
Fix Version/s: (was: 3.0.0)
Resolution: Out of Date
Move component construction out of Cache into Configuration to allow
for better configurability
-----------------------------------------------------------------------------------------------
Key: JBCACHE-1024
URL: http://jira.jboss.com/jira/browse/JBCACHE-1024
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Elias Ross
Assigned To: Manik Surtani
There's a lot of logic embedded in CacheImpl.start() and create() as to what specific
object instances are created. For example, the JGroups Channel, or the
InterceptorChainFactory are directly constructed here and users have no control on this. A
bunch of other objects are also created based on class names and whatnot; these are
configurable to some extent but why does the CacheImpl need to know how to build these?
What really should be done is allow the Configuration class to play the role as factory
class, and take out all factory details from the Cache itself.
--
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
6525
days inactive
6951
days old
3 comments
2 participants
participants (2)
-
Elias Ross (JIRA) -
Manik Surtani (JIRA)