Here's a revision that better addresses Eelco and Juergen's
concerns.
1) We unify the resource path. You must place all your files in
/WebApp/ or /WebApp/WEB-INF/classes/ but not both.
2) Contrary to my previous email, you can refer outside the WebApp.
Refering to "/" refers to the root path on the server, *not* the
WebApp. If you wish to refer to the root of your WebApp, you're
supposed to use "/WebApp". I believe JSP works the same way.
3) Extend autolink to work for *any* resource (including images) by
encoding the markup type into the class name. That is,
/WebApp/WEB-INF/classes/MyPage.class becomes
/WebApp/WEB-INF/classes/MyPage$html.class
The general markup would be <path>/<class name>$<markup
name>.class
This would allow autolink to automatically map static resources
to Wicket components. If you refer to a resource (say an image file)
and there is no associated component with it, Wicket simply streams its
contents. This will ensure static resources continue to function the
same way they did before migration to Wicket.
Eelco, Juergen, are there any further concerns?
Gili
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
