[jboss-dev-forums] [Design of POJO Server] - Re: Leaking annotation API

[scott.stark@jboss.org]

"ALRubinger" wrote : 
  | @Clustered depends on org.jboss.ha.framework.interfaces.LoadBalancePolicy from trunk/cluster
  | 
This is also specific to a particular invocation implementation. This really can't be generically in ejb3 since its an aspect related to remoting. Its possible the server does not support anything but local ejbs, so ejb3 should not be providing this aspect.

"ALRubinger" wrote : 
  | @PoolClass has:
  | Class<? extends Pool> value();
  | 
  | ..where Pool defines:
  | 
  | BeanContext<?> get();
  | 
  | ..and BeanContext exposes many internals: Container, etc.
  | 
This is way too implementation specific for a client api. I would say you need to follow the factory approach suggested by Adrian where a client PoolFactory annotation provides the name of a registered Pool implementation. These would be registered with the factory in the ejb beans setup.


  | @PoolFactory(type="EntityInstancePool",maxSize=10,timeout=300)
  | 


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

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