On Tue, March 26, 2013, Martin Grigorov wrote:
> Can you reproduce the problem in a demo application? If YES - please attach
> it to a ticket in Jira. Thanks!
https://issues.apache.org/jira/browse/WICKET-5123
M'bert
--
--- / http://herbert.the-little-red-haired-girl.org / -
On Tue, March 26, 2013, Martin Grigorov wrote:
> Which version of Wicket do you use ?
6.6.0
> Can you reproduce the problem in a demo application? If YES - please attach
> it to a ticket in Jira. Thanks!
I'll have a look.
Cheers,
M'bert
--
--- / http://herbert.the-little-red-haired
Hi,
Which version of Wicket do you use ?
Can you reproduce the problem in a demo application? If YES - please attach
it to a ticket in Jira. Thanks!
On Tue, Mar 26, 2013 at 1:04 PM, Martin Dietze wrote:
> I found that in some situations, when
> Component.continueToOriginalDestination is called
I found that in some situations, when
Component.continueToOriginalDestination is called, the
InterceptionData object used there internally points to the home
page, i.e., the path element is empty. In that case the
RequestCycle's UrlRenderer.renderUrl() produces "./.".
This URL seems to cause probl
