Gili wrote:
That's why I've stated before I think we should disallow thesorry, i'm not really following this conversation, but this sounds extreme to me.
ability to store HTML files both under /WebApp/ and
/WebApp/WEB-INF/classes/ -- force one or the other. Otherwise it could
lead to confusing behavior for the user. If we force all HTML files
under a single root path we guarantee consistent behavior and no name
collisions.
if you're forced to put all your HTML files in the classes folders, haven't you
essentially excluded any possibility of integration with anything else? also, what
about sites that are 90% static files? why should those belong in classes?
Juergen didn't like this idea because:
I like the possibility to put my markup in two different locations:
classpath and (configurable) sourcepath. Makes life easier, when you
think about 3rd parties providing a jar with their components and you
want to replace some of there markup without being able to modifiy the
sources.
so we need to address his concern as well. Personally my view is: by default (if no other mapping exists) we use the CLASSPATH as a search path. Force everyone to dump their HTMLs into /WebApp/WEB-INF/classes/ -- which is part of the CLASSPATH -- and if you really want to override 3rd party markups, you explicitly add mappings to ResourceLocator to override the default behavior. We can document that ResourceLocator is treated as if it was the first entry of the CLASSPATH, so the behavior is consistent.
Gili
On Sat, 01 Jan 2005 20:57:58 +0100, Johan Compagner wrote:
normally (if you don't set a sourcepath in the ApplicationSettings) the html must be beside the class.
So in the package.
But a href to something in a page can contain this: Xxxx.html
That thing could be a normal (no wicket component html file) that is in the webroot
Or it could be a html file that is a wicket component.
Maybe this isn't something that will happen but it can be very confusing for a user
if this happens. And he will not really know what suddenly happens...
If he expects X but suddenly Y happens
johan
Gili wrote:
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
------------------------------------------------------- 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
------------------------------------------------------- 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
------------------------------------------------------- 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
