I agree with Aaron, the message without context are very frustrating.
Perhaps the way to do it is to pass a context message with the thread
something like a stack of messages that are passed along and implicitely.
This way when an exception is thrown you can retrieve it from the thread cl
(something like the BeanClassLoader of the container) and you can read all
the message and the mess that you verified.
I believe it is quite a bit of work though, it means you either pass
explicitely either you pass implicetely. Oh, now that I think about it,
isn't there a way to work on the logger, like set a logger that is really a
"in memory" stack, that you print in case you have a problem? that might be
the lighter version
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Aaron Mulder
|Sent: Tuesday, October 17, 2000 8:46 AM
|To: jBoss Developer
|Subject: [jBoss-Dev] Verifier Messages
|
|
| Well, on the user list they just hitting on one of the
|deficiencies in the current verifier mechanism - namely, that we aren't
|more specific than a message per level of the spec that was violated.
| One thing I'd definitely like to add is some context, which could
|perhaps be represented as $1 $2 parameters in the resource message or
|something. Examples of using this could be the name of the offending
|class or method. Or perhaps we could just add a colon on to the end of
|the message, followed by any context information - I guess that would be
|the easiest.
| The most painful section in my mind is indeed the "valid RMI-IIOP
|type" check, since it has to check dozens of things about each class,
|recursively to all classes that are referenced. It's very difficult to
|figure out exactly what caused the error.
| BTW - do we prevent circular references causing nasty loops here?
|
|Aaron
|
|
|
