jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-595) Refactoring of the Persistence Managers
Date Tue, 31 Oct 2006 13:54:17 GMT
    [ http://issues.apache.org/jira/browse/JCR-595?page=comments#action_12445896 ] 
            
Jukka Zitting commented on JCR-595:
-----------------------------------

> Configuration error: unknown schema 'derby' 

This was caused by the use of getClass().getResourceAsStream() to load the DDL files. The
resources are local to the o.a.j.core.persistence.db package, so the call failed when invoked
from a compatibility subclass in o.a.j.core.state.db.

I just committed (revision 469481) a simple fix that replaces getClass() with DatabasePersistenceManager.class.

> Refactoring of the Persistence Managers
> ---------------------------------------
>
>                 Key: JCR-595
>                 URL: http://issues.apache.org/jira/browse/JCR-595
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.1.1
>            Reporter: Tobias Bocanegra
>         Assigned To: Tobias Bocanegra
>            Priority: Minor
>             Fix For: 1.1.1
>
>         Attachments: jackrabbit.465518.patch
>
>
> currently the persistence managers reside in:
>  org.apache.jackrabbit.core.state
>  org.apache.jackrabbit.core.state.db
>  org.apache.jackrabbit.core.state.mem
>  org.apache.jackrabbit.core.state.obj
>  org.apache.jackrabbit.core.state.xml
>  (org.apache.jackrabbit.core.state.util)
> there are also a lot of other classes that deal with states (eg:
> SharedItemStateManager) in the state package that do not relate to
> pms.
> i would like to move all persistencemanagers and pm related stuff to:
>  org.apache.jackrabbit.core.persistence
> I'd keep the current classes as deprecated subclasses within
> jackrabbit-core.jar until Jackrabbit 2.0. There may (?) be people who
> are extending the existing classes, so I'd avoid breaking binary
> compatibility there even though we've never promised to actually honor
> compatiblity within o.a.j.core.

-- 
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message