after viewing a page, when the page gets serialized
But you could also trigger it your self,
for example you can have something in the detach() of your base page
super.onDetach()
if (development)
{
Objects.objectToByteArray(this)
}
then you should get the same error right away
On Wed, Aug 11,
When exactly the serialization happens? When viewing a page?
Tom
On 11.08.2010 13:25, Johan Compagner wrote:
> the only way to do this is as i described look where the exception
> really comes from
> and go to that same page in your developer, do as your user does.
> There is no other way, you r
the only way to do this is as i described look where the exception
really comes from
and go to that same page in your developer, do as your user does.
There is no other way, you really need to be in the same state.
On Wed, Aug 11, 2010 at 13:24, Thomas Singer wrote:
> I want to know how I can ge
I want to know how I can generate this exception in my development
environment. It is nasty to test on the production system.
Tom
On 11.08.2010 10:53, Johan Compagner wrote:
> why not?
> if you know which page it was and which component/model that holds
> that none serializable class
> then you
why not?
if you know which page it was and which component/model that holds
that none serializable class
then you just have to make sure that you go to that same area in your
developer..
What else do you expect that you can do?
On Wed, Aug 11, 2010 at 10:29, Thomas Singer wrote:
> Unfortunately,
Unfortunately, this does not answer my question.
Tom
On 11.08.2010 09:57, Johan Compagner wrote:
> then you just have to check where those classes are used and where
> they could be stored in a wicket component/model
> and make sure you detach that object .
> Wicket tells you the field hierarchy
then you just have to check where those classes are used and where
they could be stored in a wicket component/model
and make sure you detach that object .
Wicket tells you the field hierarchy to that object so you should be
able to track it down quite easily
On Wed, Aug 11, 2010 at 09:55, Thomas
> doesnt the message of that exception tell you which object class is the
> problem?
It does, but I don't want to make the logged class serializable, but instead
avoid it. Independent of that I want to verify whether the done steps work
correctly.
Tom
On 11.08.2010 09:27, Johan Compagner wrote
doesnt the message of that exception tell you which object class is the problem?
On Wed, Aug 11, 2010 at 09:24, Thomas Singer wrote:
> Hi,
>
> In our server logs we have a couple of WicketNotSerializableException
> logged, but we don't know when they occur. How we can create them locally in
> ou
Hi,
In our server logs we have a couple of WicketNotSerializableException
logged, but we don't know when they occur. How we can create them locally in
our development environment (to test whether we have avoided them)?
Thanks in advance,
Tom
--
10 matches
Mail list logo
