Brian,<br><br> Can you please provide one example for us to understand better the case?<br><br> Thank you,<br> Edson<br><br><div><span class="gmail_quote">2007/3/28, wasabifan <<a href="mailto:bryan.rickman@kewill.com">
bryan.rickman@kewill.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>In creating a list of rules, I noticed when adding facts to my working memory
<br>it may cause errors if Integer or Long values are null (as they are<br>attempting to do comparisons on null objects...even if other conditions<br>previously listed in that particular rule eliminate this fact from that
<br>particular conflicting rule), however, I have not noticed this behavior for<br>null String objects. Is this the expected behavior, or should they be<br>defaulting to 0 in the comparisons (much like I am assuming the Strings must
<br>be defaulting to empty Strings)?<br><br>Thanks for any clarification. I am using 3.1M1 if that is relevant as well.<br><br>Bryan<br>--<br>View this message in context: <a href="http://www.nabble.com/comparisons-on-Java-primitive-wrapper-class-types-tf3481733.html#a9718377">
http://www.nabble.com/comparisons-on-Java-primitive-wrapper-class-types-tf3481733.html#a9718377</a><br>Sent from the drools - user mailing list archive at <a href="http://Nabble.com">Nabble.com</a>.<br><br>_______________________________________________
<br>rules-users mailing list<br><a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/rules-users">https://lists.jboss.org/mailman/listinfo/rules-users
</a><br></blockquote></div><br><br clear="all"><br>-- <br> Edson Tirelli<br> Software Engineer - JBoss Rules Core Developer<br> Office: +55 11 3124-6000<br> Mobile: +55 11 9218-4151<br> JBoss, a division of Red Hat @
<a href="http://www.jboss.com">www.jboss.com</a>