[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-7107) Problems when creating BPEL Correlation Set

[Robert (Bob) Brodt (JIRA)]

     [ https://jira.jboss.org/browse/JBIDE-7107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert (Bob) Brodt resolved JBIDE-7107.
---------------------------------------

    Resolution: Done


Wow, this is a big one - hope I didn't break anything :(
The fix for this is a complete rewrite of the <property> and <propertyAlias> definition dialogs in the BPEL editor. There are many enhancements and bug fixes:

* Correlation properties can now be defined as both XSD Simple Types and XSD Elements
* PropertyAlias elements now support Message Type, XSD Simple Type and XSD Element definitions
* The XPath expression editor is used to define the <query> expression, which was not available previously
* The EMF model definitions for Property and PropertyAlias were ... lacking - these only supported Message Type definitions. Also there were many glaring mistakes (typos, etc.) that were fixed.
* WSDL error reporting has been greatly improved, so that the Problem markers now include line/column information
* The dialogs themselves were simplified and hopefully are less confusing

Still to be done is to enhance the XPath expression editor (specifically the ExpressionContentAssistProcessor class) so that it supports content assist for Message and XSDElementDefinition types (currently only supports BPEL variables which are NOT visible in WSDL propertyAlias definitions)


> 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