<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Are you in control of the JAXB code generation? If so, there are a number of plugins about which enable you to control the generation of booleans.</div><div><br></div><div>One I found was:</div><div><a href="https://code.google.com/p/nebulent-xjc-booleangetter/wiki/AboutThisProject">https://code.google.com/p/nebulent-xjc-booleangetter/wiki/AboutThisProject</a></div><div>… although I haven't used it and have no idea how it compares to alternatives.</div><div><br></div><div>At least that way you could ensure that there is an additional getSomething() method generated.</div><div><br></div><div>Steve</div><div><br></div><br><div><div>On 22 Mar 2013, at 16:57, Wolfgang Laun <<a href="mailto:wolfgang.laun@gmail.com">wolfgang.laun@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Heck, I would have considered changing Boolean to boolean, which also<br>works in 5.[45].0, but these classes are JAXB generated, and so<br>there's a good reason for the capital 'B', and I'm stuck with this,<br>and the is...()<br><br>And isSomething() works fine if the return type is *b*oolean.<br><br>-W<br><br>On 22/03/2013, Stephen Masters <<a href="mailto:stephen.masters@me.com">stephen.masters@me.com</a>> wrote:<br><blockquote type="cite">Hi Wolfgang,<br><br>I came across this (or very similar) recently. I think the issue is the<br>bean-style naming convention. The convention is (apparently):<br><br>boolean => isSomething()<br>Boolean => getSomething()<br><br>… which means that Boolean properties are not so readable as boolean.<br><br>Worth giving it a quick try on one of your classes.<br><br>Steve<br><br><br>On 22 Mar 2013, at 16:01, Wolfgang Laun <<a href="mailto:wolfgang.laun@gmail.com">wolfgang.laun@gmail.com</a>> wrote:<br><br><blockquote type="cite">Here I have lots of classes with Boolean methods such as<br> Boolean isSomething()<br>and a large number of rules where<br> X(... something == true,...)<br>used to work fine not too long ago. But 5.5.0 and 5.4.0 claim that<br>this isn't correct:<br> Unable to Analyse Expression adult == true:<br> [Error: unable to resolve method using strict-mode:<br>express.Person.adult()]<br> [Near : {... adult == true ....}]<br><br>This used to work in 5.3.0.<br><br>Trying to avoid the Boolean/bool discrepancy, I replaced true with the<br>object:<br> X(... something == Boolean.TRUE,...)<br>but being as strict as possible doesn't work, too, neither in 5.4.0nor<br>5.5.0.<br><br>This used to work in 5.3.0, and so did the very simple<br> X(... something,...)<br>but not any more.<br><br>The fact that all of the following work in 5.5.0<br> X(... isSomething(),... )<br> X(... isSomething() == true,... )<br> X(... isSomething() == Boolean.TRUE,... )<br>is certainly nice, but:<br><br>Since I'm going to have to change a ton of rules: Which of these<br>versions should I use to have best chances for future compatibility?<br><br>Thanks<br>-W<br>_______________________________________________<br>rules-users mailing list<br><a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/rules-users<br></blockquote><br><br>_______________________________________________<br>rules-users mailing list<br><a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/rules-users<br><br></blockquote><br>_______________________________________________<br>rules-users mailing list<br><a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/rules-users<br></blockquote></div><br></body></html>