Mailing-List: contact dev-help@ode.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ode.apache.org
Message-ID: <656927468.176841265800708083.JavaMail.jira@brutus.apache.org>
Date: Wed, 10 Feb 2010 11:18:28 +0000 (UTC)
From: "Rafal Rusin (JIRA)" <jira@apache.org>
To: dev@ode.apache.org
Subject: [jira] Resolved: (ODE-483) Instance replayer
In-Reply-To: <1260158116.1231794600510.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Rafal Rusin resolved ODE-483.
-----------------------------

       Resolution: Fixed
    Fix Version/s:     (was: Wishlist)
                   1.3.4

> Instance replayer
> -----------------
>
>                 Key: ODE-483
>                 URL: https://issues.apache.org/jira/browse/ODE-483
>             Project: ODE
>          Issue Type: New Feature
>    Affects Versions: Wishlist
>            Reporter: Rafal Rusin
>            Assignee: Rafal Rusin
>             Fix For: 1.3.4
>
>         Attachments: bookshop-example-1.zip, bookshop-example-4.zip, Khriss-AdaptabilitySupport.pdf, replayer-example.zip, replayer-proposal.diff, replayer-test2-soapui-project.xml
>
>
> Imagine situation when client has deployed a process with a lot of active, long running instances. Then he finds there's a bug in this process and a simple bugfix is needed. But with current versioning rules, new version is only used when new instances are created. So there's no simple way for doing such bufixes (which are usually possible with eg. java application using database connection). It is a blocking argument for deploying ODE Bpel solution instead of a regular java application.
> I think the best way to deal with such situations is to add serialize/deserialize to/from xml operations for process instances in management API. Also pause/resume ODE operations would be useful. 
> Then, a bugfix procedure would look like this;
> -pause ode
> -serialize instances
> -deploy newer version
> -deserialize instances and fix manually any import errors 
> -resume ODE
> It would also be a benefit of being able to do migration from older to newer ODE and between Hibernate/JPA DAOs, which I saw already in some bug reports. 
> What do you think about it?
> Regards

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