I have some more incite into what might be causing the problem. Once I remove the drools.package file - which shouldn't be needed since the imports and expander are in the .dslr file - and have a trivial example - I can see an "DSL Rule Translation: Array out of bounds" exception generated in Eclipse several *minutes* later. My DSL makes no mention of arrays and, in this simplest case, am generating
object1 : Car() where object1 and Car are mappings. Once the exception is generated and the dialog box clicked on, you can see the correct translation in the DLR file. Thus, I believe 1. the translator is grinding in an infinite loop, probably just before the file is closed and 2. The exception closes the (correctly translated) file. Is there some token (other than "end") that should be included in the .dslr file to ensure the file closes properly? I don't see any control characters present in the file when I open it in a variety of editors. On antlr, I was referring to an article at http://blog.athico.com/search/label/DSL%20regexp%20antlr that discusses the development of Drools. Thanks! -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Parsing-problems-using-a-DSL-tp2710491p2711243.html Sent from the Drools - User mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
