[cdi-dev] [JBoss JIRA] (CDI-613) Container should be able to receive information about the context in which it was bootstraped

[Martin Kouba (JIRA)]

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

Martin Kouba commented on CDI-613:
----------------------------------

I believe it is a more general problem (not only Java EE). A portable extension is instantiated by the CDI container and as such has no "reference" to any related technology/framework resources during bootstrap (i.e. during container lifecycle event delivery). So I think a kind of _"bootstrap configuration/metadata"_ is missing. The truth is this would probably require a standardized Bootstrap API. And this would be tricky, especially in the context of Java EE.

> Container should be able to receive information about the context in which it was bootstraped
> ---------------------------------------------------------------------------------------------
>
>                 Key: CDI-613
>                 URL: https://issues.jboss.org/browse/CDI-613
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>          Components: Java EE integration
>            Reporter: Antoine Sabot-Durand
>             Fix For: 2.0 (proposed)
>
>
> Today it's impossible to know what is the outside context of the CDI container (i.e what is the application or EE module it belongs to).
> This is problematic for other spec like JPA who needs to retrieve their information (persistence units) from a portable extension.
> This would help solving issues like WFLY-2387 in a portable way.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)