cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <>
Subject Re: Cocoon 2.2 PUT HTTP request
Date Tue, 21 Sep 2010 16:38:59 GMT
Hash: SHA1


(Is everyone on the list named Andre? :)

On 9/21/2010 9:10 AM, Andre Juffer wrote:
> There is still one other issue to be solved. In the case of a PUT
> request (or any other HTTP request for that matter), my understanding is
> that I should be able to identify the request HTTP method in flowscript
> by cocoon.request.getMethod() or in a pipeline using <map:parameter
> name="method" value="{request:method}" />. I find in either case that
> this parameter's value is always GET, whatever the original request
> method received by the servlet engine was. It seems that the original
> request method value is simply lost somewhere, -before- the request is
> being handled in the sitemap.

I'll check to see what I can get from {request:method} in my sitemap.
Other {request:*} methods seem to be working okay, though. I am also
using Cocoon 2.1, but at (the other) Andre points out, the differences
shouldn't be great in these areas.

I'm still interested in how Cocoon passes parameters to functions. In
the code you posted before, it didn't seem like you were actually trying
to access that parameter. If you use {request:method} in your pipeline,
I suspect it will give you the right method as long as you read the
/parameter/ instead of trying to use cocoon.request.getMethod() as it
appeared you were doing.

I find the Cocoon documentation very difficult to navigate. Can you
point me to the documentation for calling javascript functions? All I
could find was this:

- -chris
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla -


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message