one thing that makes me think adding parameterization to a subclass is
wrong is
that every Resource should be parameterizable. and that should really
have nothing
to do with where the resource is streamed from. one can even imagine a
resource
where the resourcestream implementation returned differs depending on
the parameters.
Johan Compagner wrote:
ooooh. very sneaky!
it's my middle name ;)
i like it. but maybe we can provide a little helper subclass so
people don't have to
do this to get resource parameters:
Map params = RequestCycle.get().getRequest().getParameterMap();
that takes a bit more knowledge of wicket than most people probably
have.
yes thinking in the same direction.
Just need something as below as default implementation
And they only have to implement one method:
public InputStream getInputStream(Map params)
{
}
And i have to fix one think more in the handling of the last
modified/cacheable nature of resources (i am on that)
johan
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle
Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing
& QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
