[
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.
Odd validation issue when importing Riftsaw samples into Eclipse
----------------------------------------------------------------
Key: JBIDE-5039
URL:
https://jira.jboss.org/jira/browse/JBIDE-5039
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Reporter: Brian Fitzpatrick
Assignee: Denny Xu
Priority: Minor
Fix For: 3.1.0.CR1
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
The Riftsaw samples, when brought into Eclipse, cause validation issues:
"The expression in
<{http://docs.oasis-open.org/wsbpel/2.0/process/executable}from> cannot be checked -
no expression validator has been registered for language
urn:oasis:names:tc:wsbpel:2.0:sublang: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