I find the "New missing/unsatisfied dependencies" error in JBoss 7.1.1 Final a little difficult to read. I just wanted to ask if my interpretations of the following lines of the error are correct.
service jboss.deployment.subunit."MyApplication.ear"."MyComponent.jar".component.MyComponent.START (missing) dependents: [service jboss.deployment.subunit."MyApplication.ear"."MyJobComponent.jar".INSTALL]
Does this mean that MyComponent cannot start because MyJobComponent.jar was not installed? And what exactly is missing? MyComponent.START or MyJobComponent.jar.INSTALL? In other words, is the left-hand-side or the right-hand-side of the (missing) string actually missing?
service jboss.naming.context.java.comp.MyApplication.MyComponent.MyComponent (missing) dependents: [service jboss.naming.context.java.comp.MyApplication.MyComponent.MyComponent.Validator, service jboss.naming.context.java.comp.MyApplication.MyComponent.MyComponent.ValidatorFactory, service jboss.naming.context.java.comp.MyApplication.MyComponent.MyComponent.ORB, service jboss.naming.context.java.comp.MyApplication.MyComponent.MyComponent.HandleDelegate]
The confusing thing here is that I know that the Validator, ValidatorFactory and HandleDelegate classes are available in JARs that are provided in the modules directory, namely validation-api-1.0.0.GA.jar and jboss-ejb-api_3.1_spec.jar. How can I tell which of the JARs in the modules directory are made available on startup, and which are not? Is it a case of searching in my standalone-full.xml (the configuration file I am using for startup)?
Finally,in a New missing/unsatisfied dependencies error, are the lines in any kind of meaningful order?
Many thanks in anticipation.
Your first interpretation was right. For some reason, your jar was missing from the classpath. Please look at the classpath of the ear and make changes accordingly.Please go through the following link for a clear understanding.
If you need a module you have to add it to your application by MANIFEST entry or provide a jboss-deployment-structure.xml.
Also you can set a global dependency (if you are want to have it for all your applications e.g. logging) in the standalone.xml.
See AS7 Classloading
Thank you both. I had other issues associated with datasources and Weld amongst others. Resolving these made the "New missing/unsatisfied dependencies" error go away, which perhaps is misleading in that it was not the possible classpath issues I thought of in my original post.
My advice to others seeing this error would be to scan the server.log file and look for any other errors that are reported, and try to fix them.