RE: [alf-dev] Article about BPEL

["Brian Carroll" <BCarroll@xxxxxxxxxx>]

Hi Daniel,

It is important to remember that Eclipse is not a standards body.
Eclipse prefers the notion of an "exemplar" - basically working code -
and therefore does not set a standard but rather shows how something
could be accomplished while leaving open the possibility of implementing
it another way.

A focus of ALF is on interoperability and that does require agreement
among the communicating entities, so ALF is defining a set of exemplar
vocabularies for a variety of domains involved in the application
development lifecycle.  Your phrase of "workable and viable
interface[s]" describes it quite well, but ALF does not set standards.

>From a practical perspective, we see a lot of insight and thought in the
form of input from interested vendors going into the vocabularies, and
if someone wanted to take the ALF vocabulary and ALF component
interfaces through a standards process such as OASIS or the OMG (Eclipse
IP rules permitting), then the contributions of the ALF would not be a
bad place to start.

Glad you are still participating,
Regards,
Brian


Brian Carroll
Architect, Eclipse ALF project
www.eclipse.org/alf
Serena Fellow
Serena Software
(ofc)  (503) 617-2436
(cell)  (503) 318-2017
bcarroll@xxxxxxxxxx 


-----Original Message-----
From: alf-dev-bounces@xxxxxxxxxxx [mailto:alf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Daniel Gross
Sent: Tuesday, July 11, 2006 5:32 AM
To: ALF Developer Mailing List
Subject: Re: [alf-dev] Article about BPEL

Hello Tim,

It appears to me from your respond that the actual objective of
designing ALF is to obtain a standardized set of WSDL interfaces
(structure + behavior + vocabulary), which should guide the
implementation of systems, which enact service flows amongst Enterprise
application development tools. In this sense one prime objective of the
ALF framework appears to become a ALM standard, and designing the ALF
framework means coming up with workable and viable interface standards,
that applications and execution engines can adhere to.

Can you agree to that observation?

thank you,

Daniel

p.s. BTW, I am still following the ALF project for my research ... just
more in the background ...



Tim Buss wrote:
> Thanks Mark,
>
> Here is some commentary.
>
> BPEL was chosen for ALF because a) it is a cross platform standard for
> aggregating web services, b) it addresses a lot of the common issues
> necessary to coordinate disparate web services, c) it is designable,
and
> d) there is some momentum behind it as far as the availability of
> designers and execution engines.
>
> That said, the ALF design does not require BPEL to be the
implementation
> of a Service Flow.  In fact a service flow could be implemented in any
> language that can be deployed as a web service.  The key point is to
> have a runtime definition where the interfaces are all described by
> WSDL.  This should allow ALF to be deployed in a variety of ways on a
> variety of platforms.  
>
> BPMN is a design description.  It is not a execution language.  While
it
> may be possible to design an ALF application using BPMN there would
> still be the issue of how to deploy it.
>
> Tim
>
> -----Original Message-----
> From: alf-dev-bounces@xxxxxxxxxxx [mailto:alf-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Mark Phippard
> Sent: Monday, July 10, 2006 12:36 PM
> To: ALF Developer Mailing List
> Subject: [alf-dev] Article about BPEL
>
> Saw this article today.  Not really sure how much stock to put into
it.
>
> http://www.sdtimes.com/article/story-20060701-02.html
>
> There was also an article about an Eclipse-based product that
implements
> this:
>
> http://www.sdtimes.com/article/story-20060701-19.html
> http://www.eclarus.com/products.html
>
> This post would probably be more useful if I had some analysis or
> commentary to add, but I do not.  I was mainly tossing this out there
to
> see if anyone had any concerns about BPEL as a long term technology
> choice for ALF.
>
> Mark
>
>
> _______________________________________________
> alf-dev mailing list
> alf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/alf-dev
>
> **********************************************************************
> This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. Any unauthorized review, use, disclosure or distribution is
prohibited. If you are not the intended recipient, please contact the
sender by reply e-mail and destroy all copies of the original message.
>
> _______________________________________________
> alf-dev mailing list
> alf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/alf-dev
>
>   


_______________________________________________
alf-dev mailing list
alf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/alf-dev