Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1062222

Summary: NPE if sequenceFlow has no targetRef
Product: [Retired] JBoss BPMS Platform 6 Reporter: Kris Verlaenen <kverlaen>
Component: jBPM CoreAssignee: Maciej Swiderski <mswiders>
Status: CLOSED WORKSFORME QA Contact: Marek Baluch <mbaluch>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0.0CC: rrajasek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-07 15:24:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
validation messages none

Description Kris Verlaenen 2014-02-06 13:23:27 UTC 
Provide more user-friendly error message (including for example process id) in case sequence flow does not have (correct) source or target refs.  

Stack trace from customer that seems to occur during incremental compilation in guvnor here it seems:

09:32:00,749 ERROR [org.drools.core.xml.ExtensibleXmlParser] (http-vm-4679-6a6e.nam.nsroot.net/10.49.238.189:8080-4) (null: 8, 149): cvc-complex-type.4: Attribute 'targetRef' must appear on element 'bpmn2:sequenceFlow'.

09:32:00,757 ERROR [stderr] (http-vm-4679-6a6e.nam.nsroot.net/10.49.238.189:8080-4) java.lang.NullPointerException

09:32:00,758 ERROR [stderr] (http-vm-4679-6a6e.nam.nsroot.net/10.49.238.189:8080-4)     at org.jbpm.bpmn2.xml.ProcessHandler.findNodeByIdOrUniqueIdInMetadata(ProcessHandler.java:276)
Comment 1 Maciej Swiderski 2014-02-07 15:18:48 UTC 
Created attachment 860555 [details]
validation messages
Comment 2 Maciej Swiderski 2014-02-07 15:24:51 UTC 
I cannot reproduce it this issues, as can be seen on the attached screenshot messages are properly displayed in problems panel and there are no exceptions in logs. Closing it as cannot reproduce.