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
o attempt is made to serialize it).
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Emmanuel Bernard
Sent: Thursday, September 08, 2005 9:05 AM
To: Hibernate development
Subject: [Hibernate] QuerySyntaxException not always serializable
To be more specific,
el Bernard
Sent: Thursday, September 08, 2005 9:05 AM
To: Hibernate development
Subject: [Hibernate] QuerySyntaxException not always serializable
To be more specific,
RecognitionException the cause exception may be not Serializable (eg
antlr.NoViableAltException (AST and Token are not serializable)
Th
rialize it).
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Emmanuel Bernard
Sent: Thursday, September 08, 2005 9:05 AM
To: Hibernate development
Subject: [Hibernate] QuerySyntaxException not always serializable
To be more specific,
RecognitionException
To be more specific,
RecognitionException the cause exception may be not Serializable (eg
antlr.NoViableAltException (AST and Token are not serializable)
Thus JBoss or any remote capable system clashes on remote calls.
Is it OK if we do not propagate the cause exception?
ie
public QuerySyntaxEx
