[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-4732) The summary of BPEL validator issue

[Denny Xu (JIRA)]

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

Denny Xu resolved JBIDE-4732.
-----------------------------

    Resolution: Done


> The summary of BPEL validator issue
> -----------------------------------
>
>                 Key: JBIDE-4732
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4732
>             Project: JBoss Tools
>          Issue Type: Bug
>          Components: bpm
>    Affects Versions: 3.1.0.M3
>            Reporter: Denny Xu
>            Assignee: Denny Xu
>             Fix For: 3.1.0.M3
>
>         Attachments: bpel-validator.patch
>
>
> so far, the bpel validator still has the following issues not get fixed:
> 1. before validate bpel resource, the validator is unable to delete all bpel problem markers which created by bpel validator, it only delete the related markers in .bpel files, but it should not be the right logic, when validating a bpel file, it validates all the bpel file referenced other types of files, such .wsdl and .xsd file,
> so that if validate the same file *n* times, the same bpel problem markers will have *n* records in the problem view.
> 2. after validate bpel resource, only the markers of .bpel file can be located to the accurate line number position when double click relevant markers.
> 3. when checking xpath function, the return type of those functions are *Integer*, such as the function concat(string str1, string str2) , then it generates a type 
> un-compatible warning message.
> 4. it seems the validator doesn't support to validate xpath2.0

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira