the other option puts the resources into a jar. so if you have a reusable
component that comes as a jar file wicket knows how to find them without you
as a user of that component needing to do anything.
-igor
On 11/17/06, Ian Clarke <[EMAIL PROTECTED]> wrote:
On 17 Nov 2006, at 21:34, Eelco Hillenius wrote:
If you don't want to package them (e.g. you don't need them as part as
a reusable component), just put them in your web app dir (you know,
the one with WEB-INF in it). Your application server will figure out
how to get them. If you want them to be packaged, you typically put
them in the same java package as where your component class resides,
and use something like HeaderContributor to serve them.
Much appreciated.
So I have the web app dir thing working, but I'm curious, why might I want
to go with the other option?
thanks,
Ian.
*Ian Clarke*: Co-Founder & Chief Scientist Revver, Inc.<http://revver.com>
phone: 323.871.2828 | personal blog - http://locut.us/blog
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
