On 3/16/08, Phil Grimm <[EMAIL PROTECTED]> wrote: > I think a JIRA request is appropriate. > Perhaps we'll hear a confirmation from the Wicket developers. > > I'd add the following to the request... > > 1. Add support for "../" relative path resolution
+1 - This is essential and shouldn't be very difficult, IMHO (without looking at the code). A few unit tests should verify this behavior. I might even submit the patch myself. > 2. Add support for searching the classpath (if absolute and relative search > fails) > -- I think this is reasonable, but there may be issues here > -- This is the only way to have <wicket:link> paths continue to work > even after refactoring pages/packages. I don't know about this. In my IDE (IntelliJ IDEA), if I move the HTML template, the links in my other pages automatically get updated. So, this is a non-issue for me. Also, pages could be named the same thing in multiple packages. For instance, suppose you have a project with multiple "modules" (customers, inventory, accounts, etc.). Each "module" could have its own HomePage. > 3. Document the valid path syntax (and limitations) in the Wiki, WIA, etc. > +1 - but it should at least be in the Wiki, though. I remember getting frustrated when seeing replies on the Tapestry lists that said "Buy Kent Tong's book." Don't get me wrong, his book was/is good, but having to pay for documentation for an Apache project just seems wrong to me. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
