1 of 1 people found this helpful
If the POJO class is defined in the EJB jar then Quartz will not be able to to "see" it as they exist in different class loaders. You need to move the POJO class into a jar in the EAR/lib directory so that it shares the same class loader as quartz and yet is still visible to the EJB jar.
Thanks for your looks it will work. I need one more clarification, at present my pojo classes are bundled in shared project jar which is add a project dependency to my jar and thats how it is visible to my jar.
What want to understand here is that to make my POJO visible to quartz i have to put this pojo bundle in lib ? please correct me if im gettingn it wrong?
That is exactly right.
All jars in the EAR/lib directory share a class loader that makes classes available to all other modules (such as EJB jars and WARs) in the EAR.
However, the EAR/lib class loader cannot see the classes in those other modules.