On 26 August 2011 17:06, dcrissman
<dac@akc.org> wrote:
Wolfgang Laun-2 wrote:
>
> On 24 August 2011 15:34, dcrissman <dac@akc.org> 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 result
>> > modify drl
>> > wait until kagent rebuilds the kbase
>> > get the new kbase from kagent
>> > Create a stateless ksession
>> > insert some facts
>> > fire all rules
>> > check result
>> >
>> > Also, which version of Drools are you using?
>> >
>>
>> The steps you outline are correct.
>>
>
> You cannot "insert some facts" and "fire all rules" on a stateless
> knowledge
> session. So what is the sequence of API calls? Configurations?
> -W
>
We have a web application running on Tomcat. The user can initiate an action
that fires a series of stateless drules rules.
If I fire up the application on tomcat and execute the action in the portal
that runs the drools rules it works. If I change the drl file while tomcat
is still running, wait for the altered rules to be loaded, then execute the
action again. Some rules will not fire the second time that fired the first
time.
--
View this message in context: http://drools.46999.n3.nabble.com/Rules-stop-firing-when-white-space-is-changed-tp3278986p3287114.html