Just iterate over all attributes in the session. They should be Serializable. If not -> ignore them.
LieGrue, strub > On Wednesday, 4 February 2015, 19:52, Romain Manni-Bucau > <[email protected]> wrote: > > @Karl: if you didnt wrap it just use session fielf of the session you > get (by reflection). Should be serializable > > > Romain Manni-Bucau > @rmannibucau > http://www.tomitribe.com > http://rmannibucau.wordpress.com > https://github.com/rmannibucau > > > 2015-02-04 19:49 GMT+01:00 <[email protected]>: >> Hello Mark, httpsession does not implement Serializable and tomcat > sessionholder does not. The actual session is not obtainable :( >> >> Skickat från min iPhone >> >>> 4 feb 2015 kl. 16:52 skrev Mark Struberg <[email protected]>: >>> >>> did that via a SerlvetFilter and just serialized the session into a > byte[] and output the size. As benefit you also see early on whether you have > something which is not properly Serializable and would fail on a cluster. >>> >>> LieGrue, >>> strub >>> >>> >>> >>> >>> >>>>> On Monday, 2 February 2015, 20:01, Karl Kildén > <[email protected]> wrote: >>>>> Hello! >>>> >>>> Anyone got some ideas on how to measure session size? >>>> >>>> I serialized the JSF sessionmap and it gave some hints but seems > not >>>> everything is there. If I CDI scope with Session and put a lot of > stuff in >>>> my bean the JSF map does not grow and I can't figure out how to > serialize >>>> the session manually... >>>> >>>> If anyone knows exactly how viewstate and sessionstate is stored > for a >>>> modern CDI/JSF application I would be glad to hear about some > internals. >>>> >>>> I have no issues - just want to know this so I can keep tabs as my > app grows >>>> >>>> cheers >>>> >
