On Tuesday 28 September 2004 20:33, Mansour Raad wrote: > What I'm trying to get to is *not* having to explicitly invoked from the > component the etherization and creation steps.
Of course not. > In my case, I would like to > make my component have a transient lifestyle, and do the following on an > error in the implementation of the JMS MessageListener or the onException. > _serviceManager.release(this); Hmmm... This would require that we implement the Availability contract that has been my attempt over the last 6-8 months, since you would otherwise be unable to signal that the component is killed/recreated. I would suggest the following; Create a Singleton lifestyle component that is a thin wrapper, for everyone else to be dependent on. Create a Transient lifestyle component that the singleton manages, i.e. it looks it up, keep the reference until there is a problem, then it releases it in its (the singleton's) service manager, and looks up a new transient instance. Understand what I mean? This will provide you with a managed solution, yet have a singleton reference to the JMS service. > PS: what is "traditional SFT" ? System Fault Tolerance is how to design and create systems where any part can fail without degradation of functionality and, depending on level, with maintained performance. That includes hardware, software, networked resources, external equipment and so on as a combination of pieces that works together. High-grade SFT often stipulates how many random pieces that can break during a specified time interval, during which the failing component will be fixed by service personell, and statistical analysis of what the cost vs risk of a given SFT strategy. Cheers Niclas -- +------//-------------------+ / http://www.bali.ac / / http://niclas.hedhman.org / +------//-------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
