You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Tammo van Lessen (JIRA)" <ji...@apache.org> on 2009/12/02 13:32:21 UTC

[jira] Resolved: (ODE-721) JPA DAOs must ensure that property keys are unique

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

Tammo van Lessen resolved ODE-721.
----------------------------------

    Resolution: Fixed

> JPA DAOs must ensure that property keys are unique
> --------------------------------------------------
>
>                 Key: ODE-721
>                 URL: https://issues.apache.org/jira/browse/ODE-721
>             Project: ODE
>          Issue Type: Bug
>          Components: BPEL Runtime
>    Affects Versions: 2.0
>            Reporter: Tammo van Lessen
>            Assignee: Tammo van Lessen
>             Fix For: 1.3.4, 1.3.5, 2.0
>
>
> Currently, writeVariableProperty creates always new entries to the XmlDataProperty table, even if the key is identical.This break correlation in ODE 2.0 as properties are then stored even in the case of variable initialization. This typically results in an empty property value, which will not be replaced by upcoming property write operations (they will simply add new objects with the same key to the table, property reads will always return the first occurrence of the key, which represents in that case an empty value).
> Although this is not directly affecting 1.x, making sure that the key is unique doesn't harm 1.x either.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.