java-ee,dependency-injection,cdi,jboss-weld
Congratulation ! You've just discovered a bug in Weld : https://issues.jboss.org/browse/WELD-1855 While waiting for the fix, you can use this workaround. Change your EJB to : @Stateless @LocalBean public class MyService<T extends MasterDbo<? extends DetailDbo>, D extends DetailDbo>{ //implemetation } It should work....
jboss7.x,cdi,entitymanager,jboss-weld
Error found: the EJB module was present twice in the generated EAR, once on the root path of the EAR file and a second time in the WEB-INF/lib folder of the WAR file. I changed the dependency declaration in the WAR project's POM file from: <dependency> <groupId>br.com.sigga</groupId> <artifactId>siot-mobility-ejb</artifactId> </dependency> to:...
Check out https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Web_Platform/5/html/Seam_Reference_Guide/ch07s11.html "Where interceptor order is important, add @Interceptor annotations to your interceptor classes to specify a particular order of interceptors." @Interceptor(around={BijectionInterceptor.class, ValidationInterceptor.class, ConversationInterceptor.class}) public class LoggedInInterceptor { ... } So with one interceptor it is not very useful ... ...
java,gradle,jboss-weld,weld-se
Having spent more time than seems sane on a problem like this, I was finally able to hunt down the origin of my issue. It has to do neither with Weld nor Jandex, but rather the way Gradle structures its output directories: The :build task creates two separate output folders...
ejb,cdi,wildfly,jboss-weld,wildfly-8
Take a look at this Wildfly issue; https://issues.jboss.org/browse/WFLY-4116 This issue relates to; "WAR deployment fails on missing security domain dependency" and contains error traces in the log output that are similar in nature to the ones reported. Specifically, constructs like; <jboss-web> <security-domain>java:/jaas/haa-portal</security-domain> </jboss-web> should be replaced with; <jboss-web> <security-domain>haa-portal</security-domain> </jboss-web>...
jsf,session,cdi,wildfly,jboss-weld
It seems we did encounter a Wildfly 8.2 bug, located in Weld. See this jira for more information : https://issues.jboss.org/browse/WFLY-4753 The fix has been to patch Wildfly with this patch : http://sourceforge.net/projects/jboss/files/Weld/2.2.12.Final Thank you all...
java,java-ee,dependency-injection,cdi,jboss-weld
The tutorial is a bit ambiguous (pun intended) about which classes should be deployed simulataneously in each step, so I wouldn't worry about that too much. The answer to the other question you linked does match your case. BankOfAmerica is a bean of type Bank (in CDI 1.0 or in...
I assume the question refers to OSGi, as it wouldn't make sense to use Pax CDI otherwise. Pax CDI creates a separate CDI container and thus a separate bean manager per bean bundle. For this reason, it is not quite obvious what the current bean manager should be. As of...