[JBoss JIRA] (CDI-622) External post-configuration of a bean
by Antoine Sabot-Durand (JIRA)
[ https://issues.jboss.org/browse/CDI-622?page=com.atlassian.jira.plugin.sy... ]
Antoine Sabot-Durand updated CDI-622:
-------------------------------------
Fix Version/s: 2.1 (Discussion)
> External post-configuration of a bean
> -------------------------------------
>
> Key: CDI-622
> URL: https://issues.jboss.org/browse/CDI-622
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Reporter: John Ament
> Fix For: 2.1 (Discussion)
>
>
> The use case here is that a framework has provided the application developer with some bean, X. While the framework can provide internal post construction support for this bean, the application developer has some need to set additional attributes on the bean prior to the bean being injected into its final target.
> The application developer currently has no way to do this. To accomplish this feat, the framework developer must put the burden on the application developer to do both configuration and bootstrapping of this bean. This is a bit of a pain point to be honest.
> One idea I had was to introduce a {{@Configures}} annotation that could be used, similar to observers. These methods (plural) could be called (based on priority) during the post construct phase and may exist in any managed bean.
> {code}
> @Configures
> public void setupWebServer(WebServer webserver, Configuration configuration) {
> webserver.setPort(configuration.getWebServerPort());
> }
> {code}
> In this case, webserver is the bean being configured, configuration is some other bean that retains the configuration data. This should support normal qualifiers, and perhaps provide an injection point for the underlying {{InjectionTarget}}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months
[JBoss JIRA] (CDI-635) Session context activation
by Antoine Sabot-Durand (JIRA)
[ https://issues.jboss.org/browse/CDI-635?page=com.atlassian.jira.plugin.sy... ]
Antoine Sabot-Durand updated CDI-635:
-------------------------------------
Fix Version/s: 2.1 (Discussion)
(was: 2.0 .Final)
> Session context activation
> --------------------------
>
> Key: CDI-635
> URL: https://issues.jboss.org/browse/CDI-635
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Contexts
> Affects Versions: 1.2.Final
> Reporter: John Ament
> Fix For: 2.1 (Discussion)
>
>
> This is split from discussions around CDI-30. It was agreed that session context management and request context management are two different things. CDI-30 is now targeted to just managing request contexts, this ticket is to manage session contexts.
> When considering this ticket, think of the following:
> - How to associate a context with multiple threads
> - How to look up a session context
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months
[JBoss JIRA] (CDI-635) Session context activation
by Antoine Sabot-Durand (JIRA)
[ https://issues.jboss.org/browse/CDI-635?page=com.atlassian.jira.plugin.sy... ]
Antoine Sabot-Durand updated CDI-635:
-------------------------------------
Fix Version/s: 2.0 .Final
> Session context activation
> --------------------------
>
> Key: CDI-635
> URL: https://issues.jboss.org/browse/CDI-635
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Contexts
> Affects Versions: 1.2.Final
> Reporter: John Ament
> Fix For: 2.1 (Discussion)
>
>
> This is split from discussions around CDI-30. It was agreed that session context management and request context management are two different things. CDI-30 is now targeted to just managing request contexts, this ticket is to manage session contexts.
> When considering this ticket, think of the following:
> - How to associate a context with multiple threads
> - How to look up a session context
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months
[JBoss JIRA] (CDI-9) Interceptors are not applied to custom bean types
by Antoine Sabot-Durand (JIRA)
[ https://issues.jboss.org/browse/CDI-9?page=com.atlassian.jira.plugin.syst... ]
Antoine Sabot-Durand resolved CDI-9.
------------------------------------
Resolution: Duplicate Issue
Effort on this feature will be done in CDI-580
> Interceptors are not applied to custom bean types
> -------------------------------------------------
>
> Key: CDI-9
> URL: https://issues.jboss.org/browse/CDI-9
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Interceptors, Portable Extensions
> Affects Versions: 1.0
> Reporter: Stuart Douglas
> Fix For: 2.0 (discussion)
>
>
> Beans added through the SPI do not have interceptors applied.
> Even though bean does not have a getInterceptorBindings() method, interceptors applied to stereotypes should still work.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months
[JBoss JIRA] (CDI-10) Add ability to access a bean instance from a proxy
by Antoine Sabot-Durand (JIRA)
[ https://issues.jboss.org/browse/CDI-10?page=com.atlassian.jira.plugin.sys... ]
Antoine Sabot-Durand updated CDI-10:
------------------------------------
Fix Version/s: 2.1 (Discussion)
(was: 2.0 (discussion))
> Add ability to access a bean instance from a proxy
> --------------------------------------------------
>
> Key: CDI-10
> URL: https://issues.jboss.org/browse/CDI-10
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Beans
> Affects Versions: 1.0
> Reporter: Stuart Douglas
> Labels: F2F2016
> Fix For: 2.1 (Discussion)
>
>
> There are occasions when it would be useful to access a bean instance directly from a proxy. This could be achieved by making all proxies assignable to an interface (say BeanProxy) that provides a getBeanInstance() method.
> Client code that needs access to the actual instance can check if the object is assignable to the BeanProxy interface and then call getBeanInstance() to get the actual instance if required.
> This is something that is probably more useful to extension writers than the end user, but there have already been a few requests on the weld forum about this so it is probably worth considering.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months
[JBoss JIRA] (CDI-19) Ordering execution on Extensions
by Antoine Sabot-Durand (JIRA)
[ https://issues.jboss.org/browse/CDI-19?page=com.atlassian.jira.plugin.sys... ]
Antoine Sabot-Durand resolved CDI-19.
-------------------------------------
Resolution: Rejected
CDI-4 brings a solution for this ordering
> Ordering execution on Extensions
> --------------------------------
>
> Key: CDI-19
> URL: https://issues.jboss.org/browse/CDI-19
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Portable Extensions
> Affects Versions: 1.0
> Reporter: Robson Ximenes
> Priority: Minor
> Fix For: 2.0 (discussion)
>
>
> I believe the cdi portable extension could have the load order of extensions the same as it is registered;
> It is possible that one extension expect some previous preparation of beans from another extension
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months