[
https://issues.apache.org/jira/browse/ODE-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538868
]
Richard Taylor commented on ODE-192:
------------------------------------
Also wanted to add that I tested this under Tomcat 5.5.20 as well, with the
same results. And this is using the current 1.1 branch.
> Delete instance call on Management API fails
> --------------------------------------------
>
> Key: ODE-192
> URL: https://issues.apache.org/jira/browse/ODE-192
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Environment: Axis2 Distro
> Jetty 6.1.1
> WinXP 64
> JDK 1.5.0_10
> Reporter: Richard Taylor
> Attachments: DeleteInstanceIssue.zip, stacktrace.txt
>
>
> When trying to delete a single instance via the PMAPI it appears that all
> instances are deleted and Ode is left in an unstable state. I am using the
> JPA persistence which I'm assuming is the default.
> The problem appears to be in BPELDAOConnectionImpl.java in the
> instanceQuery() method. If I debug down to this method, the "criteria"
> parameter has been properly built with my filter (i.e. iid=54) but it is not
> properly utilized in the query. There is a TODO note to "finish the
> implementation"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
