RE: Problem with relative URLs

2012-01-10 Thread Chris Colman
to BookmarkablePageLink tags (and any classes derived from BookmarkablePageLink)? -Original Message- From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] Sent: Tuesday, 10 January 2012 2:44 PM To: users@wicket.apache.org Subject: Re: Problem with relative URLs wicket by default always generates

Re: Problem with relative URLs

2012-01-10 Thread Martin Grigorov
[mailto:igor.vaynb...@gmail.com] Sent: Tuesday, 10 January 2012 2:44 PM To: users@wicket.apache.org Subject: Re: Problem with relative URLs wicket by default always generates relative urls. this is the safest/easiest approach for fronting the app with a proxy, which most people do... -igor On Mon

RE: Problem with relative URLs

2012-01-10 Thread Chris Colman
Am I right in saying that RelativepathPrefixHandler should never even be applied to BookmarkablePageLink tags (and any classes derived from BookmarkablePageLink)? At least its source doesn't indicate that BPL should be treated specially. I've made some inroads: I got a quickstart to fail by

RE: Problem with relative URLs

2012-01-10 Thread Chris Colman
The problem is related to non standard (i.e. wicket) namespaces. In my quickstart if I change the namespace in all markup from wicket to foobar then the BPL which has only the last segment differing from the current page ends up producing an incorrect link to another page in the same path. i.e.

RE: Problem with relative URLs

2012-01-10 Thread Chris Colman
I've just submitted a JIRA issue with quickstart for this issue: https://issues.apache.org/jira/browse/WICKET-4330 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail:

Re: Problem with relative URLs

2012-01-09 Thread Igor Vaynberg
On Mon, Jan 9, 2012 at 5:51 PM, Chris Colman chr...@stepaheadsoftware.com wrote: I'm having a problem with relative URLs. If the current page is: content/mypage/n1/p1/n2/fred And it contains a link to content/mypage/n1/p1/n2/jane The relative URL rendered to HTML is:

RE: Problem with relative URLs

2012-01-09 Thread Chris Colman
I looked at the URL renderer and it was returning just 'jane' instead of ../jane actually jane is correct and ../jane is incorrect. if the browser is on content/mypage/n1/p1/n2/fred then going to a relative url jane will produce content/mypage/n1/p1/n2/jane which is what you want, no...?

RE: Problem with relative URLs

2012-01-09 Thread Chris Colman
why is RelativePathPrefixHandler invoked on that tag? sounds a little funky... -igor I'm using UrlPathPageParametersEncoder for backwards compatibility with 1.5 links. I'm not sure if that could be causing the funkiness of RelativePathPrefixHandler being invoked. Are BookmarkablePageLinks

Re: Problem with relative URLs

2012-01-09 Thread Igor Vaynberg
wicket by default always generates relative urls. this is the safest/easiest approach for fronting the app with a proxy, which most people do... -igor On Mon, Jan 9, 2012 at 6:59 PM, Chris Colman chr...@stepaheadsoftware.com wrote: why is RelativePathPrefixHandler invoked on that tag? sounds a

RE: Problem with relative URLs

2012-01-09 Thread Chris Colman
wicket by default always generates relative urls. this is the safest/easiest approach for fronting the app with a proxy, which most people do... -igor I guess there are three types of urls: Relative: Url with no leading protocol or '/' Absolute: Urls with a leading / Complete: Urls with