[jboss-dev-forums] [Design of EJB 3.0] - Re: New Build Artifact - EJB3 External API

[wolfc]

The current @Cache should not be in ext-api. Maybe we'll keep the construct in core.

So for a bean developer we get either:
@Cache("NoPassivationCache")
or
@CacheFactory("NoPassivationCache")

By making the CacheFactoryRegistry a generic interface:
interface CacheFactoryRegistry<T> {
  |    CacheFactory<T> getFactory(String name);
  | }
We can have typesafety in the core.

On a related note: we still need something to pass in the cache configuration.
interface CacheFactory<T> {
  |    Cache<T> createCache(AnnotedElement element);
  | }

I don't like it that we have two different @CacheConfig annotations.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102836#4102836

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102836