You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Jervis Liu (JIRA)" <ji...@apache.org> on 2007/03/02 04:06:50 UTC
[jira] Created: (CXF-441) Support the injection of context and
environment entries
Support the injection of context and environment entries
---------------------------------------------------------
Key: CXF-441
URL: https://issues.apache.org/jira/browse/CXF-441
Project: CXF
Issue Type: Sub-task
Components: JAX-WS Runtime
Reporter: Jervis Liu
Assigned To: Jervis Liu
When CXF is deployed into a servlet container, the component's context and environment entries are injected into handlers. JSR-109, section 6.2.3:
With JAX-WS, the handler allows for resources to be injected, typically by using the @Resource annotation. So
a Handler.handle<action>() method may access the component's context and environment entries by using any
resources that were injected. It can also use JNDI lookup of the "java:comp/env" context and accessing
the env-entry-names defined in the deployment descriptor by performing a JNDI lookup. See chapter 15
of the Enterprise JavaBeans specification - Enterprise JavaBeans Core Contracts and Requirements for details.
The container may throw a java.lang.IllegalStateException if the environment is accessed from
any other Handler method and the environment is not available. The element init-params in the
deployment descriptors is no longer used for JAX-WS based container. If needed, the developer should use the
environment entry elements (<env-entry>) declared in the application component's deployment descriptor for
this purpose. These can be injected into the handler using the @Resource annotation or looked up using JNDI.
An example of this use case: http://forums.java.net/jive/thread.jspa?messageID=131230&tstart=0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (CXF-441) Support the injection of context and
environment entries
Posted by "Jervis Liu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jervis Liu closed CXF-441.
--------------------------
> Support the injection of context and environment entries
> ---------------------------------------------------------
>
> Key: CXF-441
> URL: https://issues.apache.org/jira/browse/CXF-441
> Project: CXF
> Issue Type: Sub-task
> Components: JAX-WS Runtime
> Reporter: Jervis Liu
> Assigned To: Jervis Liu
>
> When CXF is deployed into a servlet container, the component's context and environment entries are injected into handlers. JSR-109, section 6.2.3:
> With JAX-WS, the handler allows for resources to be injected, typically by using the @Resource annotation. So
> a Handler.handle<action>() method may access the component's context and environment entries by using any
> resources that were injected. It can also use JNDI lookup of the "java:comp/env" context and accessing
> the env-entry-names defined in the deployment descriptor by performing a JNDI lookup. See chapter 15
> of the Enterprise JavaBeans specification - Enterprise JavaBeans Core Contracts and Requirements for details.
> The container may throw a java.lang.IllegalStateException if the environment is accessed from
> any other Handler method and the environment is not available. The element init-params in the
> deployment descriptors is no longer used for JAX-WS based container. If needed, the developer should use the
> environment entry elements (<env-entry>) declared in the application component's deployment descriptor for
> this purpose. These can be injected into the handler using the @Resource annotation or looked up using JNDI.
> An example of this use case: http://forums.java.net/jive/thread.jspa?messageID=131230&tstart=0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-441) Support the injection of context and
environment entries
Posted by "Jervis Liu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jervis Liu resolved CXF-441.
----------------------------
Resolution: Fixed
> Support the injection of context and environment entries
> ---------------------------------------------------------
>
> Key: CXF-441
> URL: https://issues.apache.org/jira/browse/CXF-441
> Project: CXF
> Issue Type: Sub-task
> Components: JAX-WS Runtime
> Reporter: Jervis Liu
> Assigned To: Jervis Liu
>
> When CXF is deployed into a servlet container, the component's context and environment entries are injected into handlers. JSR-109, section 6.2.3:
> With JAX-WS, the handler allows for resources to be injected, typically by using the @Resource annotation. So
> a Handler.handle<action>() method may access the component's context and environment entries by using any
> resources that were injected. It can also use JNDI lookup of the "java:comp/env" context and accessing
> the env-entry-names defined in the deployment descriptor by performing a JNDI lookup. See chapter 15
> of the Enterprise JavaBeans specification - Enterprise JavaBeans Core Contracts and Requirements for details.
> The container may throw a java.lang.IllegalStateException if the environment is accessed from
> any other Handler method and the environment is not available. The element init-params in the
> deployment descriptors is no longer used for JAX-WS based container. If needed, the developer should use the
> environment entry elements (<env-entry>) declared in the application component's deployment descriptor for
> this purpose. These can be injected into the handler using the @Resource annotation or looked up using JNDI.
> An example of this use case: http://forums.java.net/jive/thread.jspa?messageID=131230&tstart=0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.