jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2493) Unit tests for persistence managers
Date Tue, 16 Feb 2010 10:13:27 GMT

    [ https://issues.apache.org/jira/browse/JCR-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834142#action_12834142
] 

Thomas Mueller commented on JCR-2493:
-------------------------------------

With the H2 database, changing the database URL is enough:
manager.setUrl("jdbc:h2:mem:" + database.getPath());
The memory is automatically released when the connection is closed.

Derby also supports in-memory databases now, but unfortunately
it doesn't release the memory, and there is no nice way to do that manually:
http://wiki.apache.org/db-derby/InMemoryBackEndPrimer

I suggest to only change the H2 JDBC URL.

> Unit tests for persistence managers
> -----------------------------------
>
>                 Key: JCR-2493
>                 URL: https://issues.apache.org/jira/browse/JCR-2493
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Minor
>         Attachments: JCR-2493.patch
>
>
> Currently we only test our persistence managers indirectly via JCR-level test cases.
The downside of this approach is that we can only test one persistence manager implementation
at a time, and need separate build profiles to switch from one implementation to another.
To ensure better coverage and consistent behaviour across all our persistence managers I implemented
a simple unit test that works directly against the PersistenceManager interface.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message