When we generate a BPEL skeleton from a WSDL definition, each service operation results in an "onMessage", mark-up, associated with the name space "http://docs.oasis-open.org/wsbpel/2.0/process/executable". If we try to add a child to this element, we got an error from EasyBPEL.
[BPEL engine restriction] Sorry, but a child activity inside the onMessage for operation null is unrecognized or not supported by Bpel Engine for the moment or is null
If I change the prefix to associate it with "http://docs.oasis-open.org/wsbpel/2.0/process/abstract", then it is validated.
I have not tested with the runtime.
My point is: if onMessage does not work, do not generate such mark-ups. Generating something that is not validated is useless.
The generation should be updated in consequence.
Bug
New
