Edson wrote: Thanks for the link but I do not see how this helps with my problem. Perhaps it would if I could see the actual .drl files. For example, when I use getClass().getResourceAsStream(...) a null is returned but even it that part worked, it wouldn't be any different than what I currently have. Seeing the .drl file is not the problem. Getting the import statements in the .drl file to actually find the proper classes is. Do you know how the actual .drl files used in the unit testing are referring to the objects they need? Ron _________________________________________________________________ Use video conversation to talk face-to-face with Windows Live Messenger. http://www.windowslive.com/messenger/connect_your_way.html?ocid=TXT_TAGLM...