[
https://issues.apache.org/jira/browse/ODE-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747460#action_12747460
]
Enrico Levesque edited comment on ODE-483 at 8/25/09 8:24 AM:
--------------------------------------------------------------
Towards Adaptability Support in Collaborative Business Processes (attached PDF)
>From the abstract :
Some approaches propose solutions to support business process adaptability;
however, they do not handle adaptability in the context of multi-partner
collaborative business processes. In this paper, we propose a new approach to
support adaptability for such collaborative processes. This approach uses a
protocol, called Change Protocol for Collaboration (CPC), for managing the
changes that can have incidence on the contract.
was (Author: enricolds):
Towards Adaptability Support in Collaborative Business Processes
Some approaches propose solutions to support business process adaptability;
however, they do not handle adaptability in the context of multi-partner
collaborative business processes. In this paper, we propose a new approach to
support adaptability for such collaborative processes. This approach uses a
protocol, called Change Protocol for Collaboration (CPC), for managing the
changes that can have incidence on the contract.
> 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: 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.
