cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chitharanjan Das" <c...@accordiasys.com>
Subject RE: File Upload using action or any other approach
Date Tue, 16 Apr 2002 20:59:59 GMT
Hello Andre,
	Thanks for the input....

I do not need to process the Data ..

Let me re-iterate the problem..

User is presented with a HTML form to upload a data file (XML or not).

The user then browses for the file on his m/c (client) and presses the
submit button..

Now this file has to be uploaded into a specific directory on the
server.


My question is , Does cocoon have inbuilt functionalities to handle
Multipart requests or should I code it. At this moment I am not
considering in processing the contents of the file.

Could U please illustrate your approach (with code snippet, if possible)
, how to achieve just the transfer of file from client to a specific
directory on the server.

Regds,
Chiths











-----Original Message-----
From: Andre Juffer [mailto:ajuffer@sun3.oulu.fi] 
Sent: Tuesday, April 16, 2002 1:53 AM
To: cocoon-users@xml.apache.org
Subject: Re: File Upload using action or any other approach



Olivier Rossel wrote:

>>
>>
>>> Hello?
>>>
>>>             Has anyone accomplished to upload files from html forms 
>>> to the server to a specific directory ..
>>
>>
>> Yes, I did, with an action. What is the problem? 
> 
> 
> Can you please explain how you did that?
> Or may be provide us the code, if it is not copyrighted?


Well, the code is protected, so I cannot give you that. But it can be 
accomplished very simply in your action. We did things in a SAX way:

1. Get the file name that is stored in one of parameters of the your 
Request object, originally set by the HTML form on the client. It should

point to a local file on the server into which the content of uploaded 
file is now stored. With Cocoon it will point to a location under 
<tomcat>/work. At least, in our case it does.

2. Define a Reader that reads from that file.

3. Define a Parser with a ContentHandler in the same way as you would do

for a SAX parser, but, of course, your Parser doesn't have to be a XML 
parser. The ContentHandler could simply write everything it receives 
into a local file at your choice. In this way, one can store the 
uploaded non-XML file into a local XML file, but with the possibility to

use filters, as in SAX.

4. Start parsing: parse(reader).


This is just one very simple possibility. If your uploaded file is 
already well-formed XML, you could use for instance Xindice to store it 
immediately into a XML database without modification.

If you don't need filtering and checking the content of your file, step 
2 to 4 can be done much simpler, but I found that solution for our 
purposes more flexible, since we dealing with non-XML input files. We 
will combine things with Xindice.

I am sure, others have better solutions.

Hopes this helps,
Andre.


> 
> 
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
> 
> To unsubscribe, e-mail: <cocoon-users-unsubscribe@xml.apache.org>
> For additional commands, e-mail: <cocoon-users-help@xml.apache.org>
> 


-- 
Andre H. Juffer              | Phone: +358-8-553 1683
The Biocenter and            | Fax: +358-8-553-1141
     the Dep. of Biochemistry | Email: Andre.Juffer@oulu.fi
University of Oulu, Finland  | WWW:
http://www.biochem.oulu.fi/Biocomputing/


---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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




---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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


Mime
View raw message