BookmarkableMapper produces something like:
/wicket/bookmarkable/com.example.MyPage
There is a mistake in the line below, it should be
WebApplication#mountBookmarkable(pageClass) which will
call getRootRequestMapperAsCompound().add(new
BookmarkableMapper(pageClass));
i.e. without the "path"
mount
How is your last suggestion different from mount page you mention first ?
Jeremy Thomerson
http://wickettraining.com
-- sent from my "smart" phone, so please excuse spelling, formatting, or
compiler errors
On Nov 27, 2010 12:17 PM, "Martin Grigorov" wrote:
Hi,
Currently we have :
WebApplicatio
Ernesto,
In the below snippet, sometimes it is not possible to ONLY include the
content of the modal dialog in the ajax target. There are times where a
parent of the dialog may be added to another AjaxRequestTarget (for some
reason other than just updating the dialog window - maybe to update a
Hi,
I'm trying to port my Wicket testcase to 1.5, and it looks like, that
WicketTester#createRequestCycle() is gone now.
The test case is:
* create a session
* set a configuration option with a form
* invalidate session
* create new session
* assert that the session#getStyle now returns somethi
Hello,
I encountered the same problem. I found using addToBorder rather than add
fixed it though:
public NavomaticBorder(final String id)
{
super(id);
addToBorder(new BoxBorder("navigationBorder"));
addToBorder(new BoxBorder("
Hi,
Currently we have :
WebApplication.mountPage(path, pageClass) which is a shortcut for
WebApplication.getRootRequestMapperAsCompound().add(new MountedMapper(path,
pageClass));
and org.apache.wicket.protocol.http.WebApplication.mountSharedResource(String,
ResourceReference) which is:
getResourc
Hi,
is there some specific reason, why WebApplication#mount is deprecated in
1.5? It could be a really good shortcut:
mount(new MyMapper("", A.class);
rather then:
getRootRequestMapperAsCompound().add(new MyMapper("", A.class));
also PackageMapper looks really weird:
mount(new MountMapper("/er
Oh yes, I've forgotten to mention patch file. But keep in mind that it
could not work under IE6...
I just noticed that autosizing ModalWindows has made it into Wicket 1.5, heres
the JIRA:
https://issues.apache.org/jira/secure/attachment/12456436/fix-WICKET-1.4.x.patch
Take a look at the patches
I just noticed that autosizing ModalWindows has made it into Wicket 1.5, heres
the JIRA:
https://issues.apache.org/jira/secure/attachment/12456436/fix-WICKET-1.4.x.patch
Take a look at the patches, there is a method that sets the size of the window,
might be something to borrow.
cheers,
Steve