[
https://issues.apache.org/jira/browse/ODE-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856020#action_12856020
]
David Carver commented on ODE-648:
----------------------------------
Okay that gives me a little bit more to go on. So in BPEL 2.0 there is no
expression attribute...is there any validation that is done against the
corresponding BPEL grammar before it is compiled or during compilation? If so
it sounds like this could be a grammar issue that defines the BPEL spec, if no
validation is done, then we can possibly add a business rule somewhere to catch
this. But it sounds like validating the BPEL during compilation would be the
simpliest solution in general.
You can eliminate some performance issues by using a Grammar cache for any XSD
that is used to validate the BPEL before it is compiled and reuse the grammar
on subsequent items.
> 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
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
