|Re: BPEL Compilation [message #576164 is a reply to message #576093]
||Tue, 18 April 2006 09:40
| Antony Miguel
Registered: July 2009
I'll keep this short but a bit of history is useful here.
B2J started out as the Choreography component in the Test and
Performance Tools Platform (TPTP) as a runtime to link together various
aspects of the project and to serve as generic test behaviour engine.
These behaviours had certain requirements on the runtime and, in
particular, load testing behaviours had important requirements regarding
scalability and performance.
As such, the runtime grew up not as an interpreter of BPEL XML documents
but with a compilation step that converted the BPEL to Java programs.
These pure Java programs could run much faster than a Java program
interpreting a BPEL document.
In addition, the Java programs ran using a framework which could either
be implemented locally or as distributed nodes (e.g. for large load
tests involving multiple machines).
This division of the running Java program and the server/runtime
framework implementation it used was picked up on as a worthwhile
framework to base runtimes or implementations with other requirements
around and B2J was born.
The plan now is to solicit requirements from other vendors who wish to
make use of the B2J code and create or integrate their own runtimes so
we can evolve the framework to suit.
Keanu, Paik wrote:
> The main feature of B2J is BPEL to java translation and compilation,
> which is not common for other bpel engine.
> What is the main reason, or main advantage for compiling bpel into java?
Powered by FUDForum
. Page generated in 0.02527 seconds