Manik Surtani wrote:
On 26 Aug 2008, at 01:02, Jason T. Greene wrote:
> Btw, switching InvocationContext from a class to an interface is
> compile-time compatible, but it's not binary compatible. Something to
> think about...
Hmm yes, this could be a tough one. Most of the other places where
interfaces were introduced were internal stuff, so it wouldn't make a
difference - InvocationContext is exposed though. The interface is
needed though to be able to provide different behaviour for different
locking schemes. Perhaps making it an abstract class instead will have
to be the way to go. Ugly, but ...
Yeah, abstract class would fix the problem, and doesn't really have any
drawbacks. It's not as flexible as an interface, but the hierarchy for
locking models is fixed.
--
Jason T. Greene
JBoss, a division of Red Hat