> -----Original Message----- > From: Jung , Dr. Christoph [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, February 21, 2001 6:39 AM > To: 'JBoss-Dev' > Subject: AW: [jBoss-Dev] Exception and classloader issues - what about > mar shalling of exceptions??? > > > Hi, > > -----Ursprüngliche Nachricht----- > >Von: Castro, David [mailto:[EMAIL PROTECTED]] > >Gesendet: Mittwoch, 21. Februar 2001 05:02 > >An: ''JBoss-Dev' ' > >Betreff: RE: [jBoss-Dev] Exception and classloader issues - > what about > >mar shalling of exceptions??? > > >Actually, I wonder if there is another bug here. I dont > think we ever > >marshall exceptions that are thrown by an ejb method in > same-VM operation. > >This is a bug I think. When running non optimized, we > serialize parameters > >and return values, but not exceptions, which is what leads > to the bug we > are > >seeing here. > > really, is the code for out-of-VM invocation and > same-VM-but-different-classloader invocation > indeed so different? I was expecting there a MarshalledObject > indirection, > too ... hence my > earlier mail. It is the same code. there is explicit marshalling of arguments and return values. There is no explicit marshalling of exceptions. However, when not running in the same VM, I believe that RMI will marshall the exceptions for us. > > >Once the patch lands, we wont see this error any more, > but... It still > >bothers me that we would not marshall exceptions. With non-optimized > >operation we basically guarantee that everything will be > passed by value > not > >reference, and I think exceptions should not be any > exception to this. > >(heh.. no pun intended :) > > I´m quite sure that exceptions should be serialized quite as > usual return > values. +1 > > Best, > CGJ > --------------------------------------------------------------------- This message (including any attachments) contains confidential, proprietary or privileged information intended for a specific purpose and individual(s), and is protected by law. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. Any unauthorized disclosure, copying or distribution of any part of this message, or the taking of any unauthorized action based on it, is strictly prohibited.
