[
https://issues.jboss.org/browse/JBIDE-8045?page=com.atlassian.jira.plugin...
]
Robert (Bob) Brodt commented on JBIDE-8045:
-------------------------------------------
Yep, this had a couple of problems...
According to the BPEL spec, the data thrown with a fault can be a WSDL message type or a
XML Schema element. I'm thinking the faultElement attribute of the <catch>
should probably be an XML type (a XSDTypeDefinition java object) even though the BPEL EMF
model has this defined as an XML element (a XSDElementDeclaration). This is going to
require a model change.
Unable to select fault variable data type in faultHandler.
----------------------------------------------------------
Key: JBIDE-8045
URL:
https://issues.jboss.org/browse/JBIDE-8045
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel
Affects Versions: 3.2.0.Beta2, 3.2.0.CR1
Environment: JBoss tools Build: 3.2_trunk.2010-12-16_04-27-01-H504
Reporter: Marek Baluch
Assignee: Robert (Bob) Brodt
Attachments: fault_handler.zip
User is not able to select the data type for a user defined fault when defining a
faultHandler catch branch. It's possible to attempt to select the data type using the
browse button but the chosen type is not noticed by the UI. The message structure is
missing too.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira