No, as when this happens its deep in some serialization stack that has no ability to know that an improperly written subclass can be safely replaced with an instance of its baseclass. This is definitely a bug in antlr and a common mistake since the contract for Serializable was is often introduced several baseclasses away.
The hibernate base exception has this semantic knowledge, but its just a hack around the broken antlr exception. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Max Rydahl Andersen > Sent: Thursday, September 08, 2005 9:10 AM > To: Emmanuel Bernard; Hibernate development > Subject: Re: [Hibernate] QuerySyntaxException not always serializable > > > We should report it to Antlr. > ... > Regarding culling of these exceptions isn't that something > appserers actually can do in their serialization code ? > (maybe keeping it Hibernate would be better to be more portable) > > > /max > ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
