[
https://issues.apache.org/jira/browse/ODE-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861550#action_12861550
]
David Carver commented on ODE-648:
----------------------------------
I've managed to get XML Validation against a Grammar Pool working. I've run
the BPEL Compiler test suite that is supposed to be good, and it caught some
Validation constraint issues with a couple of the files.
Tammo is this type of information more what you were looking for:
[Error] AsyncProcess2.bpel:135:78: cvc-enumeration-valid: Value 'out' is not
facet-valid with respect to enumeration '[request, response,
request-response]'. It must be a value from the enumeration.
[Error] AsyncProcess2.bpel:135:78: cvc-attribute.3: The value 'out' of
attribute 'pattern' on element 'correlation' is not valid with respect to its
type, 'null'.
[Error] AsyncProcess2.bpel:146:78: cvc-enumeration-valid: Value 'out' is not
facet-valid with respect to enumeration '[request, response,
request-response]'. It must be a value from the enumeration.
[Error] AsyncProcess2.bpel:146:78: cvc-attribute.3: The value 'out' of
attribute 'pattern' on element 'correlation' is not valid with respect to its
type, 'null'.
[Error] comp1-2.0.bpel:55:36: cvc-complex-type.3.2.2: Attribute 'scope' is not
allowed to appear in element 'compensate'.
[Error] If1-2.0.bpel:55:12: cvc-complex-type.2.4.a: Invalid content was found
starting with element 'assign'. One of
'{"http://schemas.xmlsoap.org/ws/2004/03/business-process/":then}' is expected.
[Error] If2-2.0.bpel:55:17: cvc-complex-type.2.4.a: Invalid content was found
starting with element 'assign'. One of
'{"http://schemas.xmlsoap.org/ws/2004/03/business-process/":then}' is expected.
[Error] If3-2.0.bpel:55:12: cvc-complex-type.2.4.a: Invalid content was found
starting with element 'assign'. One of
'{"http://schemas.xmlsoap.org/ws/2004/03/business-process/":then}' is expected.
Dave
> Compiler should throw a meaningful error if <from>/<to> expression is empty
> ---------------------------------------------------------------------------
>
> Key: ODE-648
> URL: https://issues.apache.org/jira/browse/ODE-648
> Project: ODE
> Issue Type: Bug
> Components: BPEL Compilation/Parsing
> Affects Versions: 1.2, 1.3.2, 1.3.3, 2.0
> Reporter: Tammo van Lessen
> Assignee: Tammo van Lessen
> Fix For: 1.3.5, 2.0-beta3
>
>
> If the expression is empty, the only error message is from the expression
> compiler and is quite confusing:
> java.lang.IllegalStateException: XPath string and xpath node are both null
> at
> org.apache.ode.bpel.elang.xpath20.compiler.XPath20ExpressionCompilerImpl.doJaxpCompile.
> Fixing this issue will also help if a copy and paste engineer added a BPEL
> 1.1 <from expression="someexp"/> to a BPEL 2.0 process ;)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
