| Modeler / jBPM Problem [message #913039] |
Fri, 14 September 2012 12:43  |
 Andre Pietsch
Messages: 6
Registered: September 2012 |
Junior Member |
|
|
Hello,
I work with jBPM v5.3 to run BPMN 2.0 processes that have been created with the new BPMN2 Editor plugin for Eclipse (BPMN2 Editor | 0.0.1.201209101728).
Now I have a problem using global parameters in processes with that setup. The editor creates a line that looks like this
<tns:global tns:identifier="MyGlobal" tns:type="java.lang.String"/>
The jBPM KnowledgeBuilder with which I have to load the process-file to run the process gives me the following error:
ProcessLoadError: unable to parse xml : Exception class org.xml.sax.SAXParseException : <global> requires a 'identifier' attribute
When I remove the "tns:" before "identifier" and "type" (same problem here) with a text-editor, the KnowledgeBuilder has no problem with the files. The line looks like this after modification:
<tns:global identifier="MyGlobal" type="java.lang.String"/>
After that modification the BPMN2 Editor is not able to recognize the global variable so I have to change it back in order to use the editor.
This is a SERIOUS problem but I don't know who makes the mistake here. Is it the editor which generates false BPMN-XMLs or is it jBPM which interprets it the wrong way.
I also don't want to point with a finger. I only want the problem to be fixed. So is it correct to address this forum or do I have to address the jBPM guys? Or maybe both?
I hope for a fast answer because I have a project that depends on that stuff.
Kindest regards
Andre
|
|
|
|
| Re: Modeler / jBPM Problem [message #913454 is a reply to message #913051] |
Sat, 15 September 2012 13:58  |
|
Hi Andre,
Hmm, yes this is a known issue and I do have a workaround for it. Unfortunately it's a bit of hack and I've posted a question on the EMF forum here:
http://www.eclipse.org/forums/index.php/t/376638/
in hopes of getting a better solution to this problem. Ideally, the jBPM parser should be changed to allow ns prefixes on attributes that are contained in the drools model elements.
If I don't have an acceptable solution to this within the next few days, I'll have to go with the workaround. Either way, this WILL be fixed 
Bob
|
|
|
|
|
| Re: Modeler / jBPM Problem [message #915511 is a reply to message #915438] |
Mon, 17 September 2012 08:47 |
|
Hi Andre,
The "lax feature processing" option is set in the Bpmn2ModelerResourceImpl constructor as a load option like so:
getDefaultLoadOptions().put(XMLResource.OPTION_LAX_FEATURE_PROCESSING, true);
but, this is not the way to correct this problem. It looks like this is caused by a setting in the model's ExtendedMetaData as pointed out by Ed Merks in the EMF forum thread (see my earlier post). I'll have a look at this today and hopefully publish another build.
Bob
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.01705 seconds
] 
Search
Help
Register
Login
Home
