Hi Krzysztof,
Sorry to hear that, I must admit I never thought of testing this with forms. I
just assumed that the form would have a wicket generated URL and that from that
point on it would work the normal way.
Regards,
Erik.
Op 02-12-10 16:32, Krzysztof Kowalczyk wrote:
Thank you
Thank you Erik, the idea is nice, but it does not work ;)
I wanted to implement my own ~ Root Mounting Strategy just when I've
got your email. The idea with overriding getRequestPath sounds good, I
was afraid that I will need to implement my own RequestCycle with
custom logic replacing
The code in Wicket 1.4.14 is the same. There is still lines that causes problem:
if (!Strings.isEmpty(forwardUrl))
{
// If this is an error page, this will be
/mount or /?wicket:foo
relativeUrl = forwardUrl.substring(1);
You can try the approach from
http://blog.jteam.nl/2010/02/24/wicket-root-mounts/
This allows you to install a URL mounter that implements the following
interface:
interface RootMountedUrlCodingStrategy {
boolean accepts(String rawPath);
}
Regards,
Erik.
Op 30-11-10 11:21, Krzysztof
Hi,
We have existing urls in a form:
/long,and,complex,title,id/new_opinion
/long,and,complex,title,id/something
or sometimes
/long,title/id/new_opinion
The links like /long,and,complex,title are managed by fast and
scalable view, and are stateless. Now we are using Wicket in the same
war. It
first figure out why its failing - why is wicket generating a wrong
url, and then you can determine if its a bug in wicket or somewhere in
your configuration.
-igor
On Tue, Nov 30, 2010 at 2:21 AM, Krzysztof Kowalczyk
kowalczyk.krzysz...@gmail.com wrote:
Hi,
We have existing urls in a form:
As I have already written in previous mail (pointing to exact line
that cause the errors) - Wicket is falling because it handles
forwardUrl in incorrect way. It tries to remove / and filterPath
from forwardUrl even though forwardUrl does not contain filterPath. I
guess that it is because of an
you must be using an old wicket version...upgrade to latest 1.4.x
-igor
On Tue, Nov 30, 2010 at 8:34 AM, Krzysztof Kowalczyk
kowalczyk.krzysz...@gmail.com wrote:
As I have already written in previous mail (pointing to exact line
that cause the errors) - Wicket is falling because it handles
We use Wicket 1.4.12.
On Tue, Nov 30, 2010 at 5:43 PM, Igor Vaynberg igor.vaynb...@gmail.com wrote:
you must be using an old wicket version...upgrade to latest 1.4.x
-igor
On Tue, Nov 30, 2010 at 8:34 AM, Krzysztof Kowalczyk
kowalczyk.krzysz...@gmail.com wrote:
As I have already written in
upgrade to 1.4.14 because that code looks different for me.
-igor
On Tue, Nov 30, 2010 at 9:03 AM, Krzysztof Kowalczyk
kowalczyk.krzysz...@gmail.com wrote:
We use Wicket 1.4.12.
On Tue, Nov 30, 2010 at 5:43 PM, Igor Vaynberg igor.vaynb...@gmail.com
wrote:
you must be using an old wicket
Ok, thanks, I will try it tomorrow
On Tue, Nov 30, 2010 at 6:07 PM, Igor Vaynberg igor.vaynb...@gmail.com wrote:
upgrade to 1.4.14 because that code looks different for me.
-igor
On Tue, Nov 30, 2010 at 9:03 AM, Krzysztof Kowalczyk
kowalczyk.krzysz...@gmail.com wrote:
We use Wicket 1.4.12.
11 matches
Mail list logo
