As far as I am aware there is no other way apart from trial and error. It would be great
if Tattletale would be made to be aware of jboss-modules (I am assuming that it is not, so
apologies if it already is), so it could look at your jar and say
-these classes were not found in any modules
-these are the modules that your jar uses.
On 17 Feb 2011, at 11:05, Jaikiran Pai wrote:
I have been quite frequently running into classloading problems while
working with AS7. It's mainly a result of not having the correct dependencies setup in
my module.xml. For example, if I have class which imports some classes from
jboss-common-core module (let's assume that's the name) and some other classes
from jboss-transaction-integration module then the build completes successfully and
it's only during runtime that I start running into CNFE and/or NCDFE issues. I then I
have to individually track down these dependencies *one at a time* and then go back to add
it as a dependency in my module.xml.
Is there any better way to manage this? I am aware that just adding anything and
everything in the module.xml isn't a right approach, but atleast for classes which are
directly imported into other classes of a module, it would be better to somehow automate
(or better manage) the process of setting up the module.xml. That would atleast minimize
the time spent in fixing the module.xml by trial and error method. Thoughts?
-Jaikiran
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev