Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (herse.apache.org: domain of riceyeh@gmail.com designates
 66.249.92.174 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=jB0wrUwcawBCPDCGQW9Fr2xiEn5VJ0hytJV6BH1SinA8vbtmv3hfepExzvRXnFpfSTaf0gxFb2bbiOPp43DATRv0iahSsoTpCeS44S0TdUmEwPYuyPPZk0y7qF7AVACvqza7c4TCDe7ltpZMSfsW5QaYdlGapuGJ/lNSpLxi/Q8=
Message-ID: <47f71d940704022130s68872715o4ffaf28f66450efa@mail.gmail.com>
Date: Tue, 3 Apr 2007 12:30:07 +0800
From: "Rice Yeh" <riceyeh@gmail.com>
To: dev@cocoon.apache.org
Subject: Re: Parameters in request get lost when using servlet: protocol
In-Reply-To: <euqte0$ktg$1@sea.gmane.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_830_16393820.1175574607283"
References: <47f71d940704012335ic080521s177e9a03d8b512e1@mail.gmail.com>
	 <euqte0$ktg$1@sea.gmane.org>

------=_Part_830_16393820.1175574607283
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Thank you for your solution. But I still feel weird for a brand new request
being created for a called block (servlet), at least for a super block
(servlet). Having a look at the source code, each new brand request and
response are supposed to be stored in its call frame (actually, this feature
is not implemented yet, but api for retrieving these two objects are
provided). If such design is intended, why not just treat request and
response as part of servlet (block) context. And a way for passing a
request's attributes or parameters must be provided. My real opinion is that
request should be pass through all servlets invoked, instead of creating a
new one.

Rice

On 4/2/07, Alexander Klimetschek <alexander.klimetschek@mindquarry.com>
wrote:
>
> We had the same problem already with the previous block: protocol.
> Currently
> the only way to send parameters to the other servlet via the URL. Thus I
> have written a simple input module that converts your params into URL
> params:
>
> - ParamsToURIModule: (Input Module)
>
> a meta module that converts all attributes of another module into a
> correct
> uri query string (&a=b;c=d)
>
>
> http://www.mindquarry.org/repos/mindquarry-webapp/trunk/mindquarry-webapp-resources/src/main/java/com/mindquarry/webapp/modules/ParamsToURIModule.java
>
>
> To use it, simply write this (if the input module is registered under
> 'params-as-uri':
>
> <map:read src="servlet:super:/{0}?{params-as-uri:request-param}"/>
>
>
> It is a meta input module, ie. it takes the name of another module and
> converts all it's attributes into an URL query string. In this case it
> will
> add all request parameters.
>
> Alex
>
>
> Rice Yeh schrieb:
> > Hi,
> >  I find that all the parameters in a http request get lost when using
> > servlet: in a sitemap like the following:
> >
> > <map:read src="servlet:super:/{0}"/>
> >
> > Any clue?
> >
> > Rice
> >
>
>
> --
> Alexander Klimetschek
> http://www.mindquarry.com
>
>

------=_Part_830_16393820.1175574607283
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Thank you for your solution. But I still feel weird for a brand new request being created for a called block (servlet), at least for a super block (servlet). Having a look at the source code, each new brand request and response are supposed to be stored in its call frame (actually, this feature is not implemented yet, but api for retrieving these two objects are provided). If such design is intended, why not just treat request and response as part of servlet (block) context. And a way for passing a request&#39;s attributes or parameters must be provided. My real opinion is that request should be pass through all servlets invoked, instead of creating a new one.
<br><br>Rice<br><br><div><span class="gmail_quote">On 4/2/07, <b class="gmail_sendername">Alexander Klimetschek</b> &lt;<a href="mailto:alexander.klimetschek@mindquarry.com">alexander.klimetschek@mindquarry.com</a>&gt; wrote:
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">We had the same problem already with the previous block: protocol. Currently<br>the only way to send parameters to the other servlet via the URL. Thus I
<br>have written a simple input module that converts your params into URL params:<br><br>- ParamsToURIModule: (Input Module)<br><br>a meta module that converts all attributes of another module into a correct<br>uri query string (&amp;a=b;c=d)
<br><br><a href="http://www.mindquarry.org/repos/mindquarry-webapp/trunk/mindquarry-webapp-resources/src/main/java/com/mindquarry/webapp/modules/ParamsToURIModule.java">http://www.mindquarry.org/repos/mindquarry-webapp/trunk/mindquarry-webapp-resources/src/main/java/com/mindquarry/webapp/modules/ParamsToURIModule.java
</a><br><br><br>To use it, simply write this (if the input module is registered under<br>&#39;params-as-uri&#39;:<br><br>&lt;map:read src=&quot;servlet:super:/{0}?{params-as-uri:request-param}&quot;/&gt;<br><br><br>It is a meta input module, ie. it takes the name of another module and
<br>converts all it&#39;s attributes into an URL query string. In this case it will<br>add all request parameters.<br><br>Alex<br><br><br>Rice Yeh schrieb:<br>&gt; Hi,<br>&gt;&nbsp;&nbsp;I find that all the parameters in a http request get lost when using
<br>&gt; servlet: in a sitemap like the following:<br>&gt;<br>&gt; &lt;map:read src=&quot;servlet:super:/{0}&quot;/&gt;<br>&gt;<br>&gt; Any clue?<br>&gt;<br>&gt; Rice<br>&gt;<br><br><br>--<br>Alexander Klimetschek<br><a href="http://www.mindquarry.com">
http://www.mindquarry.com</a><br><br></blockquote></div><br>

------=_Part_830_16393820.1175574607283--