On Sat, 1 Jan 2005 11:24:23 +0100, Juergen Donnerstag wrote:
>> 1) We unify the resource path. You must place all your files in
>> /WebApp/ or /WebApp/WEB-INF/classes/ but not both.
>
>I'd like to skip that feature only for something really important.
What do you mean?
>> 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.
>
>I''m 100% against this approach. It means. whenever to deplay your app
>in another serv elt context, yoou have modify plenty of your markup
>files. You are no longer able to deploy v1 in /appTest1; a 2nd
>revision in /appTest2 without modification.
But Juergen...... this is how the Servlet framework works...
Wicket is based on top of the Servlet framework. This is naturely how
things work. I don't mind mapping "/" to the root path of the webapp
but then you must realize that it makes it impossible for one
application to refer to another application's resources. If you're fine
with that, I am fine with it too ... but pick one :)
>> 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
>>
>
>Wicket is about making things easy and intuitiv. From a user's point
>of view I would think: what the hell did they think about when they
>decided to go that road.
>
>Sorry Gili, but for me it doesn't sound like it is the solution.
>
>Just an idea: what about
>href="classpath:Home.html",
>href="classpath:/myDir/Home.html"
>href="sourcepath:...."
We need a standardized mechanism for mapping static resources
to Wicket classnames so we can automatically map one to the other. This
is exactly what you were asking for in a previous email when you asked:
how do we what Home.class maps to? HTML? Image? Well, this is how you
know. If you don't like my suggestion, feel free to come up with your
own mechaism for automatically mapping HTML links to Wicket resources.
My personal requirements is that HTML links should remain
normal HTML links (no special markups) and that there should be a way
to automatically map them to Wicket components.
You guys have disagreed with various aspects of my proposal,
but I've yet to hear better alternatives. I'm sure you have some good
ideas of your own. Please share them with the group.
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
