This is a galactically bad idea. Using a global in this way is inherently unsafe as there's no guarantee that ebtween the time you set the var and when it's used later in the condition that the value is the same. What is your reason for wanting to use a global in this way? You should use a temporary bound variable instead.
--- On Fri, 8/21/09, Shah, Malay <[email protected]> wrote: > From: Shah, Malay <[email protected]> > Subject: [rules-users] populating global variable in Condition Section? > To: [email protected] > Date: Friday, August 21, 2009, 3:19 PM > > > > > > > Hi, > > Is it possible > to populate a global variable in > the condition section of the > drool rule, and use it later in the condition itself? > I currently have a > global HashSet variable that I construct before firing > the rule, but I > would like this code of constructing this global variable > to be with the drool > rule itself. Any help on this would be much > appreciated. > > Thanks > > Malay > > > > NOTICE: If received in error, please > destroy, and notify sender. Sender does not intend to waive > confidentiality or privilege. Use of this email is > prohibited when received in error. We may monitor and store emails to the > extent > permitted by applicable law. > > > -----Inline Attachment Follows----- > > _______________________________________________ > rules-users mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/rules-users > _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
