You should never get a ServerException that wraps a RemoteException
unless the application code did it. My major rewrite to the exception
code assures this. Actually, we should not need any of this unwrapping,
but it looks like the Sun RMI code is broken. When we get rid of the
Sun RMI
AFAIK the sun rmi code wraps all RemoteExceptions into ServerExceptions: it
certainly does so for the TransactionRolledbackException. Is there any
chance that the jboss server code or an application would throw a
ServerException? If not I think this unwrapping should unwrap any
RemoteException
A ServerException is a just RemoteException, so anything can throw one.
This is just another reason to get rid of the lame Sun RMI
implementation (JBoss 4.0). In the meantime, I agree that we (you) will
need to make patched to the unwrapping code.
-dain
David Jencks wrote:
AFAIK the sun
This is just another reason to get rid of the lame Sun RMI
implementation (JBoss 4.0). In the meantime, I agree that we
we are not there yet,
(you) will
need to make patched to the unwrapping code.
let's do the workaround
marc f
This is just another reason to get rid of the lame Sun RMI
implementation (JBoss 4.0). In the meantime, I agree that we
we are not there yet,
You guys talking about replacing RMI for the remote EJB invocations?? Isn't
that what we have the JBoss.IIOP and JBoss.Net projects??
Regards,
these are invokers yes, but they are not RMI re-implementations.
marc f
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On
Behalf Of Hiram Chirino
Sent: Wednesday, September 11, 2002 8:33 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] Unwrapping
