The only problem with having to look at the console is that sometimes
other logging can make that stuff fly by. And, if you're not watching
it, it's not obvious there's a problem. Perhaps a better solution
might be to check serializability using a unit test rather than by
exercising the pages man
well, then check who removed them and ask them why they did that...
personally i dont mind looking into the console, but thats just me...
-igor
On Mon, Aug 11, 2008 at 2:10 PM, James Carman
<[EMAIL PROTECTED]> wrote:
> But, it's in a separate thread, right? So, you'll have to look for
> error m
But, it's in a separate thread, right? So, you'll have to look for
error messages in a log file (or console window). Would a more
drastic response (error in the browser) be more appropriate during
development?
On Mon, Aug 11, 2008 at 11:34 AM, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> with the
with the default diskstore pages are always serialized...
-igor
On Mon, Aug 11, 2008 at 8:23 AM, Thomas Mäder <[EMAIL PROTECTED]> wrote:
> Ah bugger! That was most convenient! I'd be very much in favor of it's
> making a comeback
>
> Thomas
>
> On Mon, Aug 11, 2008 at 4:56 PM, Jonas <[EMAIL PROTE
Ah bugger! That was most convenient! I'd be very much in favor of it's
making a comeback
Thomas
On Mon, Aug 11, 2008 at 4:56 PM, Jonas <[EMAIL PROTECTED]> wrote:
> It seems this feature was removed, but there's some javadoc
> left in org.apache.wicket.settings.IDebugSettings:
> [quote]
> seriali
It seems this feature was removed, but there's some javadoc
left in org.apache.wicket.settings.IDebugSettings:
[quote]
serializeSessionAttributes (defaults to true in development
mode) - Causes the framework
* to serialize any attribute put into session - this helps find Not
Serializable errors ea
Yeah, but wasn't there "official" support for that? And if not, wouldn't
this be useful for debug?
Thomas
2008/8/11 Uwe Schäfer <[EMAIL PROTECTED]>
> Thomas Mäder schrieb:
>
>
> I seem to remember that there was a way to force Wicket to always
>> serialize
>> pages on detach in order to make su
Thomas Mäder schrieb:
I seem to remember that there was a way to force Wicket to always serialize
pages on detach in order to make sure every page is serializable during
development. Can someone please point me to the FM so I can read it?
Searching Nabble & Google didn't turn up anything.
one
Hi Guys,
I seem to remember that there was a way to force Wicket to always serialize
pages on detach in order to make sure every page is serializable during
development. Can someone please point me to the FM so I can read it?
Searching Nabble & Google didn't turn up anything.
this is 1.3.3
Thoma
