We have done an enormous effort to create a framework that largely works with handlers in request scope, for obvious reasons. Request takes mem, request processes, mem is purged.
Now this simple tree (with a complex model) results in a hidden jsf_state_64 field in the HTML of 6.4MB (SIX POINT FOUR MEGABYTES). BBEdit chokes on the line. We noticed that tree2 suddenly needs "some" things to be Serializable.
Question:
1) Is this changed already in more recent builds?
2) If not, you can't be serious, can you? When is this going to be changed back? Hopefully before the next release.
Now obviously we are going to switch to saving state on the server before deployment, but still. We did very much work to avoid storing large DataModels for dataTables in session scope. Are we to repeat this effort, with major workarounds, for tree2?
We've seen some mails about an option here? If this got implemented, can somebody please document it in a mail?
1) What is the name of the attribute, what are it's values?
2) What is the exact intention of it?
3) What does it do, what our the downsides of activating this?
<x-tad-smaller>Met vriendelijke groeten,
Jan Dockx
</x-tad-smaller><x-tad-smaller>
PeopleWare NV - Head Office</x-tad-smaller><x-tad-smaller>
Cdt.Weynsstraat 85
B-2660 Hoboken
Tel: +32 3 448.33.38
Fax: +32 3 448.32.66 </x-tad-smaller><x-tad-bigger>
</x-tad-bigger><x-tad-smaller>
PeopleWare NV - Branch Office Geel</x-tad-smaller><x-tad-smaller>
Kleinhoefstraat 5
B-2440 Geel
Tel: +32 14 57.00.90
Fax: +32 14 58.13.25</x-tad-smaller><x-tad-bigger>
</x-tad-bigger><x-tad-smaller>
http://www.peopleware.be/
</x-tad-smaller><x-tad-smaller>http://www.mobileware.be/</x-tad-smaller>
smime.p7s
Description: S/MIME cryptographic signature
