You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "David Carver (JIRA)" <ji...@apache.org> on 2010/04/08 04:48:36 UTC
[jira] Commented: (ODE-648) Compiler should throw a meaningful
error if / expression is empty
[ https://issues.apache.org/jira/browse/ODE-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854776#action_12854776 ]
David Carver commented on ODE-648:
----------------------------------
Would you like to see the serialized node output with the error message.
So something like:
throw new IllegalStateException("XPath string and xpath node are both null: " + source.toString());
Currently it is just:
throw new IllegalStateException("XPath string and xpath node are both null. ");
> 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.
-
You can reply to this email to add a comment to the issue online.