Star tables do not occur in end-user queries. They are introduced by the optimizer to help matching queries to materializations, and used only during the planning process.
When a materialization is defined, if it involves a join, it is converted to a query on top of a star table. Queries that are candidates to map onto the materialization are mapped onto the same star table.
Startable
provides an object with a {@link #start()} methodwhich gets called when the Mule instance gets started. This is mostly used by infrastructure components, but can also be implemented by service objects. This lifecycle interface should always be implemented with its opposite lifecycle interface {@link org.mule.api.lifecycle.Stoppable}.
@see org.mule.api.lifecycle.Stoppable
An interface which is implemented by components that can be started and stopped. The {@link Startable#start()}must be called at the begin of the component lifecycle. It can be called again only after a call to {@link Startable#stop()}. The {@link Startable#stop()} method must be called at the end of the component lifecycle,and can further be called after every {@link Startable#start()}. If a component implements the {@link Disposable}interface as well, {@link Startable#stop()} should be called before {@link Disposable#dispose()}.
For more advanced and pluggable lifecycle support, see the functionality offered by the nanocontainer-proxytoys subproject.
@author Nicolas Filotto @version $Id$
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|