In the spirit of nailing down criteria, I would agree with;
> ... avoid the BPEL
> engine having to write a container, a deployment model and a suite of
> 'binding components' to different SOAP stacks, WS-* policies and
> transports - together with all the runtime management.
With regard to "runt
As one of the Sybase BPEL developers, this certainly sounds reasonable to
me. Perhaps we can start a discussion around what the "bake off" criteria
will look like ( i.e. what BPEL constructs are fully/half/not supported,
what set of unit tests should be supported, etc ... ). As an example; in
looki
ort heterogeneous components written in C/C++, BPEL, PHP
and other languages
I have served in a lead roll for several Sybase projects with the most
recent being ( Sybase Workspace -
http://www.sybase.com/products/developmentintegration/workspace ).
Lance Waterman
Staff Architect
Sybase, Inc.
Englewood,
