You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Matthieu Riou (JIRA)" <ji...@apache.org> on 2007/01/10 18:36:27 UTC
[jira] Work started: (ODE-26) Add Version Support
[ https://issues.apache.org/jira/browse/ODE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on ODE-26 started by Matthieu Riou.
> Add Version Support
> -------------------
>
> Key: ODE-26
> URL: https://issues.apache.org/jira/browse/ODE-26
> Project: Apache Ode
> Issue Type: Task
> Components: BPEL Runtime
> Affects Versions: Incubator
> Reporter: Lance Waterman
> Assigned To: Matthieu Riou
> Fix For: Incubator
>
>
> Add version support into the BPEL runtime.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Work started: (ODE-26) Add Version Support
Posted by Lance Waterman <la...@gmail.com>.
Thanks for the scope clarification and I think this sounds like a reasonable
first step.
Lance
On 1/10/07, Matthieu Riou <ma...@gmail.com> wrote:
>
> Actually what I would like to do isn't a full versioning implementation
> but
> more a way to not have all your instances removed when you redeploy the
> same
> process definition several times. Otherwise the engine is only usable for
> development and even integration testing can become hard to achieve.
>
> So my idea was to make this pretty local to the process store by just
> altering slightly the pid given to the engine on deployment and to have
> the
> most simple possible policy for version increments. Here is how it would
> work:
>
> 1. You deploy a process for the first time, the store saves it and sets
> pid = new QName(processBpelNameNS, processBpelName + ".1")
> So the version is 1.
>
> 2. You deploy the same process again. The store detects it by just
> checking
> if it already have a deployed process with the same process name. If it
> does
> it just deploys a version with a different pid by incrementing the version
> number:
> pid = new QName(processBpelNameNS, processBpelName + ".2")
> Other processes with the same bpel process name are retired.
>
> By doing so the engine will handle both as being different processes
> anyway,
> it's not really a versioning policy in that respect.
>
> So that's a very preliminary implementation, mostly at the store level,
> just
> to allow redeployment without removing all instances of all previous
> executions. The default mode will remain the one we have now, it's just to
> let people use the engine not only and strictly in development. As you
> mentioned, after the release, we would re-discuss all that anyway to see
> which versioning policy would make more sense and see how we implement it.
>
> Matthieu
>
> On 1/10/07, Lance Waterman <la...@gmail.com> wrote:
> >
> > Matthieu,
> >
> > I didn't think we were adding this in until after the first release?
> >
> > Lance
> >
> > On 1/10/07, Matthieu Riou (JIRA) <ji...@apache.org> wrote:
> > >
> > >
> > > [
> > >
> >
> https://issues.apache.org/jira/browse/ODE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> > ]
> > >
> > > Work on ODE-26 started by Matthieu Riou.
> > >
> > > > Add Version Support
> > > > -------------------
> > > >
> > > > Key: ODE-26
> > > > URL: https://issues.apache.org/jira/browse/ODE-26
> > > > Project: Apache Ode
> > > > Issue Type: Task
> > > > Components: BPEL Runtime
> > > > Affects Versions: Incubator
> > > > Reporter: Lance Waterman
> > > > Assigned To: Matthieu Riou
> > > > Fix For: Incubator
> > > >
> > > >
> > > > Add version support into the BPEL runtime.
> > >
> > > --
> > > This message is automatically generated by JIRA.
> > > -
> > > If you think it was sent incorrectly contact one of the
> administrators:
> > > https://issues.apache.org/jira/secure/Administrators.jspa
> > > -
> > > For more information on JIRA, see:
> > http://www.atlassian.com/software/jira
> > >
> > >
> > >
> >
> >
>
>
Re: [jira] Work started: (ODE-26) Add Version Support
Posted by Matthieu Riou <ma...@gmail.com>.
Actually what I would like to do isn't a full versioning implementation but
more a way to not have all your instances removed when you redeploy the same
process definition several times. Otherwise the engine is only usable for
development and even integration testing can become hard to achieve.
So my idea was to make this pretty local to the process store by just
altering slightly the pid given to the engine on deployment and to have the
most simple possible policy for version increments. Here is how it would
work:
1. You deploy a process for the first time, the store saves it and sets
pid = new QName(processBpelNameNS, processBpelName + ".1")
So the version is 1.
2. You deploy the same process again. The store detects it by just checking
if it already have a deployed process with the same process name. If it does
it just deploys a version with a different pid by incrementing the version
number:
pid = new QName(processBpelNameNS, processBpelName + ".2")
Other processes with the same bpel process name are retired.
By doing so the engine will handle both as being different processes anyway,
it's not really a versioning policy in that respect.
So that's a very preliminary implementation, mostly at the store level, just
to allow redeployment without removing all instances of all previous
executions. The default mode will remain the one we have now, it's just to
let people use the engine not only and strictly in development. As you
mentioned, after the release, we would re-discuss all that anyway to see
which versioning policy would make more sense and see how we implement it.
Matthieu
On 1/10/07, Lance Waterman <la...@gmail.com> wrote:
>
> Matthieu,
>
> I didn't think we were adding this in until after the first release?
>
> Lance
>
> On 1/10/07, Matthieu Riou (JIRA) <ji...@apache.org> wrote:
> >
> >
> > [
> >
> https://issues.apache.org/jira/browse/ODE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
> >
> > Work on ODE-26 started by Matthieu Riou.
> >
> > > Add Version Support
> > > -------------------
> > >
> > > Key: ODE-26
> > > URL: https://issues.apache.org/jira/browse/ODE-26
> > > Project: Apache Ode
> > > Issue Type: Task
> > > Components: BPEL Runtime
> > > Affects Versions: Incubator
> > > Reporter: Lance Waterman
> > > Assigned To: Matthieu Riou
> > > Fix For: Incubator
> > >
> > >
> > > Add version support into the BPEL runtime.
> >
> > --
> > This message is automatically generated by JIRA.
> > -
> > If you think it was sent incorrectly contact one of the administrators:
> > https://issues.apache.org/jira/secure/Administrators.jspa
> > -
> > For more information on JIRA, see:
> http://www.atlassian.com/software/jira
> >
> >
> >
>
>
Re: [jira] Work started: (ODE-26) Add Version Support
Posted by Lance Waterman <la...@gmail.com>.
Matthieu,
I didn't think we were adding this in until after the first release?
Lance
On 1/10/07, Matthieu Riou (JIRA) <ji...@apache.org> wrote:
>
>
> [
> https://issues.apache.org/jira/browse/ODE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Work on ODE-26 started by Matthieu Riou.
>
> > Add Version Support
> > -------------------
> >
> > Key: ODE-26
> > URL: https://issues.apache.org/jira/browse/ODE-26
> > Project: Apache Ode
> > Issue Type: Task
> > Components: BPEL Runtime
> > Affects Versions: Incubator
> > Reporter: Lance Waterman
> > Assigned To: Matthieu Riou
> > Fix For: Incubator
> >
> >
> > Add version support into the BPEL runtime.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
> https://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>