[jboss-dev-forums] [Design of EJB 3.0] - EJBTHREE-1290, MCDependencyPolicy interface

scott.stark@jboss.org do-not-reply at jboss.com
Wed Apr 16 06:45:43 EDT 2008


As part of EJBTHREE-1290 where we want to change the dependency on the ejb container name to be based on demand/supply of the ejb container jndi name, I want to make MCDependencyPolicy a proper interface: 


  | public interface DependencyPolicy
  | {
  |    public void addDependency(String dependency);
  |    public void addDatasource(String jndiName);
  | }
  | public interface MCDependencyPolicy extends DependencyPolicy
  | {
  |    public void addDemand(DemandMetaData dependency);
  |    public Set<DemandMetaData> getDemands();
  |    public void addSupply(SupplyMetaData smd);
  | }
  | 

I want to drop a number of methods from the current MCDependencyPolicy class.
- addDependency(Class businessInterface) addDependency(String ejbLink, businessInterface), addSupply(businessInterface) as this is something that should have been resolved to a container by the deployment resolver.
- addJNDIName(String name) which creates a dependency on an ejb mapped name also becomes redundant and should be dropped.

The current casting to JBoss5DependencyPolicy would be a reliance on the extended MCDependencyPolicy interface instead which would allow for alternate implementations in jbossas vs standalone.



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

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



More information about the jboss-dev-forums mailing list