5:19 a.m.
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 !
On 1/11/07, Justine Hlista <justine(a)vsasset.com> wrote:
Another newbie question - I'm not sure if what I'm trying to do is legal.
I have two drl files, and one contains a function that I would like to use
from the other. Is that possible? I am loading the one with the function
into the rule base first, then the other. But I get an error message from
the other saying the function cannot be resolved. If I copy the function
into the other, then it works.
Of course, I can always write a Java helper class for a single definition
of the function. But I was just wondering if it is possible to maintain a
single function definition in a drl.
Thanks in advance for any enlightenment!
Justine
11:56 a.m.
New subject: [drools-user] using function from another .drl file
Ah -- that was the problem, I was using a new packagebuilder each time
(d'oh)!
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.
Thanks,
Justine
On 1/12/07, Michael Neale <michael.neale(a)gmail.com> wrote:
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 !
3:24 p.m.
New subject: [drools-user] using function from another .drl file
Yes the PackageDescr object has a package name property which is where the
name lives. Not sure if you can easily get that from PackageBuilder, but if
you go a little more low level, you can use DrlParser to get PackageDescr
yourself, and there you go (peek at the PackageBuilder source code if you
need more hints).
On 1/12/07, Justine Hlista <justine(a)vsasset.com> wrote:
Ah -- that was the problem, I was using a new packagebuilder each time
(d'oh)!
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.
Thanks,
Justine
On 1/12/07, Michael Neale <michael.neale(a)gmail.com> wrote:
>
> 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 !
>
>
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
3:24 p.m.
New subject: [drools-user] using function from another .drl file
There is also an ant task that can take a set of files (rules) and build
them altogether for you if needed.
On 1/12/07, Michael Neale <michael.neale(a)gmail.com> wrote:
Yes the PackageDescr object has a package name property which is where the
name lives. Not sure if you can easily get that from PackageBuilder, but if
you go a little more low level, you can use DrlParser to get PackageDescr
yourself, and there you go (peek at the PackageBuilder source code if you
need more hints).
On 1/12/07, Justine Hlista <justine(a)vsasset.com> wrote:
> Ah -- that was the problem, I was using a new packagebuilder each time
> (d'oh)!
>
> 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.
>
> Thanks,
> Justine
>
>
>
> On 1/12/07, Michael Neale <michael.neale(a)gmail.com > wrote:
> >
> > 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 !
> >
> >
> _______________________________________________
> rules-users mailing list
> rules-users(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>
>
>
6558
days inactive
6558
days old
3 comments
2 participants
participants (2)
-
Justine Hlista -
Michael Neale