[
https://issues.apache.org/jira/browse/ODE-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Taylor updated ODE-158:
-------------------------------
Attachment: update.patch
A patch to fix the discussed issue. Tested in the specified environment.
> Unable to deal with empty "query" element in to-spec
> ----------------------------------------------------
>
> Key: ODE-158
> URL: https://issues.apache.org/jira/browse/ODE-158
> Project: ODE
> Issue Type: Improvement
> Components: BPEL Compilation/Parsing
> Affects Versions: 1.1
> Environment: JDK 1.5.0_11
> Axis2 Distro
> WinXP x64
> Reporter: Richard Taylor
> Priority: Trivial
> Attachments: update.patch
>
>
> Note: A patch is attached for this issue.
> There is currently a common case in the Eclipse BPEL editor which inserts an
> empty "query" element in the to-spec of an "Assign" activity. Ode throws an
> IllegalStateException stating "XPath string and xpath node are both null".
> It is arguable whether this is a Eclipse BPEL issue or Ode issue. I feel
> this is an issue on the editor side, not Ode, however we needed to work
> around it until the Eclipse BPEL project stops producing empty Query
> elements.
> Fixing this removes one more hurdle for someone trying to use the Eclipse
> BPEL editor with Ode.
> To reproduce this, using the latest Eclipse BPEL editor, simply create a
> process and create an Assign activity in which a value is assigned to a
> variable or a message part, but no deeper, i.e. don't specify a query.
> Again, this is not a critical fix for Ode, it's something we needed in order
> to work with the Eclipse BPEL editor and Ode. If the Eclipse editor fixes
> this on their side, this issue will go away.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
