[ https://jira.jboss.org/jira/browse/JBIDE-5039?page=com.atlassian.jira.plu... ] Denny Xu commented on JBIDE-5039: --------------------------------- Basically, current bpel validator only support to parse xpath1.0 and doesn't recognise any new feature of xpath2.0 , if the user use any new expression format that xpath1.0 doesn't have, the bpel validator will consider it as an error. The issue described above is warning that the bpel validator can not validate "urn:oasis:names:tc:wsbpel:2.0:sublang:xpath2.0." expression language, I removed this warning message so that the bpel validator will treat "urn:oasis:names:tc:wsbpel:2.0:sublang:xpath2.0." like "urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0.", and will create a new issue for adding new validator for parse xpath2.0 format expression. -- 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