It is simply not possible to support the power of a rule engines in the
current pojo/spring approach. Drools 2.5 now compiles rules down to
pojos, it is possible to reference these pojo's interfaces and unit test
those - we produce the a src jar for these rules so you can also debug them.
Mark
Leonardo Susatyo wrote:
Is it true that Spring for Drools will not be
supported in the future? If so, what will be the
alternative b/c i kind of like the spring approach for
easier unit testing
thanks
--- Geoffrey Wiseman <[EMAIL PROTECTED]>
wrote:
On 12/20/05, Leonardo Susatyo <[EMAIL PROTECTED]>
wrote:
Could anyone please tell me how can I define
application-data in rulebase if i'm using
drools-spring?
My knowledge in this area is pretty dated; when we
last tried to do that, we
were on 2.0, possibly not even final, and we
couldn't do it; application
data didn't seem to be working with annotated rules,
and it was suggested
that injection of rules via Spring was a preferred
route for this approach;
we ended up moving to that, althogh there are
instances where this is not
very well suited.
For instance, if your rules are meant to be
parameterized by a processing
data, this is something that can be passed in on a
per-invocation basis with
Application Data but cannot easily be injected.
I can't speak to whether or not this has been
resolved, and I should point
out (before Mark does) that Spring/Drools is
deprecated in the Drools
3.0line, so that's something to consider.
ps: i saw a defect DROOLS 322, is it related?
Codehaus Jira is down, or at least not responding to
my attempts to access
it at the moment, so I can't say.
--
Geoffrey Wiseman
__________________________________________
Yahoo! DSL -- Something to write home about.
Just $16.99/mo. or less.
dsl.yahoo.com
