are you talking about 1.2 or 1.3?
in 1.2 a session could grow a little bit because we have there max 7 pages
that all also can contain some version info.
But as you said when you do setResponsePage(Page.class) everything drops to
normal
that means that you have to use 1.3 because then the newly
ok found it, We are leaking auto add html header containers.
Looking to fix it.
On 10/3/07, Johan Compagner [EMAIL PROTECTED] wrote:
are you talking about 1.2 or 1.3?
in 1.2 a session could grow a little bit because we have there max 7 pages
that all also can contain some version info.
Hi,
thanks for the quick response. Should I open a JIRA issue for this or is it
to minor to justify the overhead?
bw,
Martin
Johan Compagner wrote:
ok found it, We are leaking auto add html header containers.
Looking to fix it.
On 10/3/07, Johan Compagner [EMAIL PROTECTED]
i think johan already fixed it in trunk.
gerolf
On 10/3/07, Martin2 [EMAIL PROTECTED] wrote:
Hi,
thanks for the quick response. Should I open a JIRA issue for this or is
it
to minor to justify the overhead?
bw,
Martin
Johan Compagner wrote:
ok found it, We are leaking auto
jip, but open and close a jira if you want to have this in the change list..
On 10/3/07, Gerolf Seitz [EMAIL PROTECTED] wrote:
i think johan already fixed it in trunk.
gerolf
On 10/3/07, Martin2 [EMAIL PROTECTED] wrote:
Hi,
thanks for the quick response. Should I open a JIRA issue
I'm using trunk right now and the issue is resolved, the session size does
not increase anymore when setting the response page. Since this was a
critical one on our issue tracking, thanks for the quick fix.
I opened jira https://issues.apache.org/jira/browse/WICKET-1036 WICKET-1036
and I'll
