Beans within Spring may be accessed from other Oddjob components using the notation ${id-of-this/name-of-bean}.
Oddjob beans are made available via a parent BeanFactory so can be accessed by reference.
Oddjobs beans and there properties can also be accessed using the ${id.property} notation within Spring configuration files.
| classLoader | Passed to Spring for its DefaultResourceLoader. |
| files | Spring XML configuration files. |
| name | The name of the job. |
| resources | Spring XML configuration classpath resources. |
| Example 1 | See the examples in the examples/config directory. |
| Configured By | ELEMENT |
| Access | READ_WRITE |
| Required | No. |
Passed to Spring for its DefaultResourceLoader. If not supplies the class loader for this class will be used which will be the Oddball class loader when installed as an Oddball.
| Configured By | ELEMENT |
| Access | READ_WRITE |
| Required | Not if resources are supplied. |
Spring XML configuration files.
| Configured By | ATTRIBUTE |
| Access | READ_WRITE |
| Required | No. |
The name of the job. Can be any text.
| Configured By | ELEMENT |
| Access | READ_WRITE |
| Required | Not if files are supplied. |
Spring XML configuration classpath resources.
See the examples in the examples/config directory. To run
the examples copy the examples/classes directory to it's parent
directory so that Oddjob recognises them as part of the Oddball.