> i think /markup location/ and /resource stream location/ are two > separate problems.
Yeah, this is why I don't like the word "location" used when resolving markup page names. The location word is already successfully used by the ResourceStreamLocator (since 'locate' in this sense is "find the thing in many different possible places") > > i think "page name resolution" (whatever that is) is a subclass of the > markup location problem. Maybe this is my problem. What do you mean by "markup location" ? How is that different than ResourceStreamLocator ? Thanks, Seth ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
