Well, thanks a lot, thats really much more simple then i figured =P. Maybe
any pointers why the stream from the file system doesnt work? ;)
igor.vaynberg wrote:
your problem is not retreiving the data from the db - it is the weird
stuff
you try to do when stream it back to the browser. why
it easily)
Regards,
Korbinian
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag
von Sebastian Pflugbeil
Gesendet: Mittwoch, 23. August 2006 11:24
An: wicket-user@lists.sourceforge.net
Betreff: Re: [Wicket-user] best practice for uploading
11:24
An: wicket-user@lists.sourceforge.net Betreff: Re: [Wicket-user] best practice for uploading and using content (images) with wicket?
Well, thanks a lot, thats really much more simple then i figured =P. Maybe any pointers why the stream from the file system doesnt work? ;) igor.vaynberg wrote
Hi,
I haven't read through your whole email, but the cdapp example in
wicket-contrib-examples which you can find in the wicket-stuff
repository has functionality for uploading an image (edit details of a
cd), which is then stored in the database. That image is then
displayed as a thumbnail and
your problem is not retreiving the data from the db - it is the weird stuff you try to do when stream it back to the browser. why all the awt image stuff? all you have to do is read the byte array from the db and stream it back to the browser.
here is some pseudo codeadd(new Image(myimage) {
