Errai service scaffolding

[bogdand]

Hi,

I have a question on how the services in errai are bound on the bus.

It appears that there are 2 MessageCallback(s) associated with service (annotated with @Service).

One of them is from the org.jboss.errai.bus.server.service.ServiceProcessor.createRPCScaffolding(), and the other is from org.jboss.errai.cdi.server.CDIExtensionPoints.createRPCScaffolding().

As a result, the service is called twice for a message received on the bus.

Am I wrong, or do I have a wrong errai setup?

I'm using Errai 2.3.0.Final with JBOSS 7.1.1.Final

Don't know if there already is an open discussion on this, sorry if redundant

Thanks

[jfuerth]

Hi Bogdan,

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!

-Jonathan

[bogdand]

Hi,

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.

Thanks

Bogdan

[csa]

Hi Bogdan,

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:

https://docs.jboss.org/author/display/ERRAI/Upgrading+from+2.0.Beta+to+2.0.*.Final

Cheers,

Christian

[bogdand]

All clear now.Thanks for the helpful answers.

Cheers,

Bogdan