Index Changes

BPEL Service Engine Developer

Coding samples, styles, standards to be used in BPEL-SE

Using XmlResourceProvider to get DocumentBuilder and Transformer

Coding samples, styles, standards to be used across components

Document.createElement() or Document.createElementNS()


Benchmark setup and testing on Agnes, Ackerman, miles setup



In general we can say that it is the same message that comes to IMAs that are of same type, this example is to suggest that isin't the case. Engine can't blindly route the message to first receive or second receive. What if the message has optional data structure to it, and cSet1 and cSet3 depended on mutually exclusive optional message information. For instance if the message came with the optional data that is used to construct "cSet3", but engine routes it to the first receive, we may not be able to construct "cSet1" and that will result in a standard fault to be thrown. Had the engine somehow figured this and abstained from routing it to first receive, we would not have an issue. I am documenting it here so that we attempt to solve this when we implement multiple receives.

Issues & TODOs



BPEL blue prints

BPEL interaction Scenarios with other components.

Engine States

Engine States Enlargement

Engine Thread Model

Engine Thread Model Enlargement

Engine Message Exchange Flow

Message Exchange Flow Enlargement

Asynchronous Thread Modeling

  • TODO - need to post this image

Back to Subprojects

Access Count: 51
StatCounter Access Count :

JSPWiki v2.4.100
« Home Index Changes Prefs
This page (revision-18) was last changed on 24-Mar-09 11:33 AM, -0700 by rjacobus