Return-Path: 
 <users-return-100338-apmail-cocoon-users-archive=cocoon.apache.org@cocoon.apache.org>
X-Original-To: apmail-cocoon-users-archive@www.apache.org
Delivered-To: apmail-cocoon-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 1E27FDD22
	for <apmail-cocoon-users-archive@www.apache.org>;
 Mon, 20 May 2013 10:59:23 +0000 (UTC)
Received: (qmail 50866 invoked by uid 500); 20 May 2013 10:59:23 -0000
Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org
Received: (qmail 50654 invoked by uid 500); 20 May 2013 10:59:17 -0000
Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:users-help@cocoon.apache.org>
list-unsubscribe: <mailto:users-unsubscribe@cocoon.apache.org>
List-Post: <mailto:users@cocoon.apache.org>
Reply-To: users@cocoon.apache.org
List-Id: <users.cocoon.apache.org>
Delivered-To: mailing list users@cocoon.apache.org
Received: (qmail 50625 invoked by uid 99); 20 May 2013 10:59:16 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 May 2013 10:59:16 +0000
X-ASF-Spam-Status: No, hits=0.0 required=5.0
	tests=NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_NONE
X-Spam-Check-By: apache.org
Received-SPF: error (athena.apache.org: local policy)
Received: from [212.50.160.34] (HELO smtpout.karoo.kcom.com) (212.50.160.34)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 May 2013 10:59:11 +0000
X-IronPort-AV: E=Sophos;i="4.87,707,1363132800";
   d="scan'208";a="14752846"
Received: from unknown (HELO [192.168.0.2]) ([91.85.50.81])
  by smtpout.karoo.kcom.com with ESMTP; 20 May 2013 11:58:27 +0100
Message-ID: <519A01D3.3010709@didm.co.uk>
Date: Mon, 20 May 2013 11:58:27 +0100
From: Peter Sparkes <peter@didm.co.uk>
Reply-To: peter@didm.co.uk
User-Agent: Mozilla/5.0 (Windows NT 6.0;
 rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: users@cocoon.apache.org
Subject: Re: Inter Server Communications
References: <51964AC6.4050802@didm.co.uk> <5196B4FB.3050303@gmail.com>
In-Reply-To: <5196B4FB.3050303@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Now working. Thanks to all.

I used xslt to generate the cinclude, to insert the variables

Regards

Peter

On 17/05/2013 23:53, Thorsten Scherler wrote:
> On 05/17/2013 05:20 PM, Peter Sparkes wrote:
>> Hi
>>
>> I have an application in which I require to send a POST request from
>> the server to another non Cocoon website ( to set parameters for a
>> newsletter which uses phplist newsletter software) and the response
>> would be in JSON
> Highly depends on your underlying usecase what to do with the response
> and further the cocoon version you are using. I lately use the REST-way
> in c3 but you can post anything with cinclude in 2.1.x like:
>
> <cinclude:includexml>
>    <cinclude:src>http://10.231.27.63/sql_templates/</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>text</cinclude:name>
>      <cinclude:value>
>       <ROOT xmlns:sql="urn:schemas-microsoft-com:xml-sql">
>         <sql:xpath-query xmlns:lsa="blah"
> mapping-schema="schema/address.xsd">(/lsa:Address)</sql:xpath-query>
>       </ROOT>
>      </cinclude:value>
>     </cinclude:parameter>
>    </cinclude:parameters>
> </cinclude:includexml>
>
> as described in http://mail-archives.apache.org/mod_mbox/cocoon-users/200512.mbox/%3C06B403677C41D51194550002A55107D2057B8993@s5-stf1-r1.nrn.nrcan.gc.ca%3E
>
>
>> This would be server to server without any client browser being involved
> Actually if I understand your usecase that is not 100% needed. The user
> has the newsletter form generated by cocoon and the result has to go to
> the php server. IF the php is reachable form the "outside" then a simple
> javascript would do to treat the response. If not I recommend a httpd in
> front and there just proxy/rewrite the request to the different server.
>
> salu2
>
>> How do I do this?
>>
>> Help please
>>
>> Peter
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>> For additional commands, e-mail: users-help@cocoon.apache.org
>>
>


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