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.
1 of 1 people found this helpful
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.
In such cases it will be always a good idea to start at the beginning of the log and search for the first warnings and errors and solve this first, because the following applications might be depend on this.
Although @jimidy found the cause of his 'New missing/unsatisfied dependencies' error, his other questions about difficulty understanding the error were not answered:
- is the left-hand-side or the right-hand-side of the (missing) string actually missing?
- in a New missing/unsatisfied dependencies error, are the lines in any kind of meaningful order?
I could not find an answer to these question in Class Loading in AS7 - JBoss AS 7.2 - Project Documentation Editor