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
<[email protected]> 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 session
> cache, OR you plug in your own serialization support that doesn't need
> classes to be serializable).
>
> In this case though, you don't really need those members, right? All
> the members are used in methods that are called during construction of
> the panel, so why not just pass them through those methods (or if you
> don't like that, make the members transient)?
>
> Eelco
>
> On Fri, Oct 9, 2009 at 2:16 PM, Ceki Gulcu <[email protected]> wrote:
>>
>>
>> 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 DescriptionPanel class [1] you'll see that it essentially
>> presents a junit.Description and a junit.Failure instance both of which are
>> non-serializable.
>>
>> [1] http://tinyurl.com/yha75x8
>>
>>
>>> 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 you like.
>>
>> My application is a testing platform so I can't ignore junit nor testing.
>> :-)
>>
>> The backbutton, doh! Thanks.
>>
>>> Eelco
>>
>> --
>> Ceki Gülcü
>> Logback: The reliable, generic, fast and flexible logging framework for
>> Java.
>> http://logback.qos.ch
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to