Return-Path: 
 <cocoon-dev-return-36481-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 76380 invoked by uid 500); 10 Feb 2003 23:09:29 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 76346 invoked from network); 10 Feb 2003 23:09:28 -0000
User-Agent: Microsoft-Entourage/10.1.1.2418
Date: Mon, 10 Feb 2003 23:09:30 +0000
Subject: Re: WSProxyGenerator
From: Pier Fumagalli <pier@betaversion.org>
To: <cocoon-dev@xml.apache.org>
Message-ID: <BA6DE1AA.126A1%pier@betaversion.org>
In-Reply-To: <20030210155933.U3879-100000@neuagency.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

On 10/2/03 21:00, "Tony Collen" <tcollen@neuagency.com> wrote:

> On Mon, 10 Feb 2003, Nathaniel Alfred wrote:
> 
>> Why not use plain old FileGenerator?  At least with 2.1's URLSource
>> 
> 
>>    <map:generate type="file" src="http://backend/article?id=xyz"/>
>> 
>> works like a charm.  Am I missing something?
> 
> The WSP also passes any POST or GET parameters to the remote host, which
> is something the FileGenerator does not do. Would it just make sense to
> put this feature into the FileGenerator as a <map:parameter/> ?

Ok, in my working copy (which I deleted this afternoon, promptly followed by
swearing in my native language going on for roughly 4 hours), the proxy
generator was configured in the following way:

  <map:generators>

    <!-- Map the HTTP proxy generator -->

    <map:generator name="proxy"
        label="content,data"
        src="org/betaversion/cocoon/components/proxy/HttpProxyGenerator"
        logger="sitemap.generator.proxy">

      <!-- This is the _base_ URL where requests will be made to.
           It is considered the "base" URL because it can be overridden
           at runtime in the pipeline configuration -->

      <url>http://wwwp.overture.com/d/search/p/partner/xml/2.3.2/</url>

      <!-- Method: right now it's only GET or POST -->

      <method>POST</method>

      <!-- Parameters defined within the "param" element can have multiple
           values, and will end up in the request body (in case of POST)
           or added to the query string (in case of GET) -->

      <param name="paramA" value="valueA1"/>
      <param name="paramA" value="valueA2"/>
      <param name="paramB" value="valueB1">
        <value>valueB2</value>
        <value>valueB3</value>
      </param>

      <!-- Parameters defined within "query" elements will be configured
           exactly as the above "param", BUT in both cases (GET and POST)
           will end up in the query string -->

      <query name="queryX" value="valueX1"/>
      <query name="queryX" value="valueX2"/>
      <query name="queryY">
        <value>valueY1</value>
        <value>valueY2</value>
      </param>
    </map:generator>
  </map:generators>

  [...]

  <map:pipelines>
    <map:pipeline>
      <map:match pattern="test">

        <!-- Use the proxy generator defined above. Note, the src attribute
             will be relative to the URL declared in the configuration above
             (if any), while if it is an "absolute" URL, it will be used
             instead of the one above...  -->

        <map:generate type="proxy" src="./search">

          <!-- Parameters defined here override (or expand) the ones
               declared in the configuration above:

               - if the name starts with param:, the value will be added
                 to the values of the parameter defined above

               - if the name starts with param-overried:, the value will
                 override any value specified in the configuration above

               Same thing for query (starting with "query:" and/or
               "query-override:".

          <parameter name="param:q" value="{request-param:q}"/>

          <!-- Debug flag, instead of generating from the remote HTTP
               server, dump out a some sort of XML-ized kind of query we
               are going to do, since it might become complicated -->

          <parameter name="debug" value="false"/>

        </map:generate>
        <map:serialize type="xml"/>
      </map:match>

I was planning to add support for headers as well, but at the end, I have to
rewrite the entire thing by tomorrow in the morning, so, those will come
later :-(

    Pier


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