[ http://jira.jboss.com/jira/browse/JBCACHE-1156?page=comments#action_12384259 ] Brian Stansberry commented on JBCACHE-1156: ------------------------------------------- A pretty reasonable version of what I'm thinking about is now in package org.jboss.cache.registry. I'm trying to keep this simple, since in many ways it's not a true JBC concern. I'd just do it in the AS, but it's needed for standalone Hibernate, which can't depend on the AS. I'll likely want to use the same interfaces for session mgmt stuff in the AS, so I don't want this stuff in Hibernate, since session mgmt has nothing to do with Hibernate. So, putting it in JBC makes the most sense. Given the above, I thought the best approach to take was to define a couple basic interfaces that provide the API needed by Hibernate. Then do a basic impl that meets the needs of standalone Hibernate. If I decide I want to do more complex stuff inside the AS, I can can expand upon this in the AS codebase. This is pretty much ready to be resolved, other than I might think of a couple more unit tests. -- 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

[ http://jira.jboss.com/jira/browse/JBCACHE-1156?page=all ] Manik Surtani updated JBCACHE-1156: ----------------------------------- Fix Version/s: 2.1.0.CR2 -- 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