ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthieu Riou (JIRA)" <j...@apache.org>
Subject [jira] Updated: (ODE-192) Delete instance call on Management API fails
Date Wed, 21 Nov 2007 16:18:44 GMT

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

Matthieu Riou updated ODE-192:
------------------------------

    Fix Version/s: 1.3

> 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
>             Fix For: 1.3
>
>         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.


Mime
View raw message