Red Hat Bugzilla – Bug 996023
Designer complains about missing BPMNDI information which is not missing
Last modified: 2014-08-06 16:11:27 EDT
Created attachment 785613 [details]
Description of problem:
Designer fails to import process definition (originally created in Eclipse editor shipped with BRMS 5.3), "Could not find BPMNDI information" appears in server log, although the definition has BPMNDI elements with correct references to BPMN elements.
See the attached stacktrace and process definition.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start Business Central
2. create / open some process definition
3. import attached definition
Created attachment 785614 [details]
In your attachment BPMN2 remove
and the process will import fine. This is not a Designer issue.
(In reply to Tihomir Surdilovic from comment #2)
> In your attachment BPMN2 remove
> and the process will import fine. This is not a Designer issue.
I am not sure if targetNamespace should cause this issue. The process definition I provided can be opened in Eclipse editor just fine. I have also checked the definition with this online validation tool  and again, no problems. Even if there is a problem with target namespace, the error message "Could not find BPMNDI information" is misleading.
I'm not sure what to do here. The targetnamespace is incorrect. The message is what the eclipse bpmn2 parser gives, not something set by designer itself.
the web designer uses the eclipse bpmn2 API for validation? If so then this is a bug in the eclipse editor not in the web designer. We will change the component an reassign if need be.
Before we (myself) do so I would like to ask one last question (I don't want this issue to become a ping-pong match). Is the validation in the web designer based on the classes belonging to this project -> http://www.eclipse.org/bpmn2-modeler/ ? ... or is it the old modeler which was shipped with BRMS 5.3?
which version are you using? I tried to open the process definition in the BPMN2 Eclipse designer (nightly build from yesterday) and I see only "Expression and Language must not be blank" errors.
I think the talk should be more about how we want designer to be able to open bpmn2 files with incorrect targetnamespace definitions. I don't see this as a bug and there is a simple "fix" for it to just remove one attribute in the bpmn2.
Will look into having designer remove incorrect targetnamespace defined.
Created attachment 786927 [details]
working process definition with target namespace
I am still not sure the targetnamespace is the (only) root cause - see the last attachment, there is a process definition containing a targetnamespace with the same value and Designer imports this definition without any problem.
Anyway, I cannot accept "Could not find BPMNDI information" as appropriate error message for issue which as it seems is not connected with BPMNDI elements at all.
Tiho, not sure the targetNamespace is incorrect, if you look at the BPMN2 spec itself, there are various examples where the targetNamespace is set to something example-specific, so I believe this should be allowed. Could you elaborate why it would be incorrect?
It's unclear to me though why or how the targetNamespace would be interacting with find bpmndi information.
The Eclipse BPMN2 Modeler is also using the Eclipse BPMN2 meta-model and doesn't seem to have issues opening the file. Since the editor also sets the targetNamespace, being able to open a process with targetNamespace set would be required.
Verified on BPMS-6.0.0.ER5