Hi Stephan, > Of course, this is somewhat fragile, in that your test code needs to > parse Message to find out the caught RuntimeException has the specific > meaning (hoping that there is no other code somewhere that throws > RuntimeExceptions with matching Message but different meaning). > > However, that is not different from your NetBeans example: There, you > have the same fragility checking whether a caught > java.lang.UnsupportedExceptionOperation has your "Not yet implemented" > meaning or is for example thrown by calling add on an immutable > java.util.Collection instance.
But couldn't we do better in UNO, by clearly (!) separating between "unsupported" and "not implemented"? Ciao Frank -- - Frank Schönheit, Software Engineer [email protected] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
