Quick-start archetypes for "real world" apps:
* Complete responder: (event responder service + compute job implementation subprojects?
* Event responder service archetype (for adding a new responder service to an existing project)
* Compute job archetype (for adding a new job implementation to an existing project)
These would greatly reduce the pain of setting up new responder projects s by creating the required directories/files, and ensuring the relevant pom.xml files contain the correct project dependencies.
A typical responder project layout generated by these archetypes might look like:
my-responder
|-- event-responder
| |-- pom.xml
| `-- src
| `-- main
| |-- java
| | |-- foo
| | `-- MyResponderImpl.java
| |-- resources
| | `-- META-INF
| | `-- xfire
| | `-- services.xml
| `-- webapp
| `-- WEB-INF
| `-- web.xml
|-- compute
| |-- pom.xml
| `-- src
| `-- main
| |-- java
| | `-- foo
| | `-- MyJobImpl.java
| |-- mb-resources
| | `-- sample-job-resource.tgz
| | `-- sample-job-resource.tag.properties
| `-- resources
`-- pom.xml