[cdi-dev] [JBoss JIRA] (CDI-245) Promote the right way how extensions should communicate with each other during container initialization

[ https://issues.jboss.org/browse/CDI-245?page=com.atlassian.jira.plugin.sy... ] Pete Muir edited comment on CDI-245 at 8/24/12 6:13 PM: -------------------------------------------------------- Interestingly, the quote does say "may observe any event", which supports [~mkouba]'s original point. I think we can close this issue out by saying: * If a portable extension fires a container lifecycle event, non-portable behavior results * That an extension can fire a regular event by calling BeanManager.fireEvent() * Opening a new issue around contexts being active during bootstrap, as we don't really need that, as extensions are not defined as beans, but as objects which can take advantage of some CDI capabilities I'll draft up these changes and open a new issue. was (Author: pmuir): Interestingly, the quote does say "may observe any event", which supports [~mkouba] original point. I think we can close this issue out by saying: * If a portable extension fires a container lifecycle event, non-portable behavior results * That an extension can fire a regular event by calling BeanManager.fireEvent() * Opening a new issue around contexts being active during bootstrap, as we don't really need that, as extensions are not defined as beans, but as objects which can take advantage of some CDI capabilities I'll draft up these changes and open a new issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira