Hi,
> That's true. If you need a concurrent execution of extension activities
> you'd need to implement the abstract class for async extensions, fork
> your own thread and call the ExtensionContext.complete method once your
> processing has finished. In this case the run method can finish before
Hi Daniel,
(I'm moving this from user@ to dev@)
> today I found out, that the workaround with setting to
> "false" works only for invokes of webservices, not extension
> activities.
That's true. If you need a concurrent execution of extension activities
you'd need to implement the abstract clas
