Databases
StackOverflow2013
Postsdbo
POApache ODE - BPEL compensation handler - weird behavior (or may be I'm wrong somewhere
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POApache ODE - BPEL compensation handler - weird behavior (or may be I'm wrong somewhere
    primarykey
    data
    text
    <p>I've got this example of BPEL from this location <a href="https://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/bps/modules/samples/product/src/main/resources/bpel/2.0/SampleCompensationHandlers/FlightReservationProcess/" rel="nofollow">https://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/bps/modules/samples/product/src/main/resources/bpel/2.0/SampleCompensationHandlers/FlightReservationProcess/</a></p> <p>The example sets a given variable when executes a given scope. The last scope throws an error, so the fault triggers the relevant handler for that scope, which rethrows the fault. That way the fault handler for the process is triggered, where the compensation is made for every successfully completed scope.</p> <p>I've created a BPEL project in Eclipse and I've put the example in there, then I've started some tests. But I've found a very strange behavior:</p> <ol> <li><p>I've got correct results just few times: CarReservationActivity: 1 CarReservationCompensated: 1 HotelReservationActivity: 1 HotelReservationCompensated: 1 FlightReservatoinActivity: 1 </p></li> <li><p>In all other cases I've got incorrect results:</p> <p>A)</p> <p>CarReservationActivity: 1 CarReservationCompensated: 0 HotelReservationActivity: 1 HotelReservationCompensated: 1 FlightReservatoinActivity: 1 </p> <p>B)</p> <p>CarReservationActivity: 1 CarReservationCompensated: 1 HotelReservationActivity: 1 HotelReservationCompensated: 0 FlightReservatoinActivity: 1 </p></li> </ol> <p>And when the result is incorrect then the case A) dominates.</p> <p>I can not find out where is the problem. Everything looks fine. </p> <p>Can someone help me to solve the issue ?</p> <p>Used software : - Windows 7 Enterprise, SP1, 32bit - Apache Tomcat v.6.0.18 - Apache ODE v.1.3.5 - Eclipse Indigo v.3.7.2 SR2 - BPEL designer v.1.0.1 - Java 7 (v.1.7.0_07)</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDenis Weerasiri
    1. USNNedyalkov
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POApache ODE - BPEL compensation handler - weird behavior (or may be I'm wrong somewhere
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POApache ODE - BPEL compensation handler - weird behavior (or may be I'm wrong somewhere
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload