Using Osworkflow in your Application

Using OSWorkfl ow in your Application
The Object Registry—BeanFactory
S pring uses the concept of a BeanFactory. This BeanFactory is an application-wide
registry and manages components. It is responsible for instantiating and injecting
objects and their dependencies.
OSWorkfl ow can be integrated with the Spring container as a bean in the
BeanFactory. In this way you can declaratively manage OSWorkfl ow dependencies.
In addition to this native integration, OSWorkfl ow can utilize Spring-managed beans
for Functions, Conditions, and other components.
The current Spring version supported by OSWorkfl ow is 2.0. To download the
Spring Framework, go to www.springframework.org. To include Spring in your
application, just put the spring.jar fi le in the classpath. For each module you
use, several different third-party libraries are required; in this example, only the
hibernate3.jar fi le is needed.
The Spring BeanFactory's beans are usually defi ned in an XML fi le called
BeanFactory.xml. This fi le must reside in the classpath and contains each bean and
its dependencies declarations. A sample BeanFactory.xml fi le is as follows:
1000
The beans tag is the root element of the XML; all bean tags must be nested inside it.
The bean tag declares a new bean inside the BeanFactory. The id attribute serves as a
unique identifi er inside the BeanFactory and the class attribute marks the Java class
to be instantiated by refl ection.
The property tag tells Spring to set a value to the JavaBean name attribute, in this
case salary. The value element nested inside the property tag defi nes the value
to be set, in this case 1000. This value can be converted automatically by Spring,
depending on the type of the target JavaBean property.
Note that the Spring convention is to create only once instance per
component—a singleton model. To override this behavior, you must set
the bean element's singleton attribute to false.
[ 86 ]