Ah -- that was the problem, I was using a new packagebuilder each time (d'oh)!<br><br>But that brings up another thing...in some cases, I may want the rules source for a given package to be spread across multiple drl files. (I know the convention is to have everything from the package in a single drl file, but for management and organization we may need to spread across multiple drl files). In order to add drls to an existing package, I have to be able to get the package name from the drl to look up a hashed builder. Is there any part of the public API,
e.g from the antlr parser, that might help me with that? I have a very inefficient workaround at the moment, but if I could get to the parse interface, I might be able to make it better.<br><br>Thanks,<br>Justine<br><br><br>
<div><span class="gmail_quote">On 1/12/07, <b class="gmail_sendername">Michael Neale</b> <<a href="mailto:michael.neale@gmail.com">michael.neale@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<span class="q">If you use the one packagebuilder, and you add the source first from
the one with the function, and then the others, yes that should work
just fine !<br><br></span></blockquote></div>