|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of marc
|fleury
|Sent: Tuesday, October 02, 2001 9:15 AM
|To: Rickard �berg; [EMAIL PROTECTED]
|Subject: RE: [JBoss-dev] JMX service architecture: next gen++
|
|
||Well, the only thing the incoming gates would have to know is to
||immediately delegate to the stack configuration MBean. After that it can
||take care of the stack config.
||
||*But this will only work if the interceptor/config interleaving is done
||as outlined in previous post*. Otherwise it will be an MBean explosion...
|
|4 hours of sleep and I need coffee but no I think that you don't have
|explosion as we now know that you can use stateless interceptor which
|enables you to have ONE instance per node as well as "at the beginning"
|mapping that the MI sees coming in, no need to go through the config
|interceptor every call.
|
|Do you agree?
|
||Which, as discussed, need to be hand-holding the MI as it travels along
||the stack.
|
|no as it comes in... (imnho)

what you describe is how the folks at OpenAdaptor are doing it... let me
know what you think of it but when I saw it I went "buark". I mean the
functional part I don't know about, but the system implementation was truly
primitive (and pompous).  One of the interceptors  was a "message
hospital"... whatever that means.  I mean what kind of "stateless" repair
can you do in a message.   Maybe a replay from a debugger standpoint but I
still don't see the need for a centralized point to do that.

marcf


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to