Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <1441900963.1131922645274.JavaMail.jira@ajax.apache.org>
Date: Sun, 13 Nov 2005 23:57:25 +0100 (CET)
From: "Antonio Gallardo (JIRA)" <jira@apache.org>
To: dev@cocoon.apache.org
Subject: [jira] Commented: (COCOON-1365) [Patch] POST method in
 cinclude:includexml is broken
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/COCOON-1365?page=comments#action_12357551 ] 

Antonio Gallardo commented on COCOON-1365:
------------------------------------------

Patch applied in 2.1 and 2.2. Please cross check.

> [Patch] POST method in cinclude:includexml is broken
> ----------------------------------------------------
>
>          Key: COCOON-1365
>          URL: http://issues.apache.org/jira/browse/COCOON-1365
>      Project: Cocoon
>         Type: Bug
>   Components: - Components: Sitemap
>     Versions: 2.1.6
>  Environment: Operating System: Windows XP
> Platform: PC
>     Reporter: Nico Verwer
>     Assignee: Cocoon Developers Team
>  Attachments: XMLUtils.java.patch
>
> Since Cocoon 2.1.6, the cinclude transformer does not handle the POST method
> correctly. This is easy to see with the example from the Cocoon 2.1 docs:
>   <cinclude:includexml>
>     <cinclude:src>http://host:port/path</cinclude:src>
>     <cinclude:configuration>
>       <cinclude:parameter>
>         <cinclude:name>method</cinclude:name>
>         <cinclude:value>POST</cinclude:value>
>       </cinclude:parameter>
>     </cinclude:configuration>
>     <cinclude:parameters>
>       <cinclude:parameter>
> 	      <cinclude:name>message</cinclude:name>
> 	      <cinclude:value>Hi there</cinclude:value>
>     	</cinclude:parameter>
>     </cinclude:parameters>
>   </cinclude:includexml>
> In Cocoon 2.1.5 this made a HTTP-POST request, but in 2.1.6 it makes a HTTP-GET
> request.
> The code of the CInclude transformer does not seem to have changed. I suspect
> that this is a bug in the Excalibur SourceResolver, but I can't find where this
> could be. If someone can make this into a more specific Excalibur bug, please do.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira