Re: [jira] Assigned: (AGILA-36) Support for [Discriminator] workflow pattern

[Christopher Lim <ch...@gmail.com>]

Hi Geoff,


> This all sounds very cool - is this work in progress or a road map?
This is a work in progress. You help is welcome. ;)

> Do you have some pointer with explanations of the concepts you're
> heading for?
The plan is to support the workflow patterns identified by Wil van der Aalst.
www.workflowpatterns.com/


>  Are these simply new node types, or do you see engine
> changes being required?
Definitely there will be engine changes to handle some of the still
*missing* features.


> Thanks for attending to my patches this week.  I'm working on a simple
> solution for removing "out.prinln" stuff in the webapp sample and a
> few other odds and ends.

Keep those patches coming. They are most welcome. ;)


--
Chris

Re: [jira] Assigned: (AGILA-36) Support for [Discriminator] workflow pattern

[Geoff Howard <ge...@gmail.com>]

On 11/30/05, Christopher Lim <ch...@gmail.com> wrote:
> Hi Geoff,
>
> > This all sounds very cool - is this work in progress or a road map?
> This is a work in progress. You help is welcome. ;)
>
> > Do you have some pointer with explanations of the concepts you're
> > heading for?
> The plan is to support the workflow patterns identified by Wil van der Aalst.
> www.workflowpatterns.com/

Ah, thanks for the link.  Interesting to read the academic approach to
this stuff - my experience is purely in the practical.  As I digest
this stuff I'm sure I'll be able to help with it but I'm also
interested in thinking through how practical features I'm used to map
to these patterns.  My gut is that some valuable things I've seen are
not represented.

> >  Are these simply new node types, or do you see engine
> > changes being required?
> Definitely there will be engine changes to handle some of the still
> *missing* features.

Gotcha.

> > Thanks for attending to my patches this week.  I'm working on a simple
> > solution for removing "out.prinln" stuff in the webapp sample and a
> > few other odds and ends.
>
> Keep those patches coming. They are most welcome. ;)

I have some partial work on a jsp-based task form mechanism.  Aimed at
a quick solution rather than the best (as I'm not even sure what that
is but it would probably involve dependencies).

Geoff

Re: [jira] Assigned: (AGILA-36) Support for [Discriminator] workflow pattern

[Matthieu Riou <ma...@gmail.com>]

Hi Paul,

I believe that this issue is more related to the "traditional
workflow" part of Agila (BPM) and not to Agila BPEL. Agila is still a
two-headed monster that needs to be re-united :)

Cheers,

Matthieu.

On 12/1/05, Paul R Brown <pa...@gmail.com> wrote:
>
> Hi, Chris --
>
> >> Do you have some pointer with explanations of the concepts you're
> >> heading for?
> > The plan is to support the workflow patterns identified by Wil van
> > der Aalst.
> > www.workflowpatterns.com/
>
> Support or not for the vdA workflow patterns is irrelevant to
> implementing either BPEL4WS 1.1 or WS-BPEL 2.0, although the coverage
> that BPEL4WS 1.1 provides for the vdA patterns has been studied.  (WS-
> BPEL 2.0 should provide greater coverage.)
>
> Or are these changes to the Agila portion of the engine?  I was under
> the impression that the Agila+Twister combination was migrating in
> the direction of a BPEL implementation plus a workflow component.
>
> Just my $0.02.
>
>         -- Paul
>

Re: [jira] Assigned: (AGILA-36) Support for [Discriminator] workflow pattern

[Paul R Brown <pa...@gmail.com>]

Hi, Chris --

>> Do you have some pointer with explanations of the concepts you're
>> heading for?
> The plan is to support the workflow patterns identified by Wil van  
> der Aalst.
> www.workflowpatterns.com/

Support or not for the vdA workflow patterns is irrelevant to  
implementing either BPEL4WS 1.1 or WS-BPEL 2.0, although the coverage  
that BPEL4WS 1.1 provides for the vdA patterns has been studied.  (WS- 
BPEL 2.0 should provide greater coverage.)

Or are these changes to the Agila portion of the engine?  I was under  
the impression that the Agila+Twister combination was migrating in  
the direction of a BPEL implementation plus a workflow component.

Just my $0.02.

	-- Paul