I am working with a learning management system that runs on JBoss, using JDK 1.5_18.
There is a way to write classes that it will load at runtime, using reflection, in order to react to set events.
When I write the class in POJO the application will successfully find the class.
I am always using the full name of the class, and I ensure that the jar file that contains the class is in the ear file.
When this class uses a DAO written in plain Java the application works fine.
When the same class instead uses a DAO that is written in Groovy it can't find it.
The groovy-all jar file is in the same ear file.
There are other jar files in the same ear file, that are properly loaded by the application, for handling events, so it would appear that all the jar files are using the same class loader.
The groovy class is in the same jar file as the plain java classes.
So, if it isn't the classloader, and all the requisite jar files are in the ear file, what might be going on?
When I run my unit test against the jar file that calls the class that the application will use, that also passes, so I can see which jar files are needed for the application.