> meanwhile, PackageResourceReference has been deprecated
You can just use ResourceReference instead.
Eelco
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance
wicket should assume I am referring to the package resource. What raises
this question is when CSS has to be reused across applications and all the
CSS and Image resources needs to be shared in a JAR irrespective of the
application context.
meanwhile, PackageResourceReference has been deprecated
Image image = new Image("img", new ResourceReference(HomePage.class,
"Circle.gif"));
isn't so bad, is it?
Eelco
On 12/4/06, Ayodeji Aladejebi <[EMAIL PROTECTED]> wrote:
>
> In wicket Image
>
> why cant one simply bind to a Packaged Resource Like this:
>
> Image image = new Image("img",new
> Mod
because it is not explicit
do you want packaged resource com/mypackage/Circle.gif
or do you want a static resource
/mycontext/com/mypackage/Circle.gif?
how is wicket to decide?
-igor
On 12/4/06, Ayodeji Aladejebi <[EMAIL PROTECTED]> wrote:
In wicket Image
why cant one simply bind to a P
In wicket Image
why cant one simply bind to a Packaged Resource Like this:
Image image = new Image("img",new Model("com/mypackage/Circle.gif"));
assuming my Circle.gif is found in that package context
Just why? there has to be a reason :) and please dont paste me this code:
PackageResource IM
