[
https://issues.jboss.org/browse/CDI-405?page=com.atlassian.jira.plugin.sy...
]
Antoine Sabot-Durand commented on CDI-405:
------------------------------------------
Reproducing IRC discussion between [~pmuir] (pmuir) and [~antoinesabot-durand] (asd) about
this ticket and corresponding PR
{code}
<+pmuir> asd: for
https://github.com/cdi-spec/cdi/pull/204
<+pmuir> I think the new wording is too verbose and wooly
<+asd> +1. Your input as an english native speaker would be very appreciated here
<+pmuir> I wonder if we can't say something like (i.e. to paraphrase) "The
container must provide an implementation of the @RequestScoped, @ApplicationScoped and
@SessionScoped annotations defined in [builtin_contexts] representing the standard scopes
defined by the Java Servlets specification."
<+pmuir> we would need to reword the second bullet as well, to keep the definitions
consistent
<+asd> with that you remove the idea that these context are not restrict to servlet
scopes IMO
<+asd> the main idea should be "it's like scope in servlet spec but it
could be more"
<+asd> the main issue with this is nowhere in the spec we indicate how a third party
spec could extend @RequestScoped...
<+pmuir> that I think we should add to 6.2
<+pmuir> "A context object may be defined for any of the built-in scopes"
<+pmuir> agreed?
<+asd> ok
{code}
So the reword should be simplified and a new mention should be put regarding built-in
scopes extension.
I'm modifying the PR with this new approach.
Reword the description of @RequestScoped and @ApplicationScoped in
section 2.4.1
--------------------------------------------------------------------------------
Key: CDI-405
URL:
https://issues.jboss.org/browse/CDI-405
Project: CDI Specification Issues
Issue Type: Clarification
Reporter: Martin Kouba
Assignee: Antoine Sabot-Durand
Labels: CDI_spec_chge, Ready_to_fix
Fix For: 1.2 Proposed
@RequestScoped and @ApplicationScoped are not servlet-specific (see sections 6.7.1 and
6.7.3 for more use cases).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira