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

Ciaran Jessup updated ODE-192:
------------------------------

    Attachment: FixDeleteInstances.patch

This patch should resolve issues 1 & 3 but issue 2 is related to another bug 
ODE-288 as far as I can tell?   I'm a little sceptical that this fix is really 
the fix, because it was so trivial, however it works for me ? 

(OpenJPA Many-To-One relationship between the ProcessInstance + Correlator had 
a CASCADE_ALL set on it, so when the instance(s) got deleted so did the 
correlators, my reading of the code is that the correlators should not be 
deleted, so I've changed the cascade rules to CASCADE_PERSIST, which is *more* 
correct [without reading the code fully I wasn't sure whether I could remove 
the cascade rules totally]) 

I've checked the Hibernate ProcessInstanceDAO and the HProcess business object 
that uses appears not to set a cascade at all so should work ok (but I'm using 
the OpenJPA on Derby here)

> 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.2
>
>         Attachments: DeleteInstanceIssue.zip, FixDeleteInstances.patch, 
> 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.

Reply via email to