[rules-dev] Handling Dynamic Input Data Behaviour

[Mark Proctor]

You need to alter the parser and the Extractor api, you also need to be 
able to deal with ShadowFacts, where we need to know the previous and 
current value.Further to that nested value should not change without 
notifying the parent fact in the network - i.e. correct network state 
must always been maintained. It's a complex area, we are looking at a 
work around that allows this declarative language, but rewrites it as an 
eval - so you don't get the performance advantages - but it's a quick 
work around for now.

Mark
Anirvan Majumdar wrote:
>
> Is there any way to circumvent the constraint that only getter methods 
> can be called from the asserted bean object? If the input data is 
> dynamic in nature and instead I capture it in a HashMap, then how can 
> I retrieve specific key-value pairs in the "when" block of a Rule?
>
> Basically, I need to utilize a method, in the bean, which would have a 
> definition like:
>
> <code>
> public String getValue(String sKey){
>     
>      return (String)hmpData.get(sKey);
>
> }
> </code>
>
> Can this getValue method be accessed by the "when" block? If no, then 
> can someone let me know which class in the source I might have to 
> tweak to extract a similar behavior from the engine?
>
> Thanks a lot!
> Anirvan
> ------------------------------------------------------------------------
>
> _______________________________________________
> rules-dev mailing list
> rules-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-dev
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-dev/attachments/20070514/f10f9508/attachment.html