7 Replies Latest reply on Oct 4, 2012 6:29 AM by akdabas

CDI: Injecting in war from different war throws WELD Exception (unresolved dependencies)

rostifant Feb 20, 2012 9:42 AM

Hi,

I am trying to inject a stateless Bean to a Managedbean, everything works perfectly if both beans are in the same war. Now, I have divided my project into several wars. Now I am getting a Unsatisfied Dependencies Exception:

Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [ServiceLogin] with qualifiers [@Default] at injection point [[field] @Inject private org.atmosfair.view.login.LoginBean.serviceLogin]

I have already tried to put a dependency in the manifest.mf, but this doesn't work. What am I doing wrong? Or is it just impossible, what I can hardly imagine.

thx for your help

1. Re: CDI: Injecting in war from different war throws WELD Exception (unresolved dependencies)

rostifant Feb 21, 2012 7:07 AM (in response to rostifant)

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?
Actions
2. Re: CDI: Injecting in war from different war throws WELD Exception (unresolved dependencies)

sfcoy Feb 21, 2012 7:14 AM (in response to rostifant)

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.
Actions
3. Re: CDI: Injecting in war from different war throws WELD Exception (unresolved dependencies)

rostifant Feb 21, 2012 7:22 AM (in response to sfcoy)

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.
Actions
4. Re: CDI: Injecting in war from different war throws WELD Exception (unresolved dependencies)

sfcoy Feb 21, 2012 7:38 AM (in response to rostifant)

What do you mean exactly by:
"inject" via jndi
?
Actions
5. Re: CDI: Injecting in war from different war throws WELD Exception (unresolved dependencies)

alesj Feb 21, 2012 8:47 AM (in response to rostifant)

This 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.
1 of 1 people found this helpful
Actions
6. Re: CDI: Injecting in war from different war throws WELD Exception (unresolved dependencies)

rostifant Feb 21, 2012 10:10 AM (in response to alesj)

but how can I inject across multiple dependencies ?
Actions
7. Re: CDI: Injecting in war from different war throws WELD Exception (unresolved dependencies)

akdabas Oct 4, 2012 6:29 AM (in response to rostifant)

Hey Franz,
did you find a solution?
Actions

Go to original post