[
https://issues.apache.org/jira/browse/JCRRMI-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting moved JCR-1643 to JCRRMI-2:
-----------------------------------------
Component/s: (was: jackrabbit-jcr-rmi)
Affects Version/s: (was: rmi 1.4.1)
Workflow: no-reopen-closed, patch-avail (was: jira)
Key: JCRRMI-2 (was: JCR-1643)
Project: Jackrabbit JCR-RMI (was: Jackrabbit)
> ClientObservationManager causes null pointer
> --------------------------------------------
>
> Key: JCRRMI-2
> URL: https://issues.apache.org/jira/browse/JCRRMI-2
> Project: Jackrabbit JCR-RMI
> Issue Type: Bug
> Environment: Using a simple rmi connection to connect to a jackrabbit
> server running on tomcat on linux.
> Reporter: Brett Conoly
>
> This is listed as major because it prevents rmi users from accessing
> registered events...safely
> There is a mailing list thread with the subject "null pointer in client
> observation manager" for reference.
> Using:
> ObservationManager manager = session.getWorkspace().getObservationManager();
> EventListenerIterator events = manager.getRegisteredEventListeners();
> causes an unexplained null pointer within the ClientObservationManager if
> getRegisteredEventListeners() is called before an EventListener is registered
> with the related ObservationManager.
> This was tested with
> org.apache.jackrabbit.core.observation.ObservationManagerImpl and it passed
> without any issues.
> No other implementations of the ObservationManager were tested.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
