[
https://issues.jboss.org/browse/CDI-554?page=com.atlassian.jira.plugin.sy...
]
Martin Kouba edited comment on CDI-554 at 2/22/16 9:48 AM:
-----------------------------------------------------------
Yes, John {{@ApplicationScoped}} could be a better match for ServletContext. AFAIR there
some problems with EAR deployments in Weld (see also WELD-1621). But it should be possible
to identify the correct ServletContext by means of TCCL. In any case, it's not defined
at the moment and in Weld the ServletContext is only available when the request scope is
active (servlet {{service()}} invocation, {{@PostConstruct}} callback, etc.).
was (Author: mkouba):
Yes, John {{@ApplicationScoped}} could be a better match for ServletContext. AFAIR there
some problems with EAR deployments in Weld (see also WELD-1621). But it should be possible
to identify the correct ServletContext by means of TCCL. In any case, it's not defined
at the moment and in Weld the ServletContext is only available during HTTP request
processing.
Additional built-in beans do not have a scope defined
-----------------------------------------------------
Key: CDI-554
URL:
https://issues.jboss.org/browse/CDI-554
Project: CDI Specification Issues
Issue Type: Clarification
Affects Versions: 1.2.Final, 2.0-EDR1
Reporter: Martin Kouba
See section 17.8. Additional built-in beans - a scope is not defined for UserTransaction,
Principal, HttpServletRequest, etc. Maybe it's defined somewhere else but I cannot
find anything.
In Weld, Java EE beans are {{@Dependent}}, HttpServletRequest and ServletContext are
{{@RequestScoped}} and HttpSession is {{@SessionScoped}}.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)