Initialization event @Initialized Manager fires during broken deployment ------------------------------------------------------------------------ Key: WBRI-213 URL: https://jira.jboss.org/jira/browse/WBRI-213 Project: Web Beans Issue Type: Bug Affects Versions: 1.0.0.BETA1 Reporter: Shane Bryzak According to section 11.1 of the spec, the @Initialized Manager event should only fire after the container fails to detect any definition errors: "First, the container performs bean discovery and registers Bean and Observer objects for the discovered beans. The container detects definition errors by validating the bean classes and metadata, throwing a DeploymentException and aborting deployment of the application if any definition errors exist, as defined in Section 10.1, "Definition errors"." The TCK test org.jboss.jsr299.tck.tests.deployment.lifecycle.fail.DeploymentFailureTest is currently failing, because the initialization event is being raised even though deployment should have failed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira