I've seen this problem periodically.

There seem to be two issues occurring:

1. A change is actually saved on the server but Kupu has silently stripped
out the changes made, so it appears that no change has been saved.
2. There is a failure on the server to save the new file version. 

In regards to the first issue we have, through modification of the relevant
kupu files, achieved a solution that works.

I'm now trying to solve the second problem. I'm using Lenya 1.2.5 on Windows
XP with Tomcat 5.0. This problem has been reported previously but without a
satisfactory resolution it seems, possibly because of its intermittent
nature.

I've found that the editDocument() routine in
webapps\lenya\lenya\usecases\edit_document.js is giving an exception on
trying to save modifications to a file a second time around.

Note: I had to change the logging call to get a relevant error message in
the cocoon log-file as below;

     //cocoon.log.error("Can not edit document.", exception);
        cocoon.log.error("Can not edit document: "  + exception.toString());

The error message I am seeing is as below:

ERROR flow.invoke0():?  - Can not edit document: JavaException:
java.io.IOException: Could not rename
C:\tomcat\webapps\lenya\lenya\pubs\tlp\content\authoring\index\index_en.xml.tmp
to
C:\tomcat\webapps\lenya\lenya\pubs\tlp\content\authoring\index\index_en.xml

This is being caused by the call below;

        SourceUtil.copy(resolver, cocoon.parameters["sourceUri"], dstUri,
_getParameter("useBuffer", "false") == "true");

which is to the static method in
org.apache.lenya.cms.cocoon.source.SourceUtil.

There is no actual index_en.xml.tmp file being left behind.

I'm wondering if anyone has any suggestions. It does seem to me like a file
access issue.

Thanks

Steve Cameron 
-- 
View this message in context: 
http://www.nabble.com/Failure-to-save-changes-in-Kupu.-tp16736416p16736416.html
Sent from the Lenya - Dev mailing list archive at Nabble.com.


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

Reply via email to