On 1/15/06, Rovi <[EMAIL PROTECTED]> wrote:
> I still am encountering this issue - though less frequently (but is
> undoubtedly very frustrating when a CMS cannot do a basic save of change).
> This is a part of error message that I had seen using httplook when I saved
> (and it it did not save):
>
> "full exception chain stacktrace">org.apache.cocoon.ProcessingException:
> <map:call function> did not send a response, at file:/C:/lenya/apache-
> lenya-1.2.4/build/lenya/webapp/lenya/usecases/kupu/usecase-kupu.xmap:255:49
> at
> org.apache.cocoon.components.treeprocessor.sitemap.CallFunctionNode.invoke
> (CallFunctionNode.java:137)
> at......"
The JS function editdocument() never returns. Every flow path should
end with a cocoon.sendPage() or equivalent. catch(exception) does not
return properly. You could add better returns, but they would only
inform about the issue, not solve it.
FILE: webapp/lenya/usecases/edit-document.js
function editDocument() {
try {
var flowHelper = new FlowHelper();
[...]
if(hasWorkflow)
flowHelper.triggerWorkflow(cocoon,
_getParameter("workflowEvent", "edit"));
//Good returns
if(_getParameter("noStatus", "false") == "false")
cocoon.sendStatus(_getParameter("status", 204));
else
cocoon.redirectTo(_getParameter("redirectUrl", "FIXME"));
} catch (exception) {
cocoon.log.error("Can not edit doucment.", exception);
//Add return error
} finally {
if(resolver != null)
cocoon.releaseComponent(resolver);
//Add final return
}
//Add default return (should be unreachable if final return is added.)
}
We need the to solve the exception that was caught.
Where does cocoon.log.error() write?
solprovider
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
