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

["Richard Taylor (JIRA)" <ji...@apache.org>]

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

Richard Taylor commented on ODE-192:
------------------------------------

I've looked into this a bit more and from what I can tell there are three issues involved.  I am working hitting the InstanceManagement web service, and have also get the same results talking directly to the interface.

I will attach a JUnit that exercises these three problems.  It is based on the original InstanceManagment junit..

Someone please comment if they are able to either 1. delete a particular instance or 2. delete all instances and successfully execute the same process after delete instances.   

Problem 1:
InstanceManagement.delete() always returns an empty list. This can be seen in ProcessAndInstanceManagementImpl.delete().  

Problem 2:
All instances are deleted despite specifying a filter with a particular instance ID.   You can specify iid=54, piid=54, iid = 54, etc.  The instance id is properly processed by the instance filter but it is not read / handled in BPELDAOConnectionImpl.instanceQuery().  The result is that all instances are returned and hence deleted.

Problem 3:  Severe
After trying to delete a single instance (or all instances), I can no longer execute a process that worked fine just before deleting instances.   I will attach a stack trace of this aspect of the problem.






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