AOM and WebDAV

Answered by: Arbortext Last Updated: 2006-06-18

=Question by Keith Berard=

When referencing a WebDav based file through the AOM, save does not seem to work properly (or at all).

For example: (Rhino Javascript)

var newDoc = Application.openDocument(newurl,Application.OPEN_FORCEDT,null,pubId,sysId); var title = newDoc.getDocumentElement.getFirstChild.getFirstChild; var oldTitle = title.getNodeValue; Application.alert("Old title: " + oldTitle); Application.alert("Modified: " + newDoc.getModified); title.setNodeValue(oldTitle + " New Title"); Application.alert("Modified: " + newDoc.getModified); newDoc.save(Packages.com.arbortext.epic.ADocument.SAVE_XML, newurl); //newDoc.save(Packages.com.arbortext.epic.ADocument.SAVE_XML, newurl, null, //   pubId, sysId); newDoc.close;

In this case, all modified attributes show fine, and the "title" element has its text changed. Also, the openDocument command successfully locks the webdav resource, and the close command successfully unlocks. Save, however, does not seem to hit the server at all.

Furthermore, if I leave out the URL (as suggested in the javadocs) I get an exception that says "No path specified and document has 'http:'"

=Response from Arbortext 2005-09-01=

You are absolutely right with this. The problem you experienced has already been reported. The change request number is:6 3927.

Right now this change request isn't scheduled for a particular release yet however. I have linked this case to the change request so our Development Team will know that a customer has run into this problem.

I hope this information is helpful. Please let us know if you have any further questions on this.