[ http://issues.apache.org/jira/browse/JCR-78?page=history ]
Stefan Guggisberg closed JCR-78:
--------------------------------
Resolution: Invalid
> contrib/orm-persistence: Configuration-Attribute for
> HibernatePersistenceManager
> --------------------------------------------------------------------------------
>
> Key: JCR-78
> URL: http://issues.apache.org/jira/browse/JCR-78
> Project: Jackrabbit
> Type: Improvement
> Environment: JCR client applications with more than one repository using the
> HibernatePersistenceManager implementation in contrib/orm-persistence.
> Reporter: Simon Brunner
> Priority: Trivial
> Attachments: hpm_patch.txt
>
> Some applications use more than one repository. Magnolia CMS
> (www.magnolia.info) for example uses four repositories to store the websites,
> roles, users and the configuration independently. In my opinion, a small
> modification to the HibernatePersistenceManager located in
> contrib/orm-persistence would allow to specify an optional Hibernate
> configuration-file for each HibernatePersistenceManager configured within the
> same application (instead of having a global Hibernate mapping-file for the
> whole application). This would give us the possibility to use unique table
> prefixes for every repository (when stored into the same database/db-schema)
> or to use different databases/schemas for each repository.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
