[cdi-dev] [JBoss JIRA] (CDI-392) Clarify when the operations of BeanManager can be called
Antoine Sabot-Durand (JIRA)
issues at jboss.org
Wed Mar 12 11:31:10 EDT 2014
[ https://issues.jboss.org/browse/CDI-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952350#comment-12952350 ]
Antoine Sabot-Durand commented on CDI-392:
------------------------------------------
I agree with [~struberg]. I've experienced this bug in CDI 1.0, I'd prefer to have an exception. Unless there's another reason I think we should get rid of this "container is permitted to define a non-portable mode..." mention
> Clarify when the operations of BeanManager can be called
> --------------------------------------------------------
>
> Key: CDI-392
> URL: https://issues.jboss.org/browse/CDI-392
> Project: CDI Specification Issues
> Issue Type: Clarification
> Reporter: Matus Abaffy
> Assignee: Mark Struberg
> Labels: CDI_spec_chge, Ready_to_fix
> Fix For: 1.2 Proposed
>
>
> The current version of spec. states (under 11.3. The BeanManager object): "Any operation of BeanManager may be called at any time during the execution of the application."
> This sentence is likely to be misinterpreted (see WELD-1453). Pointing out that BeanManager's methods can be called (without causing exception) just after AfterDeploymentValidation event is fired might be helpful.
--
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
More information about the cdi-dev
mailing list