[JBoss JIRA] Created: (CDI-133) Further clarify the notion of a decorated type
by Marius Bogoevici (JIRA)
Further clarify the notion of a decorated type
----------------------------------------------
Key: CDI-133
URL: https://issues.jboss.org/browse/CDI-133
Project: CDI Specification Issues
Issue Type: Clarification
Reporter: Marius Bogoevici
Priority: Optional
Essentially, remove the period between the first and second statement and use a single phrase instead:
{quote}
The set of decorated types of a decorator includes all bean types of the managed bean which are Java interfaces, except for <literal>java.io.Serializable</literal>. The decorator bean class and its superclasses are not decorated types of the decorator.
{quote}
This is a rather cosmetic change, but can improve the readability of the section.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] Commented: (CDI-2) Interceptor bindings defined at method level should override those at the class level
by Marius Bogoevici (JIRA)
[ https://issues.jboss.org/browse/CDI-2?page=com.atlassian.jira.plugin.syst... ]
Marius Bogoevici commented on CDI-2:
------------------------------------
https://github.com/jboss/cdi/pull/46
> Interceptor bindings defined at method level should override those at the class level
> -------------------------------------------------------------------------------------
>
> Key: CDI-2
> URL: https://issues.jboss.org/browse/CDI-2
> Project: CDI Specification Issues
> Issue Type: Bug
> Components: Interceptors
> Affects Versions: 1.0
> Reporter: Pete Muir
> Assignee: Marius Bogoevici
> Fix For: 1.1 (Proposed)
>
>
> Gavin said:
> "We certainly *intended* for method-level interceptor bindings to override bindings declared at the class level, but whether we actually wrote that down is another story. It certainly doesn't look like that behavior is properly defined in the latest version of the spec."
> In section 9.5.2 of the spec:
> If the set of interceptor bindings of a bean or interceptor, including bindings inherited from stereotypes and other interceptor bindings, has two instances of a certain interceptor binding type and the instances have different values of some annotation member, the container automatically detects the problem and treats it as a definition error.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
Easier access to CDI outside of Java EE, easier access to instances
by Pete Muir
Regarding https://issues.jboss.org/browse/CDI-14, I've created this patch https://github.com/jboss/cdi/pull/43.
This also touches on CDI-26, which is about providing an embedded mode (API for starting CDI) - it covers about 50% of that issue. It doesn't provide a bootstrap API, but it does provide a programmatic API to access the container:
CDI.current().getBeanManager();
CDI.current().select(MyBean.class).select(new MyQualifierLiteral()).doSomething();
(CDI implements Instance)
I've copied the logic for looking up the current CDI instance from the JPA Persistence class.
Please review, as I know this addresses two much sought after improvement, and I hope that the overall ethos of the approach I've taken you guys like. I suspect there are a couple of rough edges to iron out - specifically, I would like feedback on:
* what happens when multiple CDI providers are located (right now as I straw man I followed JPA's example and returned the first one loaded, not sure if this right)
* Classloading for the providers (Stuart has a comment here)
13 years, 6 months
[JBoss JIRA] Commented: (CDI-86) Support firing general purpose lifecycle events in Java EE environments
by Jozef Hartinger (JIRA)
[ https://issues.jboss.org/browse/CDI-86?page=com.atlassian.jira.plugin.sys... ]
Jozef Hartinger commented on CDI-86:
------------------------------------
Pete,
I think that the scenario mentioned earlier is well covered in you proposal.
>From the language perspective, I don't think the following sentence is correct: "... the ServletContextEvent if the application is a web application *using* deployed to a Servlet container, or ..."
Besides, we should make sure not to forget to reflect CDI-80 within this issue (or vice versa). Your proposal adds @Initialized @Conversation *FacesContext* while with CDI-80 in place FacesContext is not generally the right payload.
> Support firing general purpose lifecycle events in Java EE environments
> -----------------------------------------------------------------------
>
> Key: CDI-86
> URL: https://issues.jboss.org/browse/CDI-86
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Java EE integration
> Affects Versions: 1.0
> Reporter: Pete Muir
> Assignee: Pete Muir
> Fix For: 1.1 (Confirmed)
>
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months