Hi Michael, > i guess i could also add a boolean abortOnException parameter... but then > the caller would be forced to think about the issue (can't default > parameters in UNO IDL), which may be unnecessary overhead if he doesn't > care anyway.
Hmm - callers which don't care about this? They will simply catch and silence your exception, too, so you will never be able to address this kind of clients. In general, I agree to Jörg here - the pattern sounds strange. If you really cannot decide in your implementation whether or not the occurred exceptions are errors or not, then a callback might be another option: Give the method call a XFoo parameter, which is called upon each error, and can decide how to handle it (bail out, ignore and continue, roll back everything and return - whatever you need). Whether or not this is too much overhead compared with your boolean parameter I do not know, though. 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]
