nfig- ResourceFactory ure() interface. The SCA provides significant latitude concerning how an instance of a Resource can be created. In its broadest LifeCycle context, a Resource can be created at any time by any The LifeCycle parent class provides the Resource with entity before it is needed by the framework for a specific the ability to both initialize and release the component waveform. This wide latitude is not necessarily useful from the framework through the initialize() and relea- because sometimes the framework needs the Resource to seObject() interfaces. Initialization in this context is not be explicitly created. In the cases in which it needs to be the same as configuring the different values associated explicitly created, the specifications provide the frame- with the component. In this context, initialization sets the work with the ResourceFactory class. The Resource- component to a known state. For example, in the case of Factory class has only three methods, createResource(), a filter, the initialization call may allocate the memory releaseResource(), and shutdown(). The createResource necessary to perform the underlying convolution and it function creates an instance of the desired Resource may populate the filter polynomial from the component's and returns the reference to the caller, and the release set of properties. The releaseObject performs the com- Resource function calls the releaseObject interface in the plimentary function to initialize. In the case of a filter, it specified Resource. The shutdown function terminates would deallocate the memory needed by the component. the ResourceFactory. How the ResourceFactory goes One aspect of releaseObject that is common to all com- about actually creating the Resource is not described in the ponents is that it unbinds the component from CORBA. specifications. Instead, the specifications provide the de- In short, releaseObject performs all the work necessary to veloper with the latitude necessary to create the Resource prepare the object for destr