mber 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 ca
We should report it to Antlr.
Regarding exceptions it would be good if we started adding some more value
to these exceptions -
it would be so much better if I actually could get the line/column numbers
as getters on the QuerySyntaxException.
The same goes with many of our other exceptions
This is nicer.
By design an exception is Serializable. It's a contract break from
antlr. So the breaking exception list has to be manually maintained.
Steve Ebersole wrote:
A simpler solution would be to just add a writeObject() impl to
HibernateException which culls the cause if it is not se
A simpler solution would be to just add a writeObject() impl to
HibernateException which culls the cause if it is not serializable
(either to null or some "marker").
This would be all encompassing. Plus it would still allow the cause to
be known (so long as no attempt is made to serialize it).
