Hi,Glad that was the issue. Yes the next problem you're seeing also seems to be the same issue. Basically you want to make sure that any dependencies you use in your POM don't get embedded (either the jar or jar exploded .class files) in the jar you build. You can open the jar you build in winzip...
Hmm...Is there any chance you are embedding a dependency jar inside your bundle? If you have your own copy of the javax.jcr.Session class file inside your bundle the classloaders could be messed up. Sorry again just a guess.Will
Hi,Shot in the dark here - wondering what the import for the Session class you are using is in your original example. Is there any chance you've got the wrong Session specified?You should always be able to adapt a com.adobe.granite.worklfow.WorkflowSession to a javax.jcr.SessionWill
Hi,Can you explain why the built-in GOTO step for 5.6.1 did not work? As for looking at this in great detail, the best thing for you to do is log a daycare ticket so it gets prioritized properly.Thanks,Will
Hi,I think what's happening is you're encountering a limitation of the node removed capabilities of the workflow launcher. Is the path "/content/my-content-1" in your example the node you deleted, or is it a node that is a parent of the node(s) you deleted? When a complete structure is removed a wo...
There shouldn't be any restrictions for running many workflows with different payloads from a single launcher, I would expect that to always work. For instance if you upload a few images to DAM they will all run workflows to generate renditions of the image.Have you narrowed the problem down furthe...
Hi,This is happening because you have the same workflow model firing for both workflow launchers, and the workflow is still running from the "create" when the "delete" launcher is fired. We are attempting to prevent multiple workflows being launched for the same path concurrently. If you specify a...
Hi,Sorry you're having trouble.The easiest way to purge running worklfows is to use the workflow JMX bean. You can access this functionality in the felix system console. It's all explained here: http://helpx.adobe.com/cq/kb/workflow-monitor-via-jmx.html#Supported featuresHope this helps,Will
Hi Ram,If you are using the Granite Workflow Process API as described here [0] you can get a ResourceResolver directly by adapting the WorkflowSession passed into your process step to a ResourceResolver. like this:ResourceResolver resolver = workflowSession.adaptTo(ResourceResolver.class);You do no...