[
https://issues.apache.org/jira/browse/ODE-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855997#action_12855997
]
Tammo van Lessen commented on ODE-648:
--------------------------------------
Hi Dave,
the problem actually is that in BPEL 1.1 you are allowed to write <from
expression="some-expr"/> but in BPEL 2.0 the expression attribute has been
dropped and instead you're meant to write <from>some-expr</from>. If you now
copy a BPEL 1.1 from-spec into a BPEL 2.0 document (i.e. different BPEL
namespace), the compiler throws an NPE although the BPEL code looks okay at the
first glance. It would be helpful if the compiler could support the BPEL
developer to spot this mistake.
Tammo
> 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
