DOMSource does not respect DB locking

[adamretter]

When we provide DOMSource to various XML libraries, for example JAXT it is done without any locking on the database resource. This can lead to problems if there are concurrent deletes or modifications on the same resource.

[dizzzz]

to you mean JAXP ?

[adamretter]

@dizzzz I mean javax.xml.transform

[alebastrov]

I think you should not take care about locking in this case. Anyone, who wants to modify a document, should call collection.store(), because locking might take loads of time and DB will become unresponsible

[alebastrov]

Any XUpdate should hold locks of course

[adamretter]

@alebastrov If you don't have a READ_LOCK then the document can be changed as you are accessing it, which could cause exceptions

[alebastrov]

I meant you should get READ_LOCK, then read document, release READ_LOCK, return document to a caller

[adamretter]

@alebastrov We have no way of knowing when a DOMSource has been read at present.