Re: [mdr-users] some storage Problems with MDR in Eclipse Rich Clients

Martin Matula <[email protected]>
Newsgroups gmane.comp.java.netbeans.modules.mdr.user
Message-ID <[email protected]>
I think the problem is that the property names are case-sensitive and 
you mistyped the name. It should be:
org.netbeans.mdr.storagemodel.StorageFactoryClassName
instead of:
org.netbeans.mdr.storageModel.StorageFactoryClassName
Hopefully this helps...
Martin

Marcus Tessmer wrote:

> Hi,
>
> I'm using NetBeans MDR in an Eclipse Rich Client.
> Although I'm able to load XMI-Models in the Repository and read its 
> data I have some "non-user-friendly" problems:
>
> 1. I want to use the in-memory storage because my client should only 
> read model data.
>
>     I use the following code as suggested:
>        
>  /System.getProperties().put("org.netbeans.mdr.storageModel.StorageFactoryClassName",
>                
>  "org.netbeans.mdr.persistence.memoryimpl.StorageFactoryImpl");
>
> /    Nevertheless the repository files (*.btd,*.btx) are created.
>
> 2. The load of these repository files fails. I get the following error 
> messages:
>
>     /org.netbeans.mdr.util.DebugException: Boot failed.
> //    org.netbeans.mdr.persistence.StorageBadRequestException: There 
> is no value for key "storageIds:"/
>   /  org.netbeans.mdr.util.DebugException: Fatal I/O error: 
> org.netbeans.mdr.persistence.StorageBadRequestException: There is no 
> value for key "storageIds:"
>
>     /If I replace the created repository files with some older ones 
> which I created with a simple test application
>     (where NetBeans MDR works without problems)  I'm able to load new 
> models. Unfortunately the size of the repository files
>     are constantly increasing with each loading...
>
> If the in-memory storage is successful I think the second problem 
> wouldn't occur.
> How can I fix that problem?
>
> Regards,
> Marcus
>
>
> /   
>
> /
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.