I'd then be circumventing the security architecture... I'm thinking
that it would be better to handle all parts through Wicket since
everything else is built in Wicket. If there is not a designed way to
do this, then a servlet may be the best option.
- Brill
On 27-Jul-08, at 1:15 PM, Igor Vaynberg wrote:
why not use a servlet?
-igor
On Sun, Jul 27, 2008 at 9:33 AM, Brill Pappin <[EMAIL PROTECTED]> wrote:
I've run into a bit of code that I'm not sure how to deal with (or
am not
sure what the wicket way would be).
I need to be able to serve raw bytes from dynamic files in the
system. Think
of it as a managed file download (although not exactly).
In a plain old servlet this would be fairly trivial, you'd simply
capture
the id of the resource and feed it back out or redirect... you
would be able
to do this with Wicket as well, but it seems a bit heavy to have to
read in
the bytes and write them out again using the
getRequestCycle().setRequestTarget(...) pattern.
I've been looking at Resource as one possibility, but am unsure how
to hook
this together..
Does anyone have some suggestions on how this might be done cleanly?
- Brill
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
