true
+ /// only if all components that apply are currently running.
+ /// true
+ /// only if all components that apply are currently running.
+ /// - /// Typically invoked during factory configuration, but can also be - /// used for runtime registration of singletons. Therefore, a factory - /// implementation should synchronize singleton access; it will have - /// to do this anyway if it supports lazy initialization of singletons. - ///
- ///
- /// Only checks already instantiated singletons; does not return
- ///
- /// The main purpose of this method is to check manually registered
- /// singletons (
- /// To check whether an object factory contains an object definition
- /// with a given name, use the
- ///
- /// Use the
- ///
AfterPropertiesSet method).
+ /// The given instance will not receive any destruction callbacks
+ /// (like IDisposable's Dispose method) either.
+ /// null if none foundtrue
+ /// for singleton bean definitions which have not been instantiated yet.
+ /// ContainsObjectDefinition. Calling both
+ /// ContainsObjectDefinition and ContainsSingleton answers
+ /// whether a specific object factory contains an own object with the given name.
+ /// ContainsObject for general checks whether the
+ /// factory knows about an object with a given name (whether manually registered singleton
+ /// instance or created by bean definition), also checking ancestor factories.
+ /// null).null).null)
+ ///
+ public NmsResourceHolder(IConnectionFactory connectionFactory)
+ {
+ this.connectionFactory = connectionFactory;
+ }
+
+ /// OnMessage methodsOnMessage methodstrue; the default 'running'
+ /// state is purely determined by false if such a restriction prevents listeners from running.
+ /// Subclasses need to implement this method for their specific - /// listener management process.
+ + ///Subclasses need to implement this method for their specific - /// listener management process.
+ ///