I think this is the time to suggest that you create a complete app
demonstrating
the effect so that it can be investigated by whomsoever and/or a JIRA can be
raised.
-W
On 29 August 2011 16:04, dcrissman wrote:
>
> Wolfgang Laun-2 wrote:
> >
> > The only thing you can do with a Stateless Knowled
Wolfgang Laun-2 wrote:
>
> The only thing you can do with a Stateless Knowledge Session is to call
> its
> execute method, overloaded to take a single object or a collection of
> objects to be inserted
> or a command to be executed. A command may not do much more than execute
> with insert(s): ge
The only thing you can do with a Stateless Knowledge Session is to call its
execute method, overloaded to take a single object or a collection of
objects to be inserted
or a command to be executed. A command may not do much more than execute
with insert(s): get/setGlobal is also possible. What comm
Wolfgang Laun-2 wrote:
>
> On 24 August 2011 15:34, dcrissman wrote:
>
>>
>> Esteban wrote:
>> >
>> > What are the steps you are following? Something like this?:
>> >
>> > The agent creates the kbase
>> > Get kbase from kagent
>> > Create a stateless ksession
>> >
On 24 August 2011 15:34, dcrissman wrote:
>
> Esteban wrote:
> >
> > What are the steps you are following? Something like this?:
> >
> > The agent creates the kbase
> > Get kbase from kagent
> > Create a stateless ksession
> > insert some facts
> > fire all rules
> > check
Edson Tirelli-4 wrote:
>
> Did you tried Drools 5.1.1? or 5.2? Lots of bugs were fixed since 5.1.0...
>
I am currently looking into experimenting with the newer version of drools,
but am running into some issues with strict mode. I created another thread
to try and address that problem over at:
Did you tried Drools 5.1.1? or 5.2? Lots of bugs were fixed since
5.1.0...
Edson
2011/8/24 dcrissman
>
> Esteban wrote:
> >
> > What are the steps you are following? Something like this?:
> >
> > The agent creates the kbase
> > Get kbase from kagent
> > Create a stateless kses
Esteban wrote:
>
> What are the steps you are following? Something like this?:
>
> The agent creates the kbase
> Get kbase from kagent
> Create a stateless ksession
> insert some facts
> fire all rules
> check result
> modify drl
> wait until kagent rebuilds the k
@Wolfgang: I have that in my TODO list for a long time. Right now it is
possible to create that mechanism using Agent listener and manipulating
ResourceScanner manually. Something similar to what KAgent tests are doing.
But the problem here seems to be different because of 2 reasons:
1. He doe
Incremental change set processing might create the effect you describe.
Declared types are always replaced; rules only if they differ.
It sure would be nice if the effects of knowledge base updates were
described in a way that leaves no room for guesswork. "Gimme hope,
Jo'anna..."
-W
On 23 Aug
What are the steps you are following? Something like this?:
1. The agent creates the kbase
2. Get kbase from kagent
3. Create a stateless ksession
4. insert some facts
5. fire all rules
6. check result
7. modify drl
8. wait until kagent rebuilds the kbase
9. get the new
It seems that the rules that stop firing are dependent on another rule which
is responsible for creating drools declared objects with a logicalInsert.
Seems to be the only commonality that I can find.
Oh, and I am using a stateless session.
Example:
declare MyClass
end
rule "Create Instance"
wh
I have an issue where I am changing white-space in a drl file and suddenly
some rules stop firing, but others do not. Has anyone seen behavior like
this?
I have the resource-change-scanner configured to watch the drl file for
changes, and then the following output is displayed:
KnowledgeAgent appl
13 matches
Mail list logo