The Oddball directory structure is:
You can have either a
myball
classes
com
acme
MyStuff.class
lib
someutil.jar
lib or classes or both,
but you must have something.
Additionally there can be as many META-INF/arooa.xml resources
on that confirm to the arooa:descriptor format for defining
element mappings and conversions.
| files | The Oddball directory or directories. |
| oddballs | Other factories for creating Oddballs. |
| Example 1 | Loading two Oddballs. |
| Configured By | ELEMENT |
| Access | READ_WRITE |
| Required | Yes. |
The Oddball directory or directories.
| Configured By | ELEMENT |
| Access | READ_WRITE |
| Required | No. Defaults to a directory loading factory. |
Other factories for creating Oddballs. See oddball.
In the future, it is hoped to support loading Oddballs from archives. Following the
existing java naming convention for archives they will probably be
called .oar files.
Loading two Oddballs.
<oddjob id="this">
<job>
<oddjob file="${this.args[0]}/test/launch/oddballs-launch.xml">
<descriptorFactory>
<oddballs>
<files>
<files>
<list>
<file file="${this.args[0]}/test/oddballs/apple"/>
<file file="${this.args[0]}/test/oddballs/orange"/>
</list>
</files>
</files>
</oddballs>
</descriptorFactory>
</oddjob>
</job>
</oddjob>
This is equivalent to launching Oddjob with the oddball path option
set as in:
java -jar run-oddjob.jar \
-op test/oddballs/apple:test/oddballs/orange \
-f test/launch/oddballs-launch.xml
Or if the test/oddballs directory only contains these two
directories, then using the oddball directory option:
java -jar run-oddjob.jar \
-ob test/oddballs \
-f test/launch/oddballs-launch.xml
If the apple and orange directories were
copied to Oddjob's Oddballs directory they would be loaded by default.