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
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.
3. Document the valid path syntax (and limitations) in the Wiki, WIA, etc.
Phil
On Sun, Mar 16, 2008 at 11:46 AM, James Carman <[EMAIL PROTECTED]>
wrote:
> On 3/16/08, Phil Grimm <[EMAIL PROTECTED]> wrote:
> > That's funny, I was about to post regarding the numerous issues with
> > <wicket:link>...
> >
> > And one suggestion I was going to give was to add support for
> > "../packge/Page.html".
> > I don't think it currently supports this, at least I couldn't see it
> from a
> > code examination.
> >
>
> Ok, thanks, Phil. I thought I was doing it correctly. My HTML can be
> viewed in the browser for a "preview" just fine. Maybe we should file
> a JIRA enhancement request?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Phil Grimm
Mobile: (858) 335-3426
Skype: philgrimm336
