Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 60553 invoked from network); 5 Jan 2009 13:43:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Jan 2009 13:43:42 -0000 Received: (qmail 21250 invoked by uid 500); 5 Jan 2009 13:43:42 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 20333 invoked by uid 500); 5 Jan 2009 13:43:39 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 20317 invoked by uid 99); 5 Jan 2009 13:43:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Jan 2009 05:43:39 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Jan 2009 13:43:39 +0000 Received: by brutus.apache.org (Postfix, from userid 33) id 91138234C48B; Mon, 5 Jan 2009 05:43:18 -0800 (PST) From: bugzilla@apache.org To: dev@tomcat.apache.org Subject: DO NOT REPLY [Bug 46464] Serialisation issues in catalina X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: newchanged X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Tomcat 6 X-Bugzilla-Component: Catalina X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: sebb@apache.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: dev@tomcat.apache.org X-Bugzilla-Target-Milestone: default X-Bugzilla-Changed-Fields: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Message-Id: <20090105134318.91138234C48B@brutus.apache.org> Date: Mon, 5 Jan 2009 05:43:18 -0800 (PST) X-Virus-Checked: Checked by ClamAV on apache.org https://issues.apache.org/bugzilla/show_bug.cgi?id=46464 --- Comment #2 from Sebb 2009-01-05 05:43:16 PST --- I've also just discovered that Java appears not to call the private readObject(ObjectInput) or writeObject(ObjectOutput) methods in DeltaSession. It seems Java only looks for "private writeObject(ObjectOutputStream)" not "private writeObject(ObjectOutput)", likewise for readObject(ObjectInput). So at present, both StandardSession nor DeltaSession will use the default Java serialisation - i.e. the readObject/writeObject methods that are defined will not be used to override the standard mechanism. It is not clear whether it is intentional or accidental that the default Java serialisation mechanism is not being overridden. If it is intended that the default mechanism is used, then I would suggest that the readObject/writeObject methods are renamed. Or at the very least, the Javadoc should make it very clear that the method names are misleading. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org