the default set of module definitions is now fixed in code.

this should be configurable. an option could be to put this config info in the jbpm.parsers.xml like this

<process-archive-deployer>
<process-definition-factory>
<module-definition class="org.jbpm...ContextDefinition" />
<module-definition class="org.jbpm...LoggingDefinition" />
<module-definition class="org.jbpm...SecurityDefinition" />
<module-definition class="org.jbpm...TaskMgmtDefinition" />
</process-definition-factory>
<parsers>
<parser class="org.jbpm.jpdl.par.JpdlArchiveParser" />
<parser class="org.jbpm.jpdl.par.FileArchiveParser" />
</parsers>
</process-archive-deployer>

this would need a small refactoring of the processdefinition creation. now the process definition is created in the JpdlArchiveParser. it would be cleaner if the ProcessDefinition was created by the process archive deployer and that it would be passed to all process archive parsers as a parameter. this will require a small refactoring of the JpdlXmlReader cause that class always creates a new ProcessDefinition... or maybe the JpdlXmlReader should be using the process-definition-factory configuration information... to be continued...

maybe we should reevaluate the responsabilities of the ProcessArchive and the ProcessArchiveDeployer. maybe the application of the process archive parsers should move from the ProcessArchive to ProcessArchiveDeployer...