Following the UNIX philosophy for automated task processing in java enable us to re-use the maximum code from other projects. As a reminder a pipe in unix starts with an invoking component (which produces a stream) and then chain as much other components that interact on the stream that are needed. The modification of each component will be passed to the next component in the chain.

For example the following command in a unix box will lance a subversion command to check for the status on the local svn checkout (svn st). The next command will filter the files that are not under svn control (grep ?). The next command will modify the stream to create a command to add this files to the repository (awk ...). The last step will cause the invocation of the command by sending it to the shell (sh).

svn st | grep ? | awk '{print "svn add "$2}' | sh

In droids your are piping/processing your tasks with small specialist components that combined are resolving your task.

Once you have created the droids.jar, place it in your classpath and you are ready to develope your own components and robots. Droids is completly Spring driven, if you never have seen Spring at all you need to check out their documentation otherwise you will be lost.

We will develope a SIMPLE robot that will crawl a web page and send the data to an Apache Solr server (poor man's approach of Apache Nutch crawling) and will call it "indexer".

The resulting classes can be found in $DROIDS_HOME/src/example/java and can be compiled with ant droids.compile-example. This target compiles the examples, creates a jar and copy the resulting jar into the lib directory.

In your principal spring configuration you need to import the default spring configuration files from droids. A typical file would look something like the following.

Then we need to configure the org.apache.droids.helper.factories.DroidFactory bean to add our new droid.

Then we need to configure our indexer.

The variables within @@ are replaced while building the jar with ant. The actual value is defiened either by the properties in your build.properties or the default.properties.

Now we need to wrap up our droid in defining our new handler.