On 21 Jul 2004, at 10:43, Werner Guttmann wrote:
I've seen the bug report already, but I won#t be able to get anything done
before August 4th, 2004 due to ... holidays ... ;-).

Go away. Have a good holiday. Don't think about it. I'm perfectly capable of hacking up the codebase to fix blockers that I run into until you get home. :)
Yes, please. But the real exercise is to integrate this with Castor's
exception classes, i.e. find the right Castor-specific Exception class that
needs to be modified (and here people like Keith will want to have an
opinion, I assume .. ;-)), deal with JDK 1.2 compliancy, etc.

My class is already fully JDK 1.2 compliant. If someone points out which class they'd like to use as the 'root' class to gain the hasCause() functionality, and I assume that's CastorException, I'll modify it and post a patch to the aforementioned bug.


Somehow I think that the RMI stuff would not be required ...

You never know. Nothing like asking. :) If not, then there's a ready-to-go and rather well tested class I can cut my code out of and offer to the castor project.


Note, however, that I don't currently try to check for the existence of super's getCause() in any of this - it's a complete 1.2 implementation. (Thinking about it, of course, we run on 1.4, and there's not a whole lot of reason for us to use it - on the other hand, there's also not a whole lot of reason to change something that Just Works. :)



----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev

Reply via email to