How has industry acceptance been for the BPEL4WS specification? |
 |
EXPERT RESPONSE FROM: Doron Sherman
|
|
|
|
| > |
QUESTION POSED ON: 31 July 2003
How has industry acceptance been for the BPEL4WS specification? Is everyone accepting it?
|
|
| > |
The BPEL specification has been originally authored by IBM, Microsoft
and BEA. The BPEL spec had been faced with lingering questions concerning its potential for industry-wide acceptance, its licensing
status (royalties) and its technical merit as compared with competing
and overlapping specifications (e.g. XPDL, BPML/WSCI, ebXML/BPSS, etc). In August 2002, BPEL has been submitted for standardization to the WSBEL TC at OASIS and subsequently has been updated to form BPEL 1.1 in March, 2003. The list of companies currently enlisted behind BPEL includes the vast majority of infrastructure platform vendors, packaged application vendors and other major ISVs, including vendors who headed support for competing standards.
BPEL is still under development by the WSBPEL TC at OASIS and will
probably continue to evolve in the foreseeable future. Customer interest in BPEL continues to pick up as evidenced from the growing pace of downloads of available BPEL engines (IBM BPWS4J and Collaxa BPEL orchestration server). BPEL will undoubtedly induce a dramatic change to the existing integration market and hence is not accepted with open arms by everyone. Reducing cost, risk and complexity of EAI & B2B implementations is good for customers but less so for traditional (read: proprietary) integration middleware vendors. BPEL, as an integral part of the Web services stack, will likely enjoy accelerated acceptance in the coming years.
|
|
|
|
|
|
|
|
Search and Browse the Expert Answer Center
Search and browse more than 25,000 question and
answer pairs from more than 250 TechTarget industry experts.
|
|
|
|
|
|
|
|
|
|
|
|
