Ron Kneusel wrote:
Edson wrote:
  
Right now, Drools uses JUnit for all its unit and integration tests. Take a look at the integration tests and I think you will figure out:
http://anonsvn.jboss.org/repos/labs/labs/jbossrules/trunk/drools-compiler/src/test/java/org/drools/integrationtests/
    

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.
  
You don't have your DRLs in the correct location, our DRLs mirror the path of the class that is loading them via getClass().getResourceAsStream():
http://anonsvn.jboss.org/repos/labs/labs/jbossrules/trunk/drools-compiler/src/test/resources/org/drools/integrationtests/
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?
  
It just does a loadClass on the classLoader, as long as your classes are in the classpath it will find them.
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_WL_Refresh_messenger_video_072008
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users