This sounds wrong to me. Can you please file a JIRA for this issue? It would help if you could provide a class with a @Service method that reproduces this issue.
We will investigate!
So after a few debug runs, it turned out the second callback (the one coming from the ServiceProcessor) was instantiated due to
the autodiscover property I had set on my servlet context.
If set, the processor creates the callback and adds it to the DeliveryPlan on the bus.
Hope I got it right..
So, how is this property used to have a consistent errai setup?
This behavior is reproduced with any @Service annotated class.
1 of 1 people found this helpful
Yes, that's exactly the issue. If you're using Errai CDI you don't need the autodiscovery init param. It's only needed for plain bus applications. This default changed on the road to 2.0.* Final:
All clear now.Thanks for the helpful answers.