> the name is not really a wicket-consistent name. IMarkupLocator
> would be more in line with the project's naming conventions... especially
> since it's likely to wrap things that implement IResourceStreamLocator.
>
> nice and consistent, nice and simple:
>
> public interface IMarkupLocator
> {
> String getMarkup(MarkupContainer container);
> }
Yeah, sorry about the name inconsistencies, I was leaving that part up to you.
I wasn't proposing to replace how you locate resources on the
filesystem, just how to resolve Page class names to their markup
(HTML) file names.
See my suggested interfaces and implementations. They only deal with
resolving the *name* of the HTML file, not even its full path. Wicket
already has a nice way to find resources (ResourceStreamLocator).
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
