You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Christian Kaltepoth (JIRA)" <ji...@apache.org> on 2010/04/23 08:04:50 UTC
[jira] Created: (OWB-360) Add BeanManager to a ServletContext
attribute
Add BeanManager to a ServletContext attribute
---------------------------------------------
Key: OWB-360
URL: https://issues.apache.org/jira/browse/OWB-360
Project: OpenWebBeans
Issue Type: Improvement
Components: New Features
Affects Versions: M4
Reporter: Christian Kaltepoth
Assignee: Gurkan Erdogdu
Priority: Minor
Attachments: add-bean-manager-to-servlet-context.patch
The specification defines a JNDI lookup as the standard way to obtain the BeanManager for resources not managed by the CDI environment. Nevertheless it would be much easier to get the BeanManager directly from the ServletContext. This behavior is already implemented in Weld and possibly subject of a change request to the specification [1] .
I have attached a patch against the trunk that adds this functionality to OpenWebBeans.
[1] http://lists.jboss.org/pipermail/weld-dev/2010-March/002359.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OWB-360) Add BeanManager to a ServletContext
attribute
Posted by "Christian Kaltepoth (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OWB-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Kaltepoth updated OWB-360:
------------------------------------
Attachment: add-bean-manager-to-servlet-context.patch
patch against trunk
> Add BeanManager to a ServletContext attribute
> ---------------------------------------------
>
> Key: OWB-360
> URL: https://issues.apache.org/jira/browse/OWB-360
> Project: OpenWebBeans
> Issue Type: Improvement
> Components: New Features
> Affects Versions: M4
> Reporter: Christian Kaltepoth
> Assignee: Gurkan Erdogdu
> Priority: Minor
> Attachments: add-bean-manager-to-servlet-context.patch
>
>
> The specification defines a JNDI lookup as the standard way to obtain the BeanManager for resources not managed by the CDI environment. Nevertheless it would be much easier to get the BeanManager directly from the ServletContext. This behavior is already implemented in Weld and possibly subject of a change request to the specification [1] .
> I have attached a patch against the trunk that adds this functionality to OpenWebBeans.
> [1] http://lists.jboss.org/pipermail/weld-dev/2010-March/002359.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (OWB-360) Add BeanManager to a ServletContext
attribute
Posted by "Gurkan Erdogdu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OWB-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gurkan Erdogdu closed OWB-360.
------------------------------
Fix Version/s: 1.0.0
Resolution: Fixed
> Add BeanManager to a ServletContext attribute
> ---------------------------------------------
>
> Key: OWB-360
> URL: https://issues.apache.org/jira/browse/OWB-360
> Project: OpenWebBeans
> Issue Type: Improvement
> Components: New Features
> Affects Versions: M4
> Reporter: Christian Kaltepoth
> Assignee: Gurkan Erdogdu
> Priority: Minor
> Fix For: 1.0.0
>
> Attachments: add-bean-manager-to-servlet-context.patch
>
>
> The specification defines a JNDI lookup as the standard way to obtain the BeanManager for resources not managed by the CDI environment. Nevertheless it would be much easier to get the BeanManager directly from the ServletContext. This behavior is already implemented in Weld and possibly subject of a change request to the specification [1] .
> I have attached a patch against the trunk that adds this functionality to OpenWebBeans.
> [1] http://lists.jboss.org/pipermail/weld-dev/2010-March/002359.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.