topic Partially deployed BAR file? in Alfresco Archive

Partially deployed BAR file?

mgriffith — Thu, 07 Jul 2011 19:33:24 GMT

I am deploying a bar file generated with the Eclipse plug in. Using Activiti 5.5, when I upload the bar file using probe, I see this error in the tomcat log file.Jul 7, 2011 2:17:51 PM org.activiti.engine.impl.bpmn.deployer.BpmnDeployer deployINFO: Processing resource TestSpringConfig.bpmn20.xmlJul

Re: Partially deployed BAR file?

ronald_van_kuij — Fri, 08 Jul 2011 08:00:38 GMT

I do not see any error…

Re: Partially deployed BAR file?

mgriffith — Fri, 08 Jul 2011 14:36:30 GMT

The thing that concerns me is:


INFO: XMLSchema currently not supported as typeLanguage
INFO: XPath currently not supported as expressionLanguage

When starting the process from the explorer, no exception is thrown in the tomcat logs, and no exception is presented through explorer, however the task is not fired off. I know this from System.out.println() statements in the method that is called from the Service task expression.

As an experiment, I created a simple 1 task project that simply consisted of a user task assigned to candidate group "management" and deployed it. During the deployment, I see the same warnings/info regarding XMLSchema and XMLPath. However this process works as expected. When fired off in explorer, it starts and I can see the process running in probe.

Why would my original process not fire the task and not throw any exception? I am stumped. Any/all replies appreciated.

Re: Partially deployed BAR file?

mgriffith — Fri, 08 Jul 2011 22:24:30 GMT

Issue resolved. Somehow I removed the $ from the expression used for my JavaService task. How this did not throw an exception, but quietly failed – causing my chase myself in circles for 3 days is disturbing.

Thanks for all who read my post, and for the reply.

MG

Re: Partially deployed BAR file?

jbarrez — Mon, 11 Jul 2011 09:45:25 GMT

The warnings

INFO: XMLSchema currently not supported as typeLanguage
INFO: XPath currently not supported as expressionLanguage

are always there, basically because this is the default XSD setting … Since we do not support the default according to the spec (ie we use java expressions), the parsers logs this warning if you don't override the settings at the top of the XML file. Nothing to worry about, all works perfect without changing them 🙂