[
https://jira.jboss.org/browse/JBIDE-7107?page=com.atlassian.jira.plugin.s...
]
Robert (Bob) Brodt updated JBIDE-7107:
--------------------------------------
Workaround Description: Use the "Source" view in the WSDL editor to
create/fix up <property> and <propertyAlias> definitions
Description:
I discovered several issues during testing:
1. The WSDL property is created correctly but the PropertySelectorDialog does not detect
the message part. This leads to "missing "type" or "element"
attribute" validation error
2. The messages.properties file in the org.eclipse.bpel.validator.vprop package (used for
error message localization) is empty
3. WSDL validator does not detect duplicate definitions of <property
name="foo">
4. The message "Structure" tree widget in EditPropertyAliasDialog is only one
line high - should display more of message structure
5. The overall workflow for creating correlation sets is overly confusing! This needs to
be reworked.
6. WSDL validator is not checking <propertyAlias> elements correctly: propertyAlias
can be defined using one of three ways:
1. message type and part specifications
2. XSD type definition
3. XSD Element definition
was:
I discovered several issues during testing:
1. The WSDL property is created correctly but the PropertySelectorDialog does not detect
the message part. This leads to "missing "type" or "element"
attribute" validation error
2. The messages.properties file in the org.eclipse.bpel.validator.vprop package (used for
error message localization) is empty
3. WSDL validator does not detect duplicate definitions of <property
name="foo">
4. The message "Structure" tree widget in EditPropertyAliasDialog is only one
line high - should display more of message structure
5. The overall workflow for creating correlation sets is overly complicated! This needs to
be reworked.
Complexity: High (was: Medium)
Problems when creating BPEL Correlation Set
-------------------------------------------
Key: JBIDE-7107
URL:
https://jira.jboss.org/browse/JBIDE-7107
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel
Reporter: Robert (Bob) Brodt
Assignee: Robert (Bob) Brodt
Fix For: 3.2.0.Beta2
I discovered several issues during testing:
1. The WSDL property is created correctly but the PropertySelectorDialog does not detect
the message part. This leads to "missing "type" or "element"
attribute" validation error
2. The messages.properties file in the org.eclipse.bpel.validator.vprop package (used for
error message localization) is empty
3. WSDL validator does not detect duplicate definitions of <property
name="foo">
4. The message "Structure" tree widget in EditPropertyAliasDialog is only one
line high - should display more of message structure
5. The overall workflow for creating correlation sets is overly confusing! This needs to
be reworked.
6. WSDL validator is not checking <propertyAlias> elements correctly: propertyAlias
can be defined using one of three ways:
1. message type and part specifications
2. XSD type definition
3. XSD Element definition
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira