Re: Undo/redo implementation & JMI compliance

Holger Krug wrote:
> On Wed, Jun 26, 2002 at 03:57:06PM +0200, Svata Dedic wrote:
> 
>>Holger Krug wrote:
> 
>>>RefBaseObject Repository.getByMofId(String mofId) throws SomeException 
>>
>>I am afraid this would be very very difficult operation, given that it 
>>spans all package extents, some possible remote. It was rejected last 
>>time I asked for something similar.
> 
> 
> MDR already has such a method:
> 
>   public StorageBaseObject MdrStorage.getObject(String mofid) throws ...
> 
Yep, but that works for a single storage... in the theory, even the MDR
can work with multiple Storage objects, and this method becomes useless
for your use case. If you worked with a JMI service, which works in a
distributed environment, say some package extends stored at different
nodes of a cluster, I doubt that such implementation would permit that
operation - so if you are after some abstraction which would allow you
to work on top of different JMI providers, I wouldn't count on this
feature being available.
IMHO mofIDs are tokens, and the only thing which is guaranteed is that 
two live objects cannot have the same mofIDs, so you can use them as 
object identity. Incidentally, MDR uses mofIDs as index keys into the 
storage layer.

-Svata

-- 
Svatopluk Dedic            <mailto:[email protected]>
NetBeans, Java/Repository  <http://java.netbeans.org>