[ https://issues.jboss.org/browse/WFLY-10784?page=com.atlassian.jira.plugin... ] Matej Novotny commented on WFLY-10784: -------------------------------------- So the problem is that Weld needs to defer initialization until all other EE components are done so that it can do a clean up and save some memory. Without going last, there is no way of telling which bean metadata is safe to drop. However, if there are some EE components which can fail initializing and WildFly still boots up (optional ones, like the one in the reproducer), Weld will not be able to finish init as we add a dependency on all the components in order to go last. There used to be a way in jboss-msc to register an [optional dependency|https://github.com/jboss-msc/jboss-msc/blob/master/src/main/ja...] (as Alex used in PR) but that was deprecated long ago. I haven't figured other way to achieve that yet, or perhaps alternative way to make sure Weld goes last amongst the services. Maybe [~ropalka] or [~dmlloyd] would have some hints? Also ccing [~mkouba]. -- This message was sent by Atlassian JIRA (v7.5.0#75005)