[ http://issues.apache.org/jira/browse/JCR-595?page=comments#action_12445902 ] Jukka Zitting commented on JCR-595: -----------------------------------
Wendy Lee on the mailing list: > I just update the version to 469481 ,The problem still exist.... You're right. In fact there already was a failsafe built into the compatibility classes at o.a.j.core.state.db that made my change redundant. I'll check what else could have caused the problem. > Refactoring of the Persistence Managers > --------------------------------------- > > Key: JCR-595 > URL: http://issues.apache.org/jira/browse/JCR-595 > Project: Jackrabbit > Issue Type: Improvement > Components: core > Reporter: Tobias Bocanegra > Assigned To: Tobias Bocanegra > Priority: Minor > Fix For: 1.2 > > 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
