You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Richard Taylor (JIRA)" <ji...@apache.org> on 2007/10/30 18:37:50 UTC

[jira] Updated: (ODE-192) Delete instance call on Management API fails

     [ https://issues.apache.org/jira/browse/ODE-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Taylor updated ODE-192:
-------------------------------

    Attachment: DeleteInstanceIssue.zip

A Junit and associated process files to illustrate the issue(s).  This JUnit was run from the Axis2 module.

> 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
>
>
> 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.