Please, unsubscribe him, I'm getting such reply for each email i send to this maillist.
---------- Forwarded message ---------- From: <[email protected]> Date: 2009/12/8 Subject: DELIVERY FAILURE: Invalid/unknown recipient [MAPI Reason Code: 1, MAPI Diagnostic Code 1] To: [email protected] Your message Subject: Re: Questions about Serialization... was not delivered to: [email protected] because: Invalid/unknown recipient [MAPI Reason Code: 1, MAPI Diagnostic Code 1] ******************** NOTICE OF CONFIDENTIALITY This communication including any information transmitted with it is intended only for the use of the addressees and is confidential. If you are not an intended recipient or responsible for delivering the message to an intended recipient, any review, disclosure, conversion to hard copy, dissemination, reproduction or other use of any part of this communication is strictly prohibited, as is the taking or omitting of any action in reliance upon this communication. If you receive this communication in error or without authorization please notify us immediately by return e-mail or otherwise and permanently delete the entire communication from any computer, disk drive, or other storage medium. If the above disclaimer is not properly readable, it can be found at www.td.com/legal AVERTISSEMENT DE CONFIDENTIALITE Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement aux destinataires susmentionnés, est confidentiel. Si vous n'êtes pas le destinataire prévu ou un agent responsable de la livraison de ce courriel, tout examen, divulgation, copie, impression, reproduction, distribution, ou autre utilisation d'une partie de ce courriel est strictement interdit de même que toute intervention ou abstraction à cet égard. Si vous avez reçu ce message par erreur ou sans autorisation, veuillez en aviser immédiatement l'expéditeur par retour de courriel ou par un autre moyen et supprimer immédiatement cette communication entière de tout système électronique. Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous pouvez le consulter à www.td.com/francais/legale Final-Recipient: rfc822;[email protected] Action: failed Status: 5.0.0 Diagnostic-Code: X-Notes;Invalid/unknown recipient [MAPI Reason Code: 1, MAPI Diagnostic Code 1] ---------- Пересылаемое сообщение ---------- From: [email protected] To: <[email protected]> Date: Tue, 8 Dec 2009 14:39:24 -0500 Subject: Re: Questions about Serialization... 2009/12/8 Yves-Marie LAINÉ <[email protected]>: > Hi, > > I'm new on the list, sorry if my question has already been asked. I didn't > find the right answer on google. > > Is it possible tu use wicket without Page serialization ? It is. Use only stateless components. > Technically, is it possible to imagine a SimpleHttpSessionPageStore that > don't serialize objects and keep them as they are in session, like it's done > in others frameworks ? Logic flaw: session contents CAN get serialized. Read Servlet spec, you shouldn't put non-serializable stuff in session. > But... I'm working on an app that consist of few pages, not versioned (no > need of the back button support), because I need to keep page state through > navigation, I keep pages references created, avoiding creation of a new page > instance when back on a visited page.. I don't need to write anything on > disk, the session space is enough. Same flaw. > This way, i wanted to share a data object instance between pages (as class > member), for modification. But due to the Page Serialization the object > identity is broken. That just means your data object serialization is broken. Sidenote: you can use HttpSessionStore (instead of SecondLevelCacheSessionStore) to make wicket store everything in session (but not in it's custom wicket on-disk store) --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
