Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <406BD76A.3040501@babelobjects.com>
Date: Thu, 01 Apr 2004 10:48:42 +0200
From: Jean-Christophe Kermagoret <jck@babelobjects.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.5) Gecko/20031007
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Trying to solve a bug
References: <OF6A528E6D.D4ED3A69-ONC1256E69.002F34AD@sundn.de>
In-Reply-To: <OF6A528E6D.D4ED3A69-ONC1256E69.002F34AD@sundn.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Carsten,
thanks for your answer

I already use hidden field for continuation id.

My action attribute doesn't contain anything important. Just submit 
value for example according the 
http://wiki.cocoondev.org/Wiki.jsp?page=WoodyCopletForPortalEngine

So, I have no request param appended to the uri in my action attribute.

However, I still can't see any request-param, hidden or not.

Jean-Christophe

Carsten Ziegeler wrote:

>Hi,
>
>now I think I remember that I had the same problem when I wrote the
>upload coplet sample that is in the basket sample in our CVS.
>If you specify an enctype attribute, the request parameters appended
>to the uri in the form action attribute are either not send to
>Cocoon or are not received by Cocoon - I tested this with Tomcat
>and Jetty. So I guess this is by design.
>Now, the portal rewrites all links in order to process them correctly.
>When you use the portal-html-eventlink transformer, it rewrites
>a form action to something like "portal?cocoon-portal-action=24".
>So, if then also an enctype attribute is set for the form, Cocoon
>never receives the request parameter.
>Instead putting this into a hidden field works. So I think this
>is not a bug of the portal.
>If you want to have a form with an enctype attribute you have
>either to expand the html-eventlink transformer so that it creates
>in this case a form element without request parameters in the
>action, but with some hidden input fields or you have to write
>your own transformer for this. You can use the BasketTransformer
>as a starting point.
>
>HTH
>Carsten 
> 
>
>  
>
>>-----Original Message-----
>>From: Jean-Christophe Kermagoret [mailto:jck@babelobjects.com] 
>>Sent: Thursday, April 01, 2004 10:11 AM
>>To: dev@cocoon.apache.org
>>Subject: Trying to solve a bug
>>
>>Hi,
>>I'm trying to solve a bug but I need a little information.
>>
>>Here is the bug I open it in bugzilla.
>>
>>I need to use a upload form with the new cocoon portal. I use 
>>the portal-html-eventlink to transform the action attribute. 
>>The problem is enctype attribute is deleted by the 
>>portal-html-eventlink transformer.
>>
>>
>>I modified the tranformer to have the enctype attribute if 
>>present. I pass the continuation id in an hidden field, but 
>>when the pipeline is processed, the 
>>{request-param:continuation-id} is empty but I saw the 
>>uploaded file in the upload-directory.
>>
>>If I don't use the transformer then I can set up a pipeline 
>>in the action attribute and I see the continuation-id
>>
>>So,
>>I think there is a problem with the multipart request. The 
>>fact to put the enctype data is not enough. Why the portal 
>>doesn't see the request param ?
>>
>>I tried to track the processing of the portal with Eclipse 
>>but I have non synchronized data between my souce and the 
>>classes that are generated so it's difficult to know what's happening.
>>
>>Can anybody give me a little info to help me debugging this ?
>>
>>-- 
>>
>>Jean-Christophe Kermagoret
>>jck@BabelObjects.Com
>>
>>
>>
>>
>>    
>>
>
>
>  
>


-- 

Jean-Christophe Kermagoret
jck@BabelObjects.Com