db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Clute, Andrew" <Andrew.Cl...@osn.state.oh.us>
Subject Pattern between PersistenceBroker and PersistenceBrokerInternal
Date Wed, 30 Mar 2005 02:38:16 GMT
I see there was a new interface introduced named
PersistenceBrokerInternal, that separates some methods to a private
versus public interface. getProxyFactory() is on the internal interface
versus the external one.
My question is: in places where I want to access the ProxyFactory
sometimes objects will have references to PersistenceBrokers, and
sometimes they will have references to PersistenceBrokerInternal or
When the reference is to just PersistenceBroker, the code to get the
ProxyFactory looks like this:
When the reference is to something at least at the
PersistenceBrokerInternal level or lower, the code can be changed to
look like:
Is the plan to move references to PersistenceBroker that exist inside
the kernel to PersistenceBrokerInternal? Is there a pattern for when an
object holds a reference to the base PersistenceBroker interface versus
the internal one? This doesn't really have a huge impact, except from a
stylistic impact (a single indirection is 'cleaner' than a triple one).

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message