[ https://issues.jboss.org/browse/CDI-95?page=com.atlassian.jira.plugin.sys... ]
Pete Muir closed CDI-95.
------------------------
Resolution: Done
API updated
> Ability to obtain a container-created bean for a Producer or InjectionTarget or for an AnnotatedType
> ----------------------------------------------------------------------------------------------------
>
> Key: CDI-95
> URL: https://issues.jboss.org/browse/CDI-95
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Portable Extensions
> 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
[ https://issues.jboss.org/browse/CDI-95?page=com.atlassian.jira.plugin.sys... ]
Pete Muir reopened CDI-95:
--------------------------
API needs updating still
> Ability to obtain a container-created bean for a Producer or InjectionTarget or for an AnnotatedType
> ----------------------------------------------------------------------------------------------------
>
> Key: CDI-95
> URL: https://issues.jboss.org/browse/CDI-95
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Portable Extensions
> 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
[ https://issues.jboss.org/browse/CDI-95?page=com.atlassian.jira.plugin.sys... ]
Pete Muir closed CDI-95.
------------------------
Assignee: Pete Muir
Fix Version/s: 1.1 (Confirmed)
(was: 1.1 (Proposed))
Resolution: Done
Gavin added this a while back.
> Ability to obtain a container-created bean for a Producer or InjectionTarget or for an AnnotatedType
> ----------------------------------------------------------------------------------------------------
>
> Key: CDI-95
> URL: https://issues.jboss.org/browse/CDI-95
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Portable Extensions
> 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
Add BeanManager to a ServletContext attribute
---------------------------------------------
Key: CDI-117
URL: https://issues.jboss.org/browse/CDI-117
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Java EE integration
Affects Versions: 1.0
Reporter: Christian Kaltepoth
Priority: Minor
CDI 1.0 defines a JNDI lookup as the standard way to obtain the BeanManager for resources not managed by the CDI environment. However in a servlet environment it would be much easier to get the BeanManager from a standardized servlet context attribute. This would be also a major simplification in environments that don't support JNDI (for example GAE) or that don't allow to use the standard JNDI name for the BeanManager (for example Apache Tomcat).
This topic was already discussed on weld-dev about a year ago [1]. Weld 1.0 already supports this [2] and OpenWebBeans also added this feature [3]. Unfortunately Weld 1.1 changed the attribute to a Weld-specific name in [4] which currently leads to much confusion [5].
As both of the major CDI implementations support this feature I think it should finally be put into the spec.
[1] http://lists.jboss.org/pipermail/weld-dev/2010-March/002359.html
[2] https://issues.jboss.org/browse/WELD-202
[3] https://issues.apache.org/jira/browse/OWB-360
[4] https://jira.jboss.org/browse/WELD-679
[5] http://seamframework.org/Community/GettingBeanManagerFromServletContextWi...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/CDI-12?page=com.atlassian.jira.plugin.sys... ]
Pete Muir reassigned CDI-12:
----------------------------
Assignee: Marius Bogoevici
> Specifically exclude methods inherited from java.lang.Object from the list of business method invocations
> ---------------------------------------------------------------------------------------------------------
>
> Key: CDI-12
> URL: https://issues.jboss.org/browse/CDI-12
> Project: CDI Specification Issues
> Issue Type: Bug
> Components: Beans
> Affects Versions: 1.0
> Reporter: Marius Bogoevici
> Assignee: Marius Bogoevici
> Priority: Optional
> Fix For: 1.1 (Proposed)
>
>
> Without this specific exclusion, there is a theoretical possibility to treat these methods as business method invocations.
> - they are defined on the object;
> - will be present on the contextual reference;
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
ValidationFactory -> ValidatorFactory
-------------------------------------
Key: CDI-111
URL: https://issues.jboss.org/browse/CDI-111
Project: CDI Specification Issues
Issue Type: Clarification
Components: Concepts
Reporter: Mark Struberg
Priority: Minor
The CDI-1.0 spec mentions a ValidationFactory, but such a class doesn't exist in JSR-303. Guess Gavin meant the ValidatorFactory.
(catched by Matt Benson)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/CDI-5?page=com.atlassian.jira.plugin.syst... ]
Pete Muir reassigned CDI-5:
---------------------------
Assignee: Marius Bogoevici
> 9.5.1 Around-Invoke Interceptor example have wrong signature
> ------------------------------------------------------------
>
> Key: CDI-5
> URL: https://issues.jboss.org/browse/CDI-5
> Project: CDI Specification Issues
> Issue Type: Bug
> Components: Interceptors
> Affects Versions: 1.0
> Reporter: Aslak Knutsen
> Assignee: Marius Bogoevici
> Fix For: 1.1 (Proposed)
>
>
> The Interceptor example in section 9.5.1 use a illegal method signature for Around-Invoke interceptors:
> @AroundInvoke
> public void aroundInvoke() throws Exception { ... }
> (void and no InvocationContex argument)
> Around-invoke methods have the following signature:
> Object <METHOD>(InvocationContext) throws Exception
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira