nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

<activiti:expression> vs <expression> validation errors

ronald_van_kuij

I just updated my branche to be in sync with trunk and get lots of errors on the <expression> element as a child of <activiti:field>. I did not get these before (afaik)

I checked svn and the xsd is not changed recently and neither are the testcases where this fails. No I also run the '5.1' designer (0.6?) in the same eclipse so I'm not sure which is ok. According to the xsd there should be prefixes…

Anybody?

Find more posts tagged with

Comments

jbarrez

Ronald, How can I enable the error messages?
Those errors surely must have been there before, because nothing has moved in that area in the last weeks;

I'm assuming you are talking about these XML snippets:

<br> <activiti:field name="html"><br>          <expression><br>
Both with an without prefix, the processes work.
I checked the parser, and it seems to be a bit too liberal about the namespace.

I believe that the prefix must be there, so I updated the code accordingly.
Is this also what you think is correct?

jbarrez

The change is checked in. The documentation was already showing the activiti: prefix.

ronald_van_kuij

Yes that is it. No idea if validation in my Eclipse installation was disabled before. Don't think so, but not sure. I just run Helios with the latest JBoss tools and activiti designer. There is explicit validation by right-clicking on the file in the explorer/navigator part.

There are more elements with validation errors… but some might be related to me having an 'older' xsd from the designer

Description Resource Path Location Type
cvc-complex-type.2.1: Element 'activiti:formProperty' must have no character or element information item [children], because the type's content type is empty. FormsTest.testFormPropertyDetails.bpmn20.xml /activiti-engine/src/test/resources/org/activiti/engine/test/forms line 26 XML Problem
cvc-complex-type.2.1: Element 'activiti:formProperty' must have no character or element information item [children], because the type's content type is empty. FormsTest.testFormPropertyDetails.bpmn20.xml /activiti-engine/target/test-classes/org/activiti/engine/test/forms line 26 XML Problem
cvc-complex-type.2.4.b: The content of element 'activiti:executionListener' is not complete. One of '{"http://activiti.org/bpmn':field}' is expected. ExecutionListenersProcess.bpmn20.xml /activiti-engine/src/test/resources/org/activiti/examples/bpmn/executionlistener line 8 XML Problem
cvc-complex-type.2.4.b: The content of element 'activiti:executionListener' is not complete. One of '{"http://activiti.org/bpmn':field}' is expected. ExecutionListenersProcess.bpmn20.xml /activiti-engine/src/test/resources/org/activiti/examples/bpmn/executionlistener line 18 XML Problem
cvc-complex-type.2.4.b: The content of element 'activiti:executionListener' is not complete. One of '{"http://activiti.org/bpmn':field}' is expected. ExecutionListenersProcess.bpmn20.xml /activiti-engine/src/test/resources/org/activiti/examples/bpmn/executionlistener line 24 XML Problem
cvc-complex-type.2.4.b: The content of element 'activiti:executionListener' is not complete. One of '{"http://activiti.org/bpmn':field}' is expected. ExecutionListenersProcess.bpmn20.xml /activiti-engine/target/test-classes/org/activiti/examples/bpmn/executionlistener line 8 XML Problem
cvc-complex-type.2.4.b: The content of element 'activiti:executionListener' is not complete. One of '{"http://activiti.org/bpmn':field}' is expected. ExecutionListenersProcess.bpmn20.xml /activiti-engine/target/test-classes/org/activiti/examples/bpmn/executionlistener line 18 XML Problem
cvc-complex-type.2.4.b: The content of element 'activiti:executionListener' is not complete. One of '{"http://activiti.org/bpmn':field}' is expected. ExecutionListenersProcess.bpmn20.xml /activiti-engine/target/test-classes/org/activiti/examples/bpmn/executionlistener line 24 XML Problem
cvc-complex-type.2.4.b: The content of element 'activiti:taskListener' is not complete. One of '{"http://activiti.org/bpmn':field}' is expected. CustomTaskAssignmentTest.testAssigneeAssignment.bpmn20.xml /activiti-engine/src/test/resources/org/activiti/examples/bpmn/tasklistener line 17 XML Problem
cvc-complex-type.2.4.b: The content of element 'activiti:taskListener' is not complete. One of '{"http://activiti.org/bpmn':field}' is expected. CustomTaskAssignmentTest.testAssigneeAssignment.bpmn20.xml /activiti-engine/target/test-classes/org/activiti/examples/bpmn/tasklistener line 17 XML Problem
cvc-complex-type.2.4.b: The content of element 'activiti:taskListener' is not complete. One of '{"http://activiti.org/bpmn':field}' is expected. CustomTaskAssignmentTest.testCandidateGroupAssignment.bpmn20.xml /activiti-engine/src/test/resources/org/activiti/examples/bpmn/tasklistener line 17 XML Problem
cvc-complex-type.2.4.b: The content of element 'activiti:taskListener' is not complete. One of '{"http://activiti.org/bpmn':field}' is expected. CustomTaskAssignmentTest.testCandidateGroupAssignment.bpmn20.xml /activiti-engine/target/test-classes/org/activiti/examples/bpmn/tasklistener line 17 XML Problem
cvc-complex-type.2.4.b: The content of element 'activiti:taskListener' is not complete. One of '{"http://activiti.org/bpmn':field}' is expected. CustomTaskAssignmentTest.testCandidateUserAssignment.bpmn20.xml /activiti-engine/src/test/resources/org/activiti/examples/bpmn/tasklistener line 17 XML Problem
cvc-complex-type.2.4.b: The content of element 'activiti:taskListener' is not complete. One of '{"http://activiti.org/bpmn':field}' is expected. CustomTaskAssignmentTest.testCandidateUserAssignment.bpmn20.xml /activiti-engine/target/test-classes/org/activiti/examples/bpmn/tasklistener line 17 XML Problem
cvc-complex-type.2.4.b: The content of element 'activiti:taskListener' is not complete. One of '{"http://activiti.org/bpmn':field}' is expected. CustomTaskAssignmentTest.testOverwriteExistingAssignments.bpmn20.xml /activiti-engine/src/test/resources/org/activiti/examples/bpmn/tasklistener line 17 XML Problem
cvc-complex-type.2.4.b: The content of element 'activiti:taskListener' is not complete. One of '{"http://activiti.org/bpmn':field}' is expected. CustomTaskAssignmentTest.testOverwriteExistingAssignments.bpmn20.xml /activiti-engine/target/test-classes/org/activiti/examples/bpmn/tasklistener line 17 XML Problem
cvc-complex-type.2.4.b: The content of element 'activiti:taskListener' is not complete. One of '{"http://activiti.org/bpmn':field}' is expected. CustomTaskAssignmentTest.testOverwriteExistingAssignmentsFromVariable.bpmn20.xml /activiti-engine/src/test/resources/org/activiti/examples/bpmn/tasklistener line 17 XML Problem
cvc-complex-type.2.4.b: The content of element 'activiti:taskListener' is not complete. One of '{"http://activiti.org/bpmn':field}' is expected. CustomTaskAssignmentTest.testOverwriteExistingAssignmentsFromVariable.bpmn20.xml /activiti-engine/target/test-classes/org/activiti/examples/bpmn/tasklistener line 17 XML Problem
cvc-complex-type.2.4.b: The content of element 'activiti:taskListener' is not complete. One of '{"http://activiti.org/bpmn':field}' is expected. TaskListenerTest.bpmn20.xml /activiti-engine/src/test/resources/org/activiti/examples/bpmn/tasklistener line 17 XML Problem
cvc-complex-type.2.4.b: The content of element 'activiti:taskListener' is not complete. One of '{"http://activiti.org/bpmn':field}' is expected. TaskListenerTest.bpmn20.xml /activiti-engine/src/test/resources/org/activiti/examples/bpmn/tasklistener line 32 XML Problem
cvc-complex-type.2.4.b: The content of element 'activiti:taskListener' is not complete. One of '{"http://activiti.org/bpmn':field}' is expected. TaskListenerTest.bpmn20.xml /activiti-engine/target/test-classes/org/activiti/examples/bpmn/tasklistener line 17 XML Problem
cvc-complex-type.2.4.b: The content of element 'activiti:taskListener' is not complete. One of '{"http://activiti.org/bpmn':field}' is expected. TaskListenerTest.bpmn20.xml /activiti-engine/target/test-classes/org/activiti/examples/bpmn/tasklistener line 32 XML Problem
cvc-complex-type.2.4.d: Invalid content was found starting with element 'activiti:field'. No child element is expected at this point. ExecutionListenersFieldInjectionProcess.bpmn20.xml /activiti-engine/src/test/resources/org/activiti/examples/bpmn/executionlistener line 10 XML Problem
cvc-complex-type.2.4.d: Invalid content was found starting with element 'activiti:field'. No child element is expected at this point. ExecutionListenersFieldInjectionProcess.bpmn20.xml /activiti-engine/target/test-classes/org/activiti/examples/bpmn/executionlistener line 10 XML Problem
cvc-complex-type.2.4.d: Invalid content was found starting with element 'activiti:field'. No child element is expected at this point. TaskListenerTest.bpmn20.xml /activiti-engine/src/test/resources/org/activiti/examples/bpmn/tasklistener line 21 XML Problem
cvc-complex-type.2.4.d: Invalid content was found starting with element 'activiti:field'. No child element is expected at this point. TaskListenerTest.bpmn20.xml /activiti-engine/target/test-classes/org/activiti/examples/bpmn/tasklistener line 21 XML Problem
cvc-complex-type.3.2.2: Attribute 'datePattern' is not allowed to appear in element 'activiti:formProperty'. FormsTest.testFormPropertyDetails.bpmn20.xml /activiti-engine/src/test/resources/org/activiti/engine/test/forms line 19 XML Problem
cvc-complex-type.3.2.2: Attribute 'datePattern' is not allowed to appear in element 'activiti:formProperty'. FormsTest.testFormPropertyDetails.bpmn20.xml /activiti-engine/target/test-classes/org/activiti/engine/test/forms line 19 XML Problem
cvc-complex-type.4: Attribute 'event' must appear on element 'activiti:executionListener'. ExecutionListenersProcess.bpmn20.xml /activiti-engine/src/test/resources/org/activiti/examples/bpmn/executionlistener line 19 XML Problem
cvc-complex-type.4: Attribute 'event' must appear on element 'activiti:executionListener'. ExecutionListenersProcess.bpmn20.xml /activiti-engine/target/test-classes/org/activiti/examples/bpmn/executionlistener line 19 XML Problem
cvc-complex-type.4: Attribute 'event' must appear on element 'activiti:executionListener'. FullHistoryTest.testVariableUpdates.bpmn20.xml /activiti-engine/src/test/resources/org/activiti/standalone/history line 19 XML Problem
cvc-complex-type.4: Attribute 'event' must appear on element 'activiti:executionListener'. FullHistoryTest.testVariableUpdates.bpmn20.xml /activiti-engine/target/test-classes/org/activiti/standalone/history line 19 XML Problem

jbarrez

- The executionListener/taskListener 'field' error is indeed an error in the xsd. I changed it to minOccurs="0", since this is not needed when you you for example the 'class' attribute.

- The event attribute on an executionListener is indeed not mandatory, altough the xsd required it

Fixed it on trunk. That should already fix 3/4 of the validation errors above

mahavirj

is there an updated activiti designer plugin? R5.2 still has the old one and this error continues

ronald_van_kuij

It was not a designer issue but an xsd vs processdefinitions issue (I had the error outside the designer as well). If you still get these errors at these elements that would be strange. If you get them at other elements, than please report which ones and in which files.

Cheers,

Ronald

mahavirj

activiti-bpmn-extensions-5.0.XSD is in the designer plugin (org.activiti.designer.eclipse_0.7.0.jar). For now, I just added a user defined XML catalog entry in eclipse to take the 5.2 XSD (windows-preferences-xml catalog). I also specified a schemaLoc in my process definition. That solved it for me….Either way, updating the designer plugin with the new XSD would have helped

Thanks,

ronald_van_kuij

Can you report a jira for this on the designer? It might be that the 'fixes' in the files done by Joram only now show up because of the older xsd in the designer. So they show up with the 'reverse cause'

Ronald

mahavirj

Posted JIRA issue ACT-619

Thanks,