Hi Matthew, > OK, at the risk of sounding dumb I'm not entirely sure > how this helps. The only thing that sounds close to > me is the ReferenceInsertionEventHandler. Is your > idea to implement a referenceInsert handler and check > every insertion event to see whether the object is > null ?
I failed to notice Claude's reply, but it's stated quite clearly there. :) > Are there any other conditions that might > generate errors but not throw an exception ? You'll have to search the source for every call to RuntimeLogger#error(...) and so on for an answer to that. > I guess > what I really wanted was some way of alerting the > users to all of these "silent" errors - ie exceptions > that don't get thrown but that appear only in the log. Who are the "users"? How will the "silent" errors messages help them? These questions might lead you to another solution. ;) Best regards, -- Shinobu Kawai -- Shinobu Kawai <[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
