You might also consider some sort of caching approach that would make the<br>second call to remoteService.getLocation() cheap.<br>-W<br><br><div class="gmail_quote">On 22 March 2012 19:45, lhorton <span dir="ltr"><<a href="mailto:LHorton@abclegal.com" target="_blank">LHorton@abclegal.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">That would be a good approach for one location. My real world rules are 24<br>
rules for 24 different locations. If I used your approach, I think I would<br>
have to look up and insert all 24 locations for each session execution (we<br>
use stateless sessions) in order to have the 24 setter rules work.<br>
<br>
I am trying to avoid too many calls to the RMI service (remote database<br>
reads), which is why I was trying to put all the work into the one rule<br>
pattern. in my real-world rules, there are more conditions in the pattern<br>
than just the RMI lookup, so that only one of the setter rules will fire for<br>
each session execution.<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://drools.46999.n3.nabble.com/Can-I-capture-the-result-of-an-RMI-call-within-a-pattern-tp3848873p3849422.html" target="_blank">http://drools.46999.n3.nabble.com/Can-I-capture-the-result-of-an-RMI-call-within-a-pattern-tp3848873p3849422.html</a><br>
<div><div>Sent from the Drools: User forum mailing list archive at Nabble.com.<br>
_______________________________________________<br>
rules-users mailing list<br>
<a href="mailto:rules-users@lists.jboss.org" target="_blank">rules-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
</div></div></blockquote></div><br>