Hmmm, does that imply that one of the member variables may be Serializable?
On 25 Apr 2010, at 05:18, Igor Vaynberg wrote:
the exception might have caused your page to not be serialized
properly into the pagestore
-igor
On Sat, Apr 24, 2010 at 6:06 PM, Douglas Ferguson
That means one of your fields might *not* be Serializable. The error
message usually tells you the exact field that caused the problem (in
development mode).
On Sun, Apr 25, 2010 at 8:26 AM, Nico Guba ng...@mac.com wrote:
Hmmm, does that imply that one of the member variables may be
we use ajaxfallbackdefaultdatatable ,it provides pagination on top,can I
pagination both on top as well as bottom ?,
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/pagination-both-bottom-and-top-ajaxfallbackdatatable-tp2064202p2064202.html
Sent from the Wicket -
Try clean and build, you might break your application.
Sent from my Nokia phone
-Original Message-
From: Igor Vaynberg
Sent: 24/04/2010 23:10:15
Subject: Re: Persistence.xml problem
wicket has nothing to do with it. maybe your IDE is not updating your
persistence.xml in the target
add the navigation toolbar to the bottom, see addbottomtoolbar
-igor
On Sun, Apr 25, 2010 at 6:03 AM, fachhoch fachh...@gmail.com wrote:
we use ajaxfallbackdefaultdatatable ,it provides pagination on top,can I
pagination both on top as well as bottom ?,
--
View this message in context:
No , is ant .
Subject: Re: Persistence.xml problem
From: ng...@mac.com
Date: Sun, 25 Apr 2010 15:41:07 +0100
To: users@wicket.apache.org
Is maven your build system?
On 25 Apr 2010, at 14:46, Matias Pansa wrote:
I try clean and build many times with the same result , i try
No.. this is not a serialization issue, unless Igor is correct in that fact
that the exception prevents serialization. But how would that effect the back
button,
should the page on the back button have already been serialized?
Say if I get a hibernate failed to lazy load exception, then I hit
Anybody have tips on the correct way to do this?
On Apr 24, 2010, at 5:42 PM, Douglas Ferguson wrote:
I'm curious about how this would work with serialization/deserialization.
For instance, with a data provider where would you actually put this:
InjectorHolder.getInjector().inject(this)
It would affect the back button because when Wicket tries to go get
the specific version of the page back from the session store (only the
current version is kept in the session and the earlier ones are in
the store), it won't be able to find it.
On Sun, Apr 25, 2010 at 11:45 AM, Douglas Ferguson
I meant page store, not session store.
On Sun, Apr 25, 2010 at 12:26 PM, James Carman
jcar...@carmanconsulting.com wrote:
It would affect the back button because when Wicket tries to go get
the specific version of the page back from the session store (only the
current version is kept in the
I also updated the exception message in commit 937854.
--
Jeremy Thomerson
http://www.wickettraining.com
On Thu, Apr 8, 2010 at 7:26 AM, Martin Grigorov mcgreg...@e-card.bg wrote:
The ticket for this is https://issues.apache.org/jira/browse/WICKET-2761
The fix is applied to 1.4.x at 13/03
ModalPanel is unsecure - as you can hide it using JavaScript
But if you still want to do that - then you can add the modal panel to
your ScurePage - which all your other pages extend - display it
every time if the user is not logged in.
Žilvinas Vilutis
Mobile: (+370) 652 38353
E-mail:
12 matches
Mail list logo
