You probably want to look at the ACL function called oid_entity_lock. As
I remember it, Subversion does not have the idea of checkout. So you
really just need to tell the Editor that you want to request a file
system level lock on this entity or XML inclusion. You don't want to
disable locking behavior, you want the entities / inclusions to be
opened with a lock asserted so that you can write to them and other
users or processes cannot. Then the DOM would see the entities /
inclusions as being writeable.
Normally, the UI of the Editor takes care of this for you. When the
Editor opens an entity or inclusion, it only opens it for read only,
which means that the operating system does not see the file as locked.
Then as the author goes around typing in the document, the Editor
automagically notices if the author is trying to type in an entity or
inclusion that is not yet locked. If so, it asks the operating system
for read/write on the underlying file, causing an operating system lock.
But you are working at the Java level, you don't get the same automagic.
So you have to see if you are trying to write to an entity / inclusion
that is not yet locked at the operating system level and ask for a lock
Software Development Director
Arbortext - PTC