[ https://jira.jboss.org/browse/JBAS-8106?page=com.atlassian.jira.plugin.sy... ] Kabir Khan commented on JBAS-8106: ---------------------------------- To run the tests go into the weld-int/deployer-mc-int folder and execute 'mvn install -Ptest-standalone' which runs the standalone tests. To test against a running AS instance start the AS, uncomment the mentioned section in weld-deployers-jboss-beans.xml and run 'mvn install -Ptest-in-as'. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8106?page=com.atlassian.jira.plugin.sy... ] Kabir Khan commented on JBAS-8106: ---------------------------------- What is currently in WeldBeanMetaDataDeployerPlugin.createContext() is quite hacky. The intent is to not install any of the "system beans" as intermediate beans, leading to WeldKernelControllerContexts, since that always leads to unresolved dependencies and failures. This is currently done by: public KernelControllerContext createContext(Controller controller, DeploymentUnit unit, BeanMetaData beanMetaData) { if (unit.getTopLevel().getAttachment(DeployersUtils.getBootstrapBeanAttachmentName(unit)) == null) { //Not a Weld deployment return null; } if (isSystemBean(unit, beanMetaData)) { //Install Weld deployment bean as normal KernelControllerContext return null; } //Create BeanMetaData & KernelControllerContext for intermediate bean } private boolean isSystemBean(DeploymentUnit unit, BeanMetaData beanMetaData) { String name = beanMetaData.getName(); String topLevelName = unit.getTopLevel().getName(); if (name.contains(topLevelName) || name.contains(unit.getSimpleName()) || name.startsWith("jboss.j2ee:") || name.startsWith("jboss.naming:") || name.startsWith("jboss.ejb3") || name.endsWith("_CompJndiBinder")) return true; return false; } Ideally we should be able to scan the bean for the @Weld property annotations and @WeldEnabled bean level annotations and only deploy beans that have those as intermediate beans giving WeldKCC. With the current setup this is not possible since it the bean class has not yet bean loaded at this stage. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8106?page=com.atlassian.jira.plugin.sy... ] Kabir Khan commented on JBAS-8106: ---------------------------------- "One issue that needs looking into is that currently the Mc->Weld tests that have the "main" Weld bean implemented as an EJB (but rather as a Managed Bean) fail. This is currently worked around by including a dummy KickstartEJB whose only job is to be there to initialise the EJB dependencies when the BootstrapBean calls DynamicDependencyCreator.createDependencies() on Start." This has been fixed by adding a dependency from the bootstrap bean on the deployment unit. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8106?page=com.atlassian.jira.plugin.sy... ] Jason T. Greene updated JBAS-8106: ---------------------------------- Fix Version/s: TBD-6.x (was: 6.0.0.M4) All uncompleted issues are now moved to the new "To be determined for future 6.x releases" category. Feel free to reassign this to a specific release, but only if you have the time to do it -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira