Hi to all. This is my first post, here's a quick introduction of myself. My name is Fabrizio Giudici, I'm a senior architect and I've been working with Wicket for a bit more than one year.
I've recently upgraded to 1.3 (I was working with an 1.3 snapshot that dated back to a few months ago) and I've got a project that is exiting from the "prototype" stage and should go into production in a matter of weeks. I'm doing a final review of the code, considering that some of the older portions weren't probably very good (it is my first Wicket project) and something changed with 1.3. Here's my list of question - I apologize as I bet there's something more or less trivial, of course I've already done some searches around but I wasn't able to find good answers (or I didn't understand them ;-) : 1. I've always experienced some sudden "session expiration" problems with no apparent reason (I mean, the user wasn't actually sleeping). But they happened only once in a while. After upgrading to 1.3 they occur very often and they have quickly become the issue on the top of the list and I've to fix it immediately, since it's jeopardizing the acceptance tests performed by my customer. I've already searched in forums and tried some change (such as disabling versioning), but I got no benefit from it. 2. I have a modal window used to enter a date (I can't use the already provided component since this a special date) that has been working from several months. After upgrading to 1.3 it deterministically causes a session expired whenever it's closed (since this is deterministic I bet it's a different thing than the above). 3. I have still some confusion about serialization of things in sessions. I've always got some objects that are not serializable and caused tons of exceptions in log files, but no harm other than it. I'm now wondering whether they can trigger one of the above problems, and anyway before going into production I'd like to face with this issue in a definitive fashion. I know about the possibility of using detachable objects, nevertheless I need first to understand why this serialization thing can't be disabled - after all I've got no need for clustering in near future (and if I should do it, I'd probably go with Terracotta). Also, in version 1.2 I once saw that there was a UserSession (?) method that looked like it was useful for disabling serialization, and I had a mental note about using it, but it looks like it disappeared in 1.3.0. Hints? Thanks in advance.. -- Fabrizio Giudici, Ph.D. - Java Architect, Project Manager Tidalwave s.a.s. - "We make Java work. Everywhere." weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/blog [EMAIL PROTECTED] - mobile: +39 348.150.6941 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
