I have written a static method, built the assembly, deployed it in to the
GAC, then called it from my rules (defined using the Business Rules
Composer). But for some reason the method just isn't being called. I have
put trace in there to double check.

When I go to test my policy, for some reason the BRC is asking for a fact
creator for the class that has the static method. Why would it need a fact
creator for a static method? Can't I just simply call a static method from
within a rule?

--
McGeeky
http://mcgeeky.blogspot.com

[ Post a follow-up to this message ]

The simple answer is "nope".  Even for static methods, you have to assert a
fact of that type into the engine either with a) fact creator, b) fact
retriever, c) passed as a parameter, or d) using the assert function in the
action step of a rule.

Matt


"McGeeky" <anon@anon.com> wrote in message
news:e7EWjUHYFHA.3132@TK2MSFTNGP09.phx.gbl...
>I have written a static method, built the assembly, deployed it in to the
>GAC, then called it from my rules (defined using the Business Rules
>Composer). But for some reason the method just isn't being called. I have
>put trace in there to double check.
>
> When I go to test my policy, for some reason the BRC is asking for a fact
> creator for the class that has the static method. Why would it need a fact
> creator for a static method? Can't I just simply call a static method from
> within a rule?
>
> --
> McGeeky
> http://mcgeeky.blogspot.com
>
>
>

[ Post a follow-up to this message ]

Thanks for the clarification on that Matt. No wonder my rule wasn't working!

--
McGeeky
http://mcgeeky.blogspot.com


"Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message
news:%23IhySJOYFHA.1404@TK2MSFTNGP09.phx.gbl...
> The simple answer is "nope".  Even for static methods, you have to assert
> a fact of that type into the engine either with a) fact creator, b) fact
> retriever, c) passed as a parameter, or d) using the assert function in
> the action step of a rule.
>
> Matt
>
>
> "McGeeky" <anon@anon.com> wrote in message
> news:e7EWjUHYFHA.3132@TK2MSFTNGP09.phx.gbl... 
>
>

[ Post a follow-up to this message ]