On 09/20/2010 11:38 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andre,
On 9/20/2010 3:06 PM, Andre Juffer wrote:
The source of my problem is therefore clear.
Absolutely.
I've checked Tomcat 7.0.2. Same issue, as expected.
With jetty 7.1.6,
Christopher,
On 09/20/2010 11:38 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[The DefaultServlet has a] readonly parameter in web.xml to change this
behavior,
but indeed this would not have any impact since the request is handled
by my cocoon2.2-based
Dear All,
in a previous thread, I was trying to understand why I could not see the
request parameters of a HTTP PUT request using the
cocoon.request.getParameter(...) family of methods in flowscript.
Conclusion: For a PUT request, according to specification, the servlet
engine is -not-
Hi Andre,
Thanks for your day to day research feedback.
In Lenya (widely use of cocoon), we have this :
map:select type=request-method
!-- many client editors like to PUT changes --
map:when test=PUT
map:mount uri-prefix=
Thanks for your response.
I am going to try this and see if this works. The RequestMethodSelector
is also available in Cocoon 2.2. I just did not expect that one must use
it to identify the request method in the sitemap, given that the request
object is available as cocoon.request in flow as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andre,
(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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andre,
On 9/21/2010 6:22 AM, Andre Juffer wrote:
I found this (for Tomcat 5)
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
On 09/21/2010 07:41 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andre,
On 9/21/2010 6:22 AM, Andre Juffer wrote:
I found this (for Tomcat 5)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andre,
On 9/21/2010 2:04 PM, Andre Juffer wrote:
On 09/21/2010 07:38 PM, Christopher Schultz wrote:
I find the Cocoon documentation very difficult to navigate. Can you
point me to the documentation for calling javascript functions? All I
could
On 09/21/2010 09:40 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andre,
On 9/21/2010 2:04 PM, Andre Juffer wrote:
On 09/21/2010 07:38 PM, Christopher Schultz wrote:
I find the Cocoon documentation very difficult to navigate. Can you
point me to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andre,
On 9/21/2010 3:15 PM, Andre Juffer wrote:
This provides an overview of the cocoon.request methods:
http://cocoon.apache.org/2.2/blocks/flowscript/1.0/1383_1_1.html
Okay, this looks like a HttpServletRequest object with a few more
methods
On 09/21/2010 10:52 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andre,
On 9/21/2010 3:15 PM, Andre Juffer wrote:
This provides an overview of the cocoon.request methods:
http://cocoon.apache.org/2.2/blocks/flowscript/1.0/1383_1_1.html
Okay, this looks like
Chris,
I got it working now. It is really in the details.
I always relied upon a PUT request like
http://localhost:/equipment
expecting to see the request method set to PUT. In fact, it was always GET.
If, however, one employs
http://localhost:/equipment/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andre,
On 9/21/2010 4:26 PM, Andre Juffer wrote:
I got it working now. It is really in the details.
I always relied upon a PUT request like
http://localhost:/equipment
expecting to see the request method set to PUT. In fact, it was
15 matches
Mail list logo
