Toby, We are still seeing this issue occur, so if there's a workaround that means you are happy to close it, then please could you give some more details? I couldn't understand precisely from Michael's email what the solution was, although it sounds as though it may be related to our configuration (single database instance for all system data).
Cheers, Miro -----Original Message----- From: Tobias Bocanegra (JIRA) [mailto:[EMAIL PROTECTED] Sent: 16 May 2006 21:18 To: [email protected] Subject: [jira] Closed: (JCR-425) NPE in VersionManagerImpl [ http://issues.apache.org/jira/browse/JCR-425?page=all ] Tobias Bocanegra closed JCR-425: -------------------------------- Resolution: Invalid > NPE in VersionManagerImpl > ------------------------- > > Key: JCR-425 > URL: http://issues.apache.org/jira/browse/JCR-425 > Project: Jackrabbit > Type: Bug > Components: core > Reporter: Michael Frericks > > Sometimes a NPE occurs in org.apache.jackrabbit.core.version.VersionManagerImpl#internalSetItemRef erences because the parameter item is null. > Up the call hierarchy i would suggest to check item != null in method: > public boolean setNodeReferences(NodeReferences refs) { > try { > InternalVersionItem item = getItem(refs.getTargetId()); > if (item == null) > { > return true; > } > setItemReferences(item, refs.getReferences()); > return true; > } catch (RepositoryException e) { > log.error("Error while setting references: " + e.toString()); > return false; > } > } -- 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
