Thanks Thomas,
that was my first try. But the consequence is that i have to handle the
page parameter (foo) in the page.
With 1.4 we had a strategy for that with some tests. I would like to
migrate that.
Mike
It has some basic support for this, you can just
mountPage(ShowTheme-${foo},
Sorry Martin, but i don't get it to work.
I wrote a mapper:
import org.apache.wicket.request.IRequestHandler;
import org.apache.wicket.request.Request;
import org.apache.wicket.request.Url;
import org.apache.wicket.request.handler.BookmarkablePageRequestHandler;
import
You need to setup it as root mapper. This way it will be asked first
to map the request.
On Tue, Sep 6, 2011 at 10:16 AM, Mike Mander wicket-m...@gmx.de wrote:
Sorry Martin, but i don't get it to work.
I wrote a mapper:
import org.apache.wicket.request.IRequestHandler;
import
Ok now it's working.
My mapper looks like this.
import org.apache.wicket.request.IRequestHandler;
import org.apache.wicket.request.Request;
import org.apache.wicket.request.Url;
import org.apache.wicket.request.handler.PageProvider;
import
Hi,
i use StatelessChecker from dev-utils. In 1.4 if a page was not
stateless the checker told me the offending component.
But now in 1.5 i only get this message:
ERROR - DefaultExceptionMapper - Unexpected error occurred
java.lang.IllegalArgumentException: '[Page class =
That message means that you have a stateful behavior attached to the
page itself.
On Tue, Sep 6, 2011 at 1:04 PM, Mike Mander wicket-m...@gmx.de wrote:
Hi,
i use StatelessChecker from dev-utils. In 1.4 if a page was not stateless
the checker told me the offending component.
But now in 1.5 i
Hi Martin,
the page itself has no behavior attached. I use a stateless form with
behaviors on components.
On first call check is passed. If i don't provide values and press
submit (validation fails) then
StatelessChecker complains.
The page stateless flag is set by PageProvider
/**
This is fixed in trunk. The fix will be available in 1.5.1
On Tue, Sep 6, 2011 at 3:34 PM, Mike Mander wicket-m...@gmx.de wrote:
Hi Martin,
the page itself has no behavior attached. I use a stateless form with
behaviors on components.
On first call check is passed. If i don't provide values
Hello,
I have the following problem. I have a repeater which declares Images as
so:
NonCachingImage image1 = new NonCachingImage(image1, new
BufferedDynamicImageResource() {
private static final long serialVersionUID = 1L;
@Override
protected byte[] getImageData() {
return
Ah, thanks.
Mike
This is fixed in trunk. The fix will be available in 1.5.1
On Tue, Sep 6, 2011 at 3:34 PM, Mike Manderwicket-m...@gmx.de wrote:
Hi Martin,
the page itself has no behavior attached. I use a stateless form with
behaviors on components.
On first call check is passed. If i
Hello!
We're slowly migrating a big legacy jsp application into wicket and I'm
evaluating the ways incorporate wicket components into existing jsp pages.
Right now I'm trying to figure out how to include a wicket component through
jsp:include tag. As I've spent some time debugging I think that's
Few years back I also had to do this exercise. But we just started
removing JSP pages and replacing them with Wicket based ones.
So we just had to generate proper links in both directions.
Another approach which is similar to what you do is described at
We've been using Terracotta Sessions with Wicket successfully for some time
now with a fairly onerous side effect. The DiskPageStore temporary directory
grows steadily and never gets cleaned up, eventually leading to us having to
manually go and clean up the directory.
The issue appears to be
Actually, after thinking about this some more, it has nothing to do with the
jvmRoute on the session per se, it's because the node from which the session
originated never has the unbind/method called for that session.
On Tue, Sep 6, 2011 at 7:44 PM, Jeremy Levy jel...@gmail.com wrote:
We've
14 matches
Mail list logo