ah, right, Here is the test.log:
---------------------
<object-stream>
<org.drools.audit.event.ActivationLogEvent>
<type>4</type>
<activationId>Hello World [0]</activationId>
<rule>Hello World</rule>
<declarations></declarations>
</org.drools.audit.event.ActivationLogEvent>
<org.drools.audit.event.ObjectLogEvent>
<type>1</type>
<factId>1</factId>
<objectToString>java.lang.obj...@19ec4ed</objectToString>
</org.drools.audit.event.ObjectLogEvent>
<org.drools.audit.event.ActivationLogEvent>
<type>5</type>
<activationId>Hello World [0]</activationId>
<rule>Hello World</rule>
<declarations></declarations>
</org.drools.audit.event.ActivationLogEvent>
<org.drools.audit.event.ObjectLogEvent>
<type>1</type>
<factId>2</factId>
<objectToString>com.mycompany.app.droolstest$mess...@fd918a
</objectToString>
</org.drools.audit.event.ObjectLogEvent>
------------------------------
first I inserted the Object then the message.
2010/5/13 Mauricio Salatino <sala...@gmail.com>
> KnoledgeRuntimeLoggerFactory.newConsoleLogger(ksession);
> Probably it's a bug, as mark said, but I want to understand your current
> behavior to be able to analyze the problem.
> Greetings.
>
> 2010/5/13 Michal Bali <michalb...@gmail.com>
>
> Thank you for looking into this.
>>
>> @Salaboy:
>> 1 what do you mean by a runtime logger? (is it agenda logger and
>> workingmemory logger?)
>> 2 yes true. I forgot about that.
>>
>> Best regards,
>> Michal
>>
>> On Thu, May 13, 2010 at 1:45 AM, Salaboy <sala...@gmail.com> wrote:
>>
>>> By the way you understand that doesn't make sense to do that LHS
>>> right? You can do forall(Message())
>>>
>>> - Ing. Mauricio Salatino -
>>>
>>> On May 12, 2010, at 13:52, Michal Bali <michalb...@gmail.com> wrote:
>>>
>>> > Hi,
>>> >
>>> > I have encountered the following problem with the latest Drools 5.1
>>> > SNAPSHOT
>>> >
>>> > I've created a sample Drools project and replaced the Sample.drl
>>> > with the following:
>>> > --Sample.drl--------------------------------------
>>> > package com.sample
>>> >
>>> > import com.sample.DroolsTest.Message;
>>> >
>>> > rule "Hello World"
>>> > when
>>> > forall( Message( )
>>> > Message() )
>>> > then
>>> > System.out.println("executed");
>>> > end
>>> > --------------------------------------------
>>> > If I run the sample application like this everything is fine -
>>> > "executed" is printed. However, if I modify the main method and
>>> > insert some additional fact just before the message fact is
>>> > inserted, like this:
>>> > --DroolsTest.java-----------------------------------
>>> > .....
>>> > ksession.insert(new Object());
>>> > ksession.insert(message);
>>> > .....
>>> > -----------------------------------------------------------
>>> > then the rule won't fire any more.
>>> >
>>> > Please note that if you change the fact insertion order (first the
>>> > message then the Object) it will work as expected.
>>> >
>>> > Is this a bug or am I missing something? I can file a JIRA if needed.
>>> >
>>> > Thank you!
>>> > Best regards,
>>> > Michal
>>> > _______________________________________________
>>> > rules-users mailing list
>>> > rules-users@lists.jboss.org
>>> > https://lists.jboss.org/mailman/listinfo/rules-users
>>> _______________________________________________
>>> rules-users mailing list
>>> rules-users@lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/rules-users
>>>
>>
>>
>> _______________________________________________
>> rules-users mailing list
>> rules-users@lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/rules-users
>>
>>
>
>
> --
> - http://salaboy.wordpress.com
> - http://www.jbug.com.ar
> - Salatino "Salaboy" Mauricio -
>
> _______________________________________________
> rules-users mailing list
> rules-users@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>
>
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
