I have the same problem arno.
If i call the addClasspathResource(xxx) the workflow will get a correct deployment. If i use the method addInputStream() the deployment is not correct.
After deployment with addClasspathResource() the following log will be generated:
26.04.2011 22:23:50 org.activiti.engine.impl.bpmn.deployer.BpmnDeployer deploy
INFO: Processing resource main/resources/diagrams/SimpleSendReceive@pA.bpmn20.xml
26.04.2011 22:23:51 org.activiti.engine.impl.bpmn.parser.BpmnParse parseDefinitionsAttributes
INFO: XMLSchema currently not supported as typeLanguage
26.04.2011 22:23:51 org.activiti.engine.impl.bpmn.parser.BpmnParse parseDefinitionsAttributes
INFO: XPath currently not supported as expressionLanguage
After deployment with addInputStream() the following log will be generated:
26.04.2011 22:13:21 org.activiti.engine.impl.bpmn.deployer.BpmnDeployer deploy
INFO: Processing resource SimpleSendReceive@pB
In ActivitProbe i see also a difference:
With addClasspathResource() i see my deployment at the DEPLOYMENT tab and my added process.
But with addInputStream() i see only my deployment and no process.
The funny thing is, that the method addClasspathResource calls implicit the method addInputStream(). The only difference is the name of the resource.
solution:
The name of the resource must end with "bpmn20.xml". When i import a resource than points to an existing file it have always the ending .bpmn20.xml, but i must also use the notation if i will use addString or addInputStream from the deployment service.
@frederikheremans: Inside the deployment service must be an hard query to the resource name. Why?