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

bstansberry@jboss.com do-not-reply at jboss.com
Wed Nov 7 12:58:02 EST 2007


"scott.stark at jboss.org" wrote : "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.
  | 

There's 2 issues here:

1) The use of org.jboss.ha.framework.interfaces.LoadBalancePolicy in this annotation leaks the legacy  org.jboss.invocation.Invocation class.  My plan for dealing with this is to introduce a parent interface that doesn't include the method that leaks that type.  See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120423.  I need to do a serialization/deserialization test to confirm that won't break compatibility with existing clients.  This I'll get done this week.

2) Where does @Clustered go?  To me it seems like it would go in the ha-client library that I started to break out of the main AS codebase a while back.  That breakout was going to have to be done when we break ejb3 out of the AS codebase, and can be done sooner if need be.

Problem with this is the name of the annotation is @org.jboss.annotation.ejb.Clustered -- not a very generic name.

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

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



More information about the jboss-dev-forums mailing list