[
http://jira.jboss.com/jira/browse/JBPM-1112?page=comments#action_12415093 ]
Ronald van Kuijk commented on JBPM-1112:
----------------------------------------
although it seems an easy fix (just this one change is already in my local code), there is
more to it. There are multiple differences between the xsd in the designer part of the
source and the one in jpdl tree. There also is a refactored one in the source of the
designer, so I'm not sure what is best. Strange thing is that I already commented on
this very issue recently and these comments are nowhere to be found... hmmm...
<mail> action not allowed in <timer>
------------------------------------
Key: JBPM-1112
URL:
http://jira.jboss.com/jira/browse/JBPM-1112
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: JDK 1.5, jPDL 3.2.2
Reporter: Tong Zheng
Assigned To: Alejandro Guizar
Priority: Minor
Fix For: jBPM jPDL 3.2.3
It's mentioned in the doc that "Anywhere you are allowed to specify actions in
the process, you can specify a mail action". But mail action doesn't work inside
timer.
sample code:
<state name="resolve-issue">
<event type="node-enter">
<mail name="notification"
to="user1@localhost"
template="notification">
</mail>
</event>
<timer name="timer-reminder-1" duedate="5 seconds">
<mail name="reminder-1"
to="user1@localhost"
template="reminder">
</mail>
</timer>
<transition to="end"></transition>
</state>
Got exception while deploying the definition:
org.jbpm.jpdl.JpdlException: [[ERROR] line 20: cvc-complex-type.2.4.a: Invalid content
was found starting with element 'mail'. One of
'{"urn:jbpm.org:jpdl-3.2":action,
"urn:jbpm.org:jpdl-3.2":script}' is expected.]
at org.jbpm.jpdl.xml.JpdlXmlReader.readProcessDefinition(JpdlXmlReader.java:172)
at org.jbpm.graph.def.ProcessDefinition.parseXmlInputStream(ProcessDefinition.java:180)
at org.jbpm.graph.def.ProcessDefinition.parseXmlResource(ProcessDefinition.java:161)
at
org.albertahealth.waitlist.workflow.app.DeployProcess.deployProcessFromXml(DeployProcess.java:61)
at
com.albertahealth.waitlist.workflow.app.DeployEWProcessTest.testDeployProcessDefinition(DeployEWProcessTest.java:23)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at
org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira