Yes, I understand now. Thanks.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/FileUploadField-getClientFileName-doesn-t-give-Absolute-Path-tp3514910p3515021.html
Sent from the Users forum mailing list archive at Nabble.com.
---
Your app runs at the server.
The file is uploaded from the client machine.
How the full *client* path will be useful at the server ?
On Wed, May 11, 2011 at 4:39 PM, eugenebalt wrote:
> Another issue with the FileUpload,
>
> When I try to retrieve the specified filename with getClientFileName(),
Thanks. That's what I'm doing.
BTW, found this thread that explains why you can't get the full path:
http://apache-wicket.1842946.n4.nabble.com/Where-is-the-full-client-filename-during-FileUpload-td1876600.html
It's a security issue, if you could get the full path then you could have
access to ot
Keep in mind that with Wicket you are on the server side and on this
side the file you are uploading simply doesn't exist on file system (so
there's no absolute path).
With class FileUpload you can copy this file on your server (with method
writeTo(java.io.File file) ) OR you can simply read fil
Keep in mind that with Wicket you are on the server side and on this
side the file you are uploading simply doesn't exist on file system (so
ther's no absolute path).
With class FileUpload you can copy this file on your server (with method
writeTo(java.io.File file) ) OR you can simply read file
You can use getInputStream() of FileUpload
Duy
On 5/11/11 6:39 PM, eugenebalt wrote:
Another issue with the FileUpload,
When I try to retrieve the specified filename with getClientFileName(), I
only get the name of the file, without the absolute path. So I can't
construct a java.io.File obje
Another issue with the FileUpload,
When I try to retrieve the specified filename with getClientFileName(), I
only get the name of the file, without the absolute path. So I can't
construct a java.io.File object with just the filename. How do I get the
full path?
In the example at http://www.wicket
