doesnt the message of that exception tell you which object class is the problem?
On Wed, Aug 11, 2010 at 09:24, Thomas Singer wic...@regnis.de 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
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:
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
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 to
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 wic...@regnis.de wrote:
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
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 wic...@regnis.de wrote:
I want to
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
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
suggestion:
load your data and keep it in a cache
use LDM to retrieve the data from the cache (e.g. ehcache) or reload
it if it expired.
Am 10.10.2009 um 19:46 schrieb Igor Vaynberg:
if you do not need to hold on to the data structure between requests
then there is no need to keep any
Eelco Hillenius wrote:
I've looked at it briefly. The main thing you need to keep in mind is
that it unfortunately is a limitation of Wicket that you can't have
references in Components that aren't serializable (unless you don't
care about back button support and turn of the second level
Igor Vaynberg wrote:
On Fri, Oct 9, 2009 at 1:41 PM, Ceki Gulcu c...@qos.ch wrote:
Anyway, my application handles a complex tree-like structure, with
almost all of the contents non-serializable and outside my control. I
don't think I can use a Loadable Detachable Model, because loading the
what is the lifecycle of this data? when do you no longer need to store it?
if this is runtime data you can create a runtime store for it, even a
simple map can do. this map can live in servlet context, spring
context, as a field of your wicket application, etc. the user pages
can then retrieve
in other words, if you were building this app using jsps or servlets
how would you carry over this data structure between requests?
-igor
On Sat, Oct 10, 2009 at 9:09 AM, Igor Vaynberg igor.vaynb...@gmail.com wrote:
what is the lifecycle of this data? when do you no longer need to store it?
Igor Vaynberg wrote:
in other words, if you were building this app using jsps or servlets
how would you carry over this data structure between requests?
No, I actually would not carry the data between requests. When the
page is requested, I would run my test suite to compute the
results.
if you do not need to hold on to the data structure between requests
then there is no need to keep any references to it in the components
themselves. pass it into the constructor, create whatever components
you need to represent it in the ui and throw it away. you may have to
create wrappers
Hi,
It looks like GenericBaseModel has a reference to a JUnit Description?
Maybe you can paste your GenericBaseModel class here?
If that's something you'll have a runtime you shouldn't ignore it if
you want to support history (the backbutton). If it's just during
testing, you can ignore it if
Eelco Hillenius wrote:
Hi,
It looks like GenericBaseModel has a reference to a JUnit Description?
Maybe you can paste your GenericBaseModel class here?
Fortunately, my application is open source. You can find its source code at
http://github.com/ceki/mistletoe
If you look at the
I've looked at it briefly. The main thing you need to keep in mind is
that it unfortunately is a limitation of Wicket that you can't have
references in Components that aren't serializable (unless you don't
care about back button support and turn of the second level session
cache, OR you plug in
Btw, this whole serialization problem is exactly why we have
detachable models (though they obviously don't solve every problem out
there. Be sure to read up on those while you're at it.
Eelco
On Fri, Oct 9, 2009 at 3:12 PM, Eelco Hillenius
eelco.hillen...@gmail.com wrote:
I've looked at it
On Fri, Oct 9, 2009 at 1:41 PM, Ceki Gulcu c...@qos.ch wrote:
Anyway, my application handles a complex tree-like structure, with
almost all of the contents non-serializable and outside my control. I
don't think I can use a Loadable Detachable Model, because loading the
tree may take several
21 matches
Mail list logo
