On 09/22/2010 06:44 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andre,
On 9/22/2010 3:36 AM, Andre Juffer wrote:
Try confirming (say, with LiveHttpHeaders) that the PUT is being
redirected by the server.
This is what I see with LiveHttpHeaders:
http://loca
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andre,
On 9/22/2010 3:36 AM, Andre Juffer wrote:
>> Try confirming (say, with LiveHttpHeaders) that the PUT is being
>> redirected by the server.
>
> This is what I see with LiveHttpHeaders:
>
> http://localhost:/equipment/
>
> POST /equipment
On 09/22/2010 01:27 AM, Christopher Schultz wrote:
-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 r
-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 wa
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/
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 a
-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
method
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 documentatio
-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
>> co
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
-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 b
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 w
Hi Andre,
Thanks for your day to day research feedback.
In Lenya (widely use of cocoon), we have this :
src="{fallback:lenya/modules/webdav/sitemap.xmap}" check-reload="true"
reload-method="synchron"/>
So the request-method selector seems to detect
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- requ
14 matches
Mail list logo
