incubator-jspwiki-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Janne Jalkanen (JIRA)" <>
Subject [jira] Commented: (JSPWIKI-324) ReferenceManager throws NullPointerException when renaming read-only page
Date Sun, 10 Aug 2008 10:29:46 GMT


Janne Jalkanen commented on JSPWIKI-324:

I agree with Harry.  JSPWiki assumes it can do whatever it wants with the repository, so if
the underlying CMS does not allow that, then your only chance is to remove the "update referrers"
functionality, or fix the provider.

> ReferenceManager throws NullPointerException when renaming read-only page
> -------------------------------------------------------------------------
>                 Key: JSPWIKI-324
>                 URL:
>             Project: JSPWiki
>          Issue Type: Bug
>          Components: Core & storage
>    Affects Versions: 2.6.2
>         Environment: RHEL 5.1, Apache Tomcat 6.0.16, JSPWiki 2.6.2
>            Reporter: Thomas Hinterndorfer
>            Assignee: Harry Metske
>            Priority: Minor
>   Original Estimate: 4h
>  Remaining Estimate: 4h
> I am using custom Page and Attachment Providers, so this issue may not be recreatable
in other environments.
> These providers store the contents in the CMS of the company, i am working for.
> I have 2 pages, created by different users, linking each other. If i change the ACL (in
the CMS) for page A, so the other user may only read, but not change it, then rename page
B with the user, who may only read page A, the referring link on page A is not updated, because
the user doesn't have write permissions. But if i then rename page A, i get a NullPointerException
from the ReferenceManager (the page name is updated correctly), it's only confusing for users
to get an error, and other references to the page aren't updated too. If i restart JSPWiki
after renaming page B, there's no error. So i guess, the ReferenceManager is trying to update
the link, it fails due to the lack of permissions, and the ReferenceManager stores wrong information
and tries to update non-existing references when renaming page A. This would explain why there's
no error after restarting, because the references are rebuilt.
> Text from Error.jsp:
> Error Message
>     An unknown exception java.lang.NullPointerException was caught by Error.jsp.
> Exception
>     java.lang.NullPointerException
> Place where detected
>     com.ecyrd.jspwiki.ReferenceManager.clearPageEntries(), line 885 

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

View raw message