ORM Persistence

["Sogal, Nagavardhan" <Na...@ca.com>]

Hi !

    Iam trying to use ORM persistence Manager (Hibernate) Implementation
for both workspace and also versioning.( Single database). 

     Seems like when the repository creates an instance of
VersionManagerImpl it inserts a record for VersionStorage and also
initWorkSpace() creates a JCR:SystemNode which has a child nodes called
VersionStorage, nodetypes. This is a Problem because JCR_NODE table has
uuid has primary key and iam getting a duplicate key on insert error. My
question is "Is it Mandatory to have separate databases for Versioning
and workspaces?". Please advice.

 

 

Thanks

Naga

Re: ORM Persistence

[Edgar Poce <ed...@gmail.com>]

Hi sogal

 In its current status orm-persistence is not ready for use. A major
bug was reported, see http://issues.apache.org/jira/browse/JCR-148. If
you think the problem you are reporting is not related please create a
new issue.

thanks,
edgar

On 7/28/05, Sogal, Nagavardhan <Na...@ca.com> wrote:
> Hi !
> 
>     Iam trying to use ORM persistence Manager (Hibernate) Implementation
> for both workspace and also versioning.( Single database).
> 
>      Seems like when the repository creates an instance of
> VersionManagerImpl it inserts a record for VersionStorage and also
> initWorkSpace() creates a JCR:SystemNode which has a child nodes called
> VersionStorage, nodetypes. This is a Problem because JCR_NODE table has
> uuid has primary key and iam getting a duplicate key on insert error. My
> question is "Is it Mandatory to have separate databases for Versioning
> and workspaces?". Please advice.
> 
> 
> 
> 
> 
> Thanks
> 
> Naga
> 
> 
>