'%1!s!': a request-response operation round-trip may not appear in multiple tasks unless wrapped in a synchronized or atomic scope
Rules policy "{0}" version {1} cannot be deleted from rules store since is already in production. Removing the policy from ...
s!': %2!s! %3!s! %4!s! may not compensate a %5!s! whose compensation block contains any transactional or synchronized scopes ...
s!': '%2!s!' may have already been compensated - repeated attempts to compensate the same scope will be ignored at runtime ...
s!': a direct or indirect reference to a type defined in a non-exportable module '%2!s!' is not permitted under BPEL4WS compliance ...
s!': a request-response operation round-trip may not appear in multiple tasks unless wrapped in a synchronized or atomic ...
s!': a sequential convoy which is initialized by an activate receive may not call or compensate a service with a receive ...
s!': all messages and message parts referred to in the 'in' (resp. 'out') parameters of a transform statement, must be unique ...
s!': an atomic scope may not call a service that contains a receive with a correlation filtration initialized in the calling ...
s!': An XLANG/s defined exception '%2!s!' that maps to a standard BPEL fault can not have an identifier under BPEL4WS compliance ...