DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32576>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32576


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |INVALID




------- Additional Comments From [EMAIL PROTECTED]  2004-12-08 16:54 -------
Either:
 - Earlier calls to retrieve information on a locked entity have resulted in a 
null response instead of an 
exception due to the object being locked, or
 - Something inside of that method isn't working.

As that's the first call, you're right, I'm passing in a null reference - but 
if it's null, it can only be 
because the API provided me a null response instead of throwing an exception 
due to a locked instance.

The loading code essentially does this:

node = state.structureHelper.retrieve(state.slideToken, path.toString());
revisions = state.contentHelper.retrieve(state.slideToken, path.toString());
if (revisions!=null && revisions.hasRevisions()) {
        properties = state.contentHelper.retrieve(state.slideToken, revisions);
        if (properties != null) {
                exists = true;
        }
}

I've now had situations where a locked object has resulted in either 
structureHelper returning a null 
node, or contentHelper returning a null revisions, without hitting the 
exception catches.  I'll try to get 
together some kind of test case that causes this under 2.1 branch, but I'm 
having problems replicating 
them predictably.  Marking as invalid until I can prove, if there is a problem, 
that there is a problem.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to