(The EJB was working for a long time until someone added a non-Serializable member variable to the returned object. Programmer error.)
I think NotSerializableException is a checked exception, but either way it's still an exception. Unchecked exception just means you don't have to declare that you throw it, and you don't have to catch it. But it's still thrown.
The question is this: is it being thrown and "eaten" somewhere without being logged? Are other people seeing it logged and my JRun configuration needs to be changed?
Thanks,
John
----- Original Message -----
From: Jeffrey Anderson
To: JRun-Talk
Sent: Thursday, December 11, 2003 11:59 AM
Subject: Re: No warning when returning non-Serializable from EJB
Uh, yeah that is what happens when you try and send Non-serialized Java
objects across a network. This not a checked exception, If I remember right
so this sounds like programmer error to me.
On 12/11/03 9:40 AM, "John D. Penrose" <[EMAIL PROTECTED]> wrote:
> If I return a non-Serializable object from an EJB, it comes back to the
> client as null, and there is no warning or error message logged.
>
> Is anyone else experiencing this? Is anyone seeing this condition logged?
> Is there a way to have JRun log this condition?
>
> I posted this to the JRun EJB forum at Macromedia.com, but there have been
> no replies in the 3.5 weeks since I posted it.
>
> Any replies, either way, are welcomed.
>
> Experienced under: JRun 4 Updater none, 1 & 2, Win2k, JDK 1.4.0, 1.4.1_02,
> 1.4.2_01
>
> Thanks,
> John
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
