Oh, actually I made the StringResponse serializable yesterday as I
thought it was temporarily set somewhere else. But now... I don't know
what I was thinking as indeed Matej, that doesn't solve the fact that
that response shouldn't be in there in the first place. It is a show
stopper though.
Eelco
On 11/22/06, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
* Matej Knopp:
> I believe that patch wasn't meant to be applied against
> 1.2.3. It's should be applied against 1.x (1.3), which I believe
> it already was.
>
> Making StringResponse serializable is not a good idea IMHO, as
> the problem is somewhere else. The response classes should never
> be stored in session.
AFAICT the StringResponse is part of the ResponseHeader, as Wicket
is adding this to the header:
<script type="text/javascript" ><!--/*--><![CDATA[/*><!--*/
if (window.name=='') { window.name="wicket:default"; }
/*-->]]>*/</script>
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
