|Home > Guides > Core Developers Guide > Configuration Elements > Bean Configuration|
Internally, the framework uses its own dependency injection container. The container loads key framework objects, so that any piece of the framework can be replaced, extended, or removed in a standard, consistent way. Plugins, in particular, leverage this capability to extend the framework to provide support for third-party libraries like Spring or Sitemesh.
Most applications won't need to extend the Bean Configuration.
The bean element has one required attribute,
class, which specifies the Java class to be created or manipulated. A bean can either
The first use, object injection, is generally accompanied by the
type attribute, which tells the container which interface this object implements.
The second use, value injection, is good for allowing objects not created by the container to receive framework constants. Objects using value inject must define the the
the name of the bean class
the primary Java interface this class implements
the unique name of this bean; must be unique among other beans that specify the same
the scope of the bean; must be either
whether to inject static methods or not; shouldn't be
whether the bean is optional or not