[omniORB] persistent hierarchical implementations

[Randy Shoup]

> Renzo Tomaselli wrote:
> 
> Dear OmniORB developers,
>            I know how to deal with single persistent implementations:
> the skeleton initialization through a private key and so on. This
> works fine.
> Now, if I have a hierarchy of persistent objects, I have a graph which
> runs somewhat in parallel to the skeleton graph (foo_i: _sk_foo,
> parentOfFoo_i and so on). I guess any point of the graph is suitable
> for  my persistent key skeleton initialization; or even all, given the
> way setRopeAndKey works (provided the key is the same, off course). Am
> I correct ?

This is correct.  You only need to call the object-key ctor once in your
implementation class tree in order for the object's key to be set. 
There is really only one base omniObject instance ultimately, so you
only need to set its key once.

-- Randy
_________________________________________________________________  
Randy Shoup                                     (650)216-2038  
Software Architect                              rshoup@tumbleweed.com  
Tumbleweed Communications Corporation