Why does RepositoryService work this way?

gregorypierce — Mon, 12 Dec 2011 21:50:00 GMT

I was looking at a way to tie the loading of a process to a ResourcePatternResolver and ran across a strange issue and I'm hoping someone can explain why it is this wayRespositoryService.createDeployment().addInputStream() takes two arguments (neither of which are documented BTW), a resourceName and

Re: Why does RepositoryService work this way?

trademak — Tue, 13 Dec 2011 08:17:10 GMT

Hi,

You just are not using the right query after you deployed the inputstream.
You can provide any name you like as the resourceName, but only resource names ending with ".bpmn20.xml" are parsed as process definitions.
So when you would use:

Deployment deployment = repositoryService.createDeploymentQuery().deploymentId(deploymentId).singleResult();

You would get your deployment back.

Best regards,

topic Re: Why does RepositoryService work this way? in Alfresco Archive

Why does RepositoryService work this way?

Re: Why does RepositoryService work this way?