-
1. Re: CDI: Injecting in war from different war throws WELD Exception (unresolved dependencies)
I played a little bit with the Configuration. The beans are put correctly in the jndi tree. If a resolve them manually everything works perflectly. But I don't want to replace every Inject with a JNDI lookup. As you can see both wars are in the same classpath, cause I don't get no ClassNotFoundException. What am I doing wrong?
-
2. Re: CDI: Injecting in war from different war throws WELD Exception (unresolved dependencies)
Are these separately deployed WAR files, or are they contained with an enveloping EAR file?
The default behaviour is that separate deployments cannot see each other's classes.
-
3. Re: CDI: Injecting in war from different war throws WELD Exception (unresolved dependencies)
They are seperateley deployed. I know that the classloaders are isolated in different deployments, but as I mentioned before I added one war as a dependency for the other in the manifest.mf. This works because I can "inject" via jndi and don't get a ClassNotFoundException.
-
4. Re: CDI: Injecting in war from different war throws WELD Exception (unresolved dependencies)
What do you mean exactly by:
"inject" via jndi
?
-
5. Re: CDI: Injecting in war from different war throws WELD Exception (unresolved dependencies)
1 of 1 people found this helpfulThis works because I can "inject" via jndi and don't get a ClassNotFoundException.
This is really not a classloading issue.
It's the way CDI resolves dependencies / injections.
And by default, it of course doesn't cross deployment boundaries -- no matter what/how you configure classloading.
-
6. Re: CDI: Injecting in war from different war throws WELD Exception (unresolved dependencies)
but how can I inject across multiple dependencies ?
-
7. Re: CDI: Injecting in war from different war throws WELD Exception (unresolved dependencies)
Hey Franz,
did you find a solution?