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] Resolved: (JCRRMI-2) ClientObservationManager causes null pointer
Date Tue, 24 Feb 2009 10:46:02 GMT

     [ https://issues.apache.org/jira/browse/JCRRMI-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jukka Zitting resolved JCRRMI-2.
--------------------------------

    Resolution: Duplicate
      Assignee: Jukka Zitting

This is a duplicate of JCR-1454.

> 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
>            Assignee: Jukka Zitting
>
> 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.


Mime
View raw message