Well, I still don't see how you insert the event facts.

However, I think you must provide the declares where you define @role(event)
in the first .drl file where these types are used in one or more rules. But failure
to do so should cause a class cast error when the condition of BBBAfterAAA is
evaluated.

Try a rule like this which should show what is in WM:

rule x
when
   $obj: Object()
then
   System.out.println( "fact: " + $obj.getClass() );
end

-W


On 29 August 2011 12:30, eskomk <esko.hujanen@ebsolut.fi> wrote:
Hi Wolfgang et al,

That <drools:batch> is used to run init.drl using mirellaInitBean.
mirellaInitBean is just a stub that fires init.drl which in turn starts
ResourceChangeNotifierService and ResourceChangeScannerService
(I did not remember to replace "mirella" with "CCC" in my original post, see
knowledge-services.xml below. mirella is a product name we are working on).
But this is something that has been verified as working solution, by me
anyway.

But the problem still exist: Our rules do not fire.

Yes, we are inserting facts (events) in real time.

I thought that, in CLOUD mode, you cannot use e.g. @expires in the declare,
or it has no effect.
Is that so ?

Also you must have stateful session to use STREAM mode.
Is that so ?

There is no notion of real-time clock in stateless session.

Cheers,
Esko
-----------
Esko Hujanen
http://www.ebsolut.fi

--
View this message in context: http://drools.46999.n3.nabble.com/How-to-deploy-Fusion-tp3287119p3292367.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users