hi
i tried it out and it works for me.
are you sure, you are using it properly? please note, that
whenever, the token returned by that custom LOCK is present
in a subsequent request (in terms of a TransactionId header),
the same session is retrieved again and all modifications are
added to that 'batch'.
however:
as soon as you omit the token you get another session and
in case the header is missing completely any modification
(such as MKCOL) is immediately persisted within the same
scope of the request, as it is 'specified' in the document
mentioned recently.
regards
angela
Kalka, Edyta wrote:
Hi,
[...] that calls
getItem(resource).refresh(false)). So far - ok, rollback is being
called
but... the changes are still kept (in other words newly created
collection can be accessed) - why?
could it be, that your client has some sort of cache,
that doesn't get flushed (since it is not notified about
the effect of the refresh)?
No, I checked the repository content from few separate clients:
- eclipse webdav site explorer,
- jcr browser,
- and using your browser viewer
Edyta
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
