ASAP/WfXML - Status / Premature completion of requesting subflow activity

Hi,

What is the status of ASAP / WfXML implementation?

I am trying to use it between two Shark engines ( 1.1-2) and  the 
requesting engine "completes" the requesting subflow activity when 
processing the initial Observer state change from the "target" of  
open.notrunning to open.running for the "target" activity.

This seems to be an error as the requesting subflow is completed 
prematurely and subsequence Observer messages from the target cause errors.

Note that the "synchronous" setting on the subflow activity appears to 
being honoured as the activity is completing after the receipt of the 
state change message

I have reproduced the problem with shark-retailer and shark-manufacturer..

David Bernard

--
You receive this message as a subscriber of the [email protected] mailing list.
To unsubscribe: mailto:[email protected]
For general help: mailto:[email protected]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws