Well ... ok ... it was a dependency problem with dom4j. The solution was now just to demove the dom4j jars in all war files jbpm (have to proof it fully the next days) ... many thanks to marko, maciejs for the help and hints :)
Reply to this message by going to Community
Start a new discussion in jBPM at Community