ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enrico Levesque (JIRA)" <j...@apache.org>
Subject [jira] Updated: (ODE-483) Instance replayer
Date Tue, 01 Sep 2009 13:38:32 GMT

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

Enrico Levesque updated ODE-483:

    Attachment: bookshop-example-4.zip

I added 2 project examples, deployment zip files and the soapUI xml projects to test the processes.
 They are 2 versions of a bookshop example, the first one without correlation and the second
with correlation.  I used those to test the Replayer, one all automatize and the second requires
the response of a financial analyst.

The first one works fine with the Replayer, since there is no correlation.  The second works
if the instance stop before the exchange that comes in asynchronously from FinancialAnalyst,
but it doesn't retrieve the instance by correlation during replay if you try to replay the
whole process after completion.

For the processes to work, you need to run the mock services inside SoapUI.  I just used SoapUI
to send my messages from the interfaces provided.  Sorry I didn't take the time to setup a
test case yet.

> 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
>             Fix For: Wishlist
>         Attachments: bookshop-example-1.zip, bookshop-example-4.zip, Khriss-AdaptabilitySupport.pdf,
replayer-example.zip, replayer-proposal.diff
> 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.

View raw message