"ALRubinger" wrote : ...
| * Add new internal callback mechanisms for things like "prePassivate",
"passivationStarted", "passivationCompleted". Part of the contract of
the cache impl will be to implement these callbacks (thus allowing us to do whatever
blocking/locking or get notification in tests).
Wouldn't a dummy persistence manager be enough?
"ALRubinger" wrote : ...
| * WTF was I thinking with this horrid CacheFactory-per-impl design? Should better be
a configurable factory capable of creating any N Caches. Ditto for the
PersistenceManagerFactories. I'll have to change up the relevant jboss-beans.xml to
fix this as well.
What I really would like to see is a deployer which takes cache metadata (@CacheConfig)
and creates a cache based on that. Which we then inject into the container using @Inject
with component scope.
That would require the container to be a MC component as well though. See embedded ejb
deployers.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185625#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...