Hi alls! I think that in the current service implementation the only "way" to change a mbean attribute is a "restart" of the service.
Why does not implementing the java bean event model (property change & co) in jmx... after all there is in the spec. I think that if I set a attribute to a mbean, the attribute must modify the behaviour of the service, if a dependent mbean need the feedback must listen to the attribute change event. If the service can not change the attribute it must send a exception. If a dependent service can not handle a attribute change must be send a request to a the ServiceController to be restarted or deactivated. Claudio > -----Original Message----- > From: Sacha Labourey [SMTP:[EMAIL PROTECTED]] > Sent: Friday, January 24, 2003 7:14 PM > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-dev] [ jboss-Change Notes-672538 ] Master > Configuration Service > > Yes, I agree, it is up to the service to say if it knows how to implement > a > restart, otherwise the service controller will simply execute the restart > commands as a start/stop pair against the non-compliant service. > > > -----Message d'origine----- > > De : [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]De la part de > > Scott M Stark > > Envoyé : vendredi, 24 janvier 2003 19:04 > > À : [EMAIL PROTECTED] > > Objet : Re: [JBoss-dev] [ jboss-Change Notes-672538 ] Master > > Configuration Service > > > > > > Logically a restart vs stop/start can make sense, but practically > > it may not depending > > on the service. The problem is a service has to be omniscient to > > understand how > > to transition old state to the new state and this can be nearly > > impossible if the service > > externalizes much of its functionality through customizable > > socket factories, etc. > > > > xxxxxxxxxxxxxxxxxxxxxxxx > > Scott Stark > > Chief Technology Officer > > JBoss Group, LLC > > xxxxxxxxxxxxxxxxxxxxxxxx > > > > ----- Original Message ----- > > From: "Sacha Labourey" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Friday, January 24, 2003 9:37 AM > > Subject: RE: [JBoss-dev] [ jboss-Change Notes-672538 ] Master > > Configuration Service > > > > > > > > > Well, then you cannot update the list of the JMX interceptors > > as you cycle > > > your service, right? Otherwise, how do you cycle the "ServiceContext" > > > interceptor? At one point, independently of where do you manage > > that, I am > > > pretty sure that you need a part of the system that thinks "I > > do think in a > > > specific way because it is a restart and not a definitive > > stop". You don't > > > think so? > > > > > > Cheers, > > > > > > > > > > > > sachay > > > > > > > > ------------------------------------------------------- > > This SF.NET email is sponsored by: > > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > > http://www.vasoftware.com > > _______________________________________________ > > Jboss-development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
