[
https://issues.jboss.org/browse/JBIDE-8048?page=com.atlassian.jira.plugin...
]
Robert (Bob) Brodt updated JBIDE-8048:
--------------------------------------
There is a fundamental problem with the way "implicit" variables are represented
in the editor's EMF model. The EMF model objects for the <forEach>,
<onEvent> and <catch> BPEL elements all contain a "Variable" object.
The "Variable" model object represents an explicitly defined BPEL variable and
the model assumes that this object corresponds to a BPEL <variable> element in the
XML document. However, the "Variable" objects in the <forEach>,
<onEvent> and <catch> elements are represented as XML attributes and not as
<variable> elements. Therefore, whenever some attribute of these implicit variables
is changed, the model can't find the corresponding XML element and regards this as an
error (which is logged and ignored).
The correct way to fix this is to define a new EMF object (e.g.
"ImplicitVariable") which understands that it is represented as an XML
attribute, rather than an element, but I'm hesitant to do this at this time because it
introduces a lot of additional complexity. I have an acceptable workaround for this (which
substitutes the parent XML element in place of the missing <variable> element) and
am still testing this fix, but so far it looks promising.
OnEvent Handler throws NPE when selecting PartnerLink and Operation
in Properties tab
-------------------------------------------------------------------------------------
Key: JBIDE-8048
URL:
https://issues.jboss.org/browse/JBIDE-8048
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel
Affects Versions: 3.2.0.Beta2, 3.2.0.CR1
Reporter: Robert (Bob) Brodt
Assignee: Robert (Bob) Brodt
Priority: Critical
Fix For: 3.2.0.CR1
Like the title says, the OnEvent handler throws an NPE when an Operation is selected from
either the combobox or the Quick Pick widgets in the Details property tab.
Also, the Details includes two "Variable:" widgets - only one should be
displayed.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira