Re: Undo/redo implementation & JMI compliance

Martin Matula <[email protected]>
Newsgroups gmane.comp.java.netbeans.modules.mdr.devel
Message-ID <[email protected]>
Hi Svata,
actually getByMofId operations can be very easily implemented in MDR. It 
is just one line of code. I know we have been playing with the idea of 
adding it somewhere for quite some time.
We just didn't agree in where to put it in the API. I guess that 
MDRepository is the right place.
Martin

Svata Dedic wrote:
> Holger Krug wrote:
> 
>> On Wed, Jun 26, 2002 at 02:44:17PM +0200, Svata Dedic wrote:
>>
>>
>> Furthermore because I want to have persistent undo/redo support I must
>> uniquely identify each repository object in a serializable way. IMHO
>> JMI allows to do this for instance objects only by a combination of
>> fully qualified names and mofIds. Quite odd, when almost every JMI
>> implementation should be able to provide a fast lookup by mofId. This
>> slows down undo/redo further. Hence my proposal to add an interface
>> Repository with an operation:
>>
>> 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.
> 
> -Svata
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.