You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by Madars Vitolins <m...@silodev.eu> on 2008/10/19 15:19:11 UTC
Students work - extending ode
Hello!
I am student, new for ode and I have planned for my student's work to
extend ode, add some new standard support.
What is current ode status for:
1) BPEL4PEOPLE
2) BPEL4CHOR
Is there is there something implemented and how hard it would be for
person to implement it?
If these are hard bit's is there anything missing in ode from:
WS Reliability
WS Reliable Messaging
WS Addressing
WS Transaction
WS Security
and how hard would be these to implement?
Thanks a lot in advance,
Madars
Re: Inline variable initialization
Posted by Matthieu Riou <ma...@gmail.com>.
On Sun, Feb 8, 2009 at 12:22 PM, Madars Vitolins <m...@silodev.eu> wrote:
> Hello!
> What is current Ode status with inline variable initialization? Does
> someone works on it or maybe it is finished? From Jira seems it is open
> and unassigned ( http://issues.apache.org/jira/browse/ODE-236 )
It's filed in Jira and in our compliance page but nobody so far has
volunteered to implement it.
>
> Can I take over it?
Sure, that'd be pretty cool :)
> And guys can you point out me what directions I
> should do research? Would it affect BPEL compiler?
It would definitely affect the compiler. You'll probably have to modify some
runtime classes too but I don't foresee anything that would break backward
compatibility. Although we'll have to keep an eye on it.
>
> I see possible way that compiler would generate extra object model
> for
> variable initialization in places where execution is performed - in
> processes or scopes. For <sequence> activities that would be extra code
> in the start of element. For other activities it would require to
> generate extra "<sequence>" to moderate variable initialization and
> other activities. What do you think? Is this right way?
>
Depends what you mean :) So I don't think we can implement this strictly as
syntax sugar (only in the compiler, without modifying any OModel (the O*
classes) or runtime classes). When a process starts, it's whole container
chain starts but there's no way to stick activities before that. So the
initialization will have to be done in the scope the variable is in and we
can't really try to have the compiler generate an assignment before.
My expectations would be that you'll have to modify OScope.Variable to add
the from-spec (reusing the ones in OAssign probably) and the compiler to set
that. Then at runtime, you'll have to alter SCOPE to set the variables when
it gets instantiated.
Hope that helps.
Cheers,
Matthieu
>
> Thanks a lot in advance,
> Madars
>
>
Inline variable initialization
Posted by Madars Vitolins <m...@silodev.eu>.
Hello!
What is current Ode status with inline variable initialization? Does
someone works on it or maybe it is finished? From Jira seems it is open
and unassigned ( http://issues.apache.org/jira/browse/ODE-236 )
Can I take over it? And guys can you point out me what directions I
should do research? Would it affect BPEL compiler?
I see possible way that compiler would generate extra object model for
variable initialization in places where execution is performed - in
processes or scopes. For <sequence> activities that would be extra code
in the start of element. For other activities it would require to
generate extra "<sequence>" to moderate variable initialization and
other activities. What do you think? Is this right way?
Thanks a lot in advance,
Madars
Re: Students work - extending ode
Posted by Madars Vitolins <m...@silodev.eu>.
Thank you guys for response!
My first step is to write course work with title "Extension
possibilities of BPMS system Apache Ode". This will be mainly research
in Ode architecture. Later once this finished and I will see that I
can manage to add some extension,
I will continue this work for final paper with title similar to "Adding
extension X to BPMS Apache Ode". I will consider improvements for
WS-BEPEL 2.0 or BPEL4People.
Will start working on this in following weeks, so you may expect some
activities here from me :)
Thanks,
Madars
Matthieu Riou wrote:
> I would also consider working on improving our WS-BPEL 2.0 support, there
> are a few interesting things that we don't do yet:
>
> http://ode.apache.org/ws-bpel-20-specification-compliance.html
>
> Things like inlined variable initialization, fromPart and toPart in invoke
> and receive or being able to send/receive classic variables (instead of
> message variables) would be pretty cool. Implementing them would give you a
> good breadth of coverage of the ODE code.
>
> Thanks,
> Matthieu
>
> On Mon, Oct 20, 2008 at 3:21 AM, Tammo van Lessen <tv...@gmail.com>wrote:
>
>
>> Madars,
>>
>> thanks for your interest in Ode and especially for your interest in
>> extending it.
>>
>> Regarding the WS-* specifications, ODE is mainly reusing the
>> functionality provided by axis2. Therefore most of the standards below
>> come with Ode out-of-the-box, however there might be some interesting
>> tasks targeting a more seamless integration with Ode (e.g. coordinating
>> transactions across WS)...
>>
>> Regarding the BPEL extensions:
>> - BPEL4People support is not yet implemented but it somehow on our
>> roadmap. Implementing it shouldn't be too hard, the most difficult part
>> is however the task manager and the integration with it (i.e. via WS-HT
>> or with Singleshot, which is rather RESTful).
>> - BPEL4Chor is a choreography model and is per definition not
>> executable. Therefore I don't see how it can be implemented in Ode.
>>
>> HTH,
>> Tammo
>>
>> Madars Vitolins wrote:
>>
>>> Hello!
>>>
>>> I am student, new for ode and I have planned for my student's work to
>>> extend ode, add some new standard support.
>>> What is current ode status for:
>>> 1) BPEL4PEOPLE
>>> 2) BPEL4CHOR
>>> Is there is there something implemented and how hard it would be for
>>> person to implement it?
>>> If these are hard bit's is there anything missing in ode from:
>>>
>>> WS Reliability
>>> WS Reliable Messaging
>>> WS Addressing
>>> WS Transaction
>>> WS Security
>>>
>>> and how hard would be these to implement?
>>>
>>> Thanks a lot in advance,
>>> Madars
>>>
>>
>>
>
>
Re: Students work - extending ode
Posted by Matthieu Riou <ma...@offthelip.org>.
I would also consider working on improving our WS-BPEL 2.0 support, there
are a few interesting things that we don't do yet:
http://ode.apache.org/ws-bpel-20-specification-compliance.html
Things like inlined variable initialization, fromPart and toPart in invoke
and receive or being able to send/receive classic variables (instead of
message variables) would be pretty cool. Implementing them would give you a
good breadth of coverage of the ODE code.
Thanks,
Matthieu
On Mon, Oct 20, 2008 at 3:21 AM, Tammo van Lessen <tv...@gmail.com>wrote:
> Madars,
>
> thanks for your interest in Ode and especially for your interest in
> extending it.
>
> Regarding the WS-* specifications, ODE is mainly reusing the
> functionality provided by axis2. Therefore most of the standards below
> come with Ode out-of-the-box, however there might be some interesting
> tasks targeting a more seamless integration with Ode (e.g. coordinating
> transactions across WS)...
>
> Regarding the BPEL extensions:
> - BPEL4People support is not yet implemented but it somehow on our
> roadmap. Implementing it shouldn't be too hard, the most difficult part
> is however the task manager and the integration with it (i.e. via WS-HT
> or with Singleshot, which is rather RESTful).
> - BPEL4Chor is a choreography model and is per definition not
> executable. Therefore I don't see how it can be implemented in Ode.
>
> HTH,
> Tammo
>
> Madars Vitolins wrote:
> > Hello!
> >
> > I am student, new for ode and I have planned for my student's work to
> > extend ode, add some new standard support.
> > What is current ode status for:
> > 1) BPEL4PEOPLE
> > 2) BPEL4CHOR
> > Is there is there something implemented and how hard it would be for
> > person to implement it?
> > If these are hard bit's is there anything missing in ode from:
> >
> > WS Reliability
> > WS Reliable Messaging
> > WS Addressing
> > WS Transaction
> > WS Security
> >
> > and how hard would be these to implement?
> >
> > Thanks a lot in advance,
> > Madars
>
>
>
Re: Students work - extending ode
Posted by Tammo van Lessen <tv...@gmail.com>.
Madars,
thanks for your interest in Ode and especially for your interest in
extending it.
Regarding the WS-* specifications, ODE is mainly reusing the
functionality provided by axis2. Therefore most of the standards below
come with Ode out-of-the-box, however there might be some interesting
tasks targeting a more seamless integration with Ode (e.g. coordinating
transactions across WS)...
Regarding the BPEL extensions:
- BPEL4People support is not yet implemented but it somehow on our
roadmap. Implementing it shouldn't be too hard, the most difficult part
is however the task manager and the integration with it (i.e. via WS-HT
or with Singleshot, which is rather RESTful).
- BPEL4Chor is a choreography model and is per definition not
executable. Therefore I don't see how it can be implemented in Ode.
HTH,
Tammo
Madars Vitolins wrote:
> Hello!
>
> I am student, new for ode and I have planned for my student's work to
> extend ode, add some new standard support.
> What is current ode status for:
> 1) BPEL4PEOPLE
> 2) BPEL4CHOR
> Is there is there something implemented and how hard it would be for
> person to implement it?
> If these are hard bit's is there anything missing in ode from:
>
> WS Reliability
> WS Reliable Messaging
> WS Addressing
> WS Transaction
> WS Security
>
> and how hard would be these to implement?
>
> Thanks a lot in advance,
> Madars