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 Serialization of Proxies revisited
Date Fri, 01 Apr 2005 17:45:41 GMT
I am sure this conversation has been had before, but with the
introduction of the new ProxyFactory, I think it is worth revisiting.
The question is: what is the best way to handle the serialization of
Proxies (both reference and collections).
The current pattern was to let the JDK Proxy serialize as normal, with a
reference to a PBKey. After being restored and interrogated, the Proxy
would reconnect to a PersistenceBroker (in whatever VM it was in) and
materialize the object.
Is this the pattern that should continue forward? If so, then a change
will need to be made to allow the IndirectionHandler to maintain a
non-transient reference to a PCKey (is this ok?).
Other potential options are to always null out references and
collections, or to fully populate references and collections. Both make
the serialized object completely detached, and non-dependant on having
the second VM be able to work with OJB.
This could also be configurable....there could be Strategies for all 3,
and the user could choose which is best for their use case.

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