cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andre Juffer <ajuf...@sun3.oulu.fi>
Subject Re: Cocoon 2.2 PUT HTTP request
Date Tue, 21 Sep 2010 18:04:31 GMT
On 09/21/2010 07:38 PM, Christopher Schultz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Andre,
>
> (Is everyone on the list named Andre? :)

No, there is Robbie as well!

>
> 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.

That's right. Both approaches are fine. I tend to use the 
cocoon.request.get* because it is available anyways within flowscript 
functions.

>
> 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:
> http://cocoon.apache.org/2.2/core-modules/core/2.2/844_1_1.html

Yeah, it is not that well organized. Have a look at:

http://cocoon.apache.org/2.2/blocks/flowscript/1.0/1241_1_1.html

>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkyY36MACgkQ9CaO5/Lv0PALAgCgtih3jh2Z4nqm+RuRafLbGOEe
> qCAAoLofwTo+Tah8/kyZlF2sA2B504Wh
> =B+Zg
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>


-- 
Andre H. Juffer              | Phone: +358-8-553 1161
Biocenter Oulu and           | Fax: +358-8-553-1141
Department of Biochemistry   | Email: andre.juffer@oulu.fi
University of Oulu, Finland  | WWW: www.biochem.oulu.fi/Biocomputing/
StruBioCat                   | WWW: www.strubiocat.oulu.fi
NordProt                     | WWW: www.nordprot.org
Triacle Biocomputing         | WWW: www.triacle-bc.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Mime
View raw message