RE: Sitemap: Error calling continuation

2013-01-11 Thread Robby Pelssers
Well… did you also try to wrap everything in a try catch? Maybe you will get a meaningful stacktrace? Now the only info you get is that there is a problem with the continuation. As a quick hack: function editingForm() { try { //do your stuff here } catch (e) { print(e) }

Re: Sitemap: Error calling continuation

2013-01-11 Thread Dimitra Nefeli
I just tried it but the problem persists The problem is with the continuation. The right points in both sitemaps (cocoon and dcEditor(my folder)) are: (*dcEditor*) (*cocoon) * src="{1}/" uri-prefix="{1}"/> *. *Maybe this information can help Dimitra. * * On 01/11/

RE: Sitemap: Error calling continuation

2013-01-11 Thread Robby Pelssers
I think you’re not using Cocoon2.2 so there might be some differences of course… And so far I have a hunch which you should try out. var viewData = { "title" : form.getChild("title").getValue() } should probably become var viewData = { "title" : form.form.getChild("title").getValue() }

Re: Sitemap: Error calling continuation

2013-01-11 Thread Dimitra Nefeli
On 01/11/2013 02:06 PM, Robby Pelssers wrote: Can you perhaps show the flowscript involved and the relevant sitemap snippets? Robby -Original Message- From: Dimitra Nefeli [mailto:dimnefel...@gmail.com] Sent: Friday, January 11, 2013 11:43 AM To: users@cocoon.apache.org Subject: Sitemap

RE: Sitemap: Error calling continuation

2013-01-11 Thread Robby Pelssers
Can you perhaps show the flowscript involved and the relevant sitemap snippets? Robby -Original Message- From: Dimitra Nefeli [mailto:dimnefel...@gmail.com] Sent: Friday, January 11, 2013 11:43 AM To: users@cocoon.apache.org Subject: Sitemap: Error calling continuation Hi, I am trying t

Sitemap: Error calling continuation

2013-01-11 Thread Dimitra Nefeli
Hi, I am trying to make a form and submitting it, a new xml file will be created. The problem is with the sitemaps and the pipelines. In the sitemap.xmap of my folder (dcEditor), I have defined a "dc-success-pipeline", which simply "calls" a .jx file. The problem is in the continuation of site