[jbosstools-issues] [JBoss JIRA] (JBIDE-15497) Support/ignore Errai custom @Inject's

Thu Oct 3 12:05:02 EDT 2013

    [ https://issues.jboss.org/browse/JBIDE-15497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12809220#comment-12809220 ] 

Viacheslav Kabanovich commented on JBIDE-15497:
-----------------------------------------------

Extension org.jboss.errai.cdi.server.CDIExtensionPoints (see at https://github.com/errai/errai/blob/master/errai-cdi/weld-integration) collects injections with type implementing org.jboss.errai.ioc.support.bus.client.Sender (e.g. org.jboss.errai.common.client.api.Caller<?>) and provides beans to be injected.

Errai Reference Guide (see Errai_2.4.0.Beta1_Reference_Guide.pdf) does not mention CDI, but in Chapter 3. Dependency Injection/3.1. Container Wiring states that Errai IOC implements org.jboss.errai.ioc.client.api.builtin.CallerProvider that makes RPC Caller<T> objects available for injection.

So, the question is, should we assume that weld-integration module with extension is available in an Errai project and implement it in JBoss CDI Tools, or we should not rely on it and just mock caller provider?

> Support/ignore Errai custom @Inject's
> -------------------------------------
>
>                 Key: JBIDE-15497
>                 URL: https://issues.jboss.org/browse/JBIDE-15497
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: cdi-extensions
>            Reporter: Max Rydahl Andersen
>            Assignee: Jonathan Fuerth
>         Attachments: Errai_2.4.0.Beta1_Reference_Guide.pdf
>
>
> in JBDS-2358 was found that Errai has its own set of CDI inject extensions that we warn against where we probably should ignore them.
> [~jfuerth] can you outline the specific CDI types/extensions in this jira and [~akazakov] can see if this fits into the kind of types/extensions we can safely/easily ignore/support.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira