http://blog.maxant.co.uk:80/pebble/ <small>A blog where Ant writes about anything he finds interesting! <a href='http://www.linkedin.com/in/maxant'><font color='white'>Who is Ant?</font></a> <a href='/pebble/pages/copyright.html'><font color='white'>Copyright 2005-2013 Ant Kutschera</font></a></small> en Ant Kutschera Fri, 03 May 2013 04:08:45 GMT Pebble (http://pebble.sourceforge.net) http://backend.userland.com/rss http://blog.maxant.co.uk:80/pebble/2011/05/22/1306092969466.html#comment1367554125139 I don't like hypes, and the fan boys that go with it. And so here I will attempt to get the hype out of the fan boys, if they dare to read the next paragraphs. Node.js is a runtime for Javascript, like Adobe Air is for Actionscript, like the JVM for Java. Every language and its runtime go through the same evolution, where they become more mature: optimized, faster, and have more 3rd party packages. Node.js is now just going through the same evolution the JVM had many many years ago. In time, it will be head-to-head with the JVM, possibly outperforms it in specific routines and trails in others. However, to think that node.js will significantly outperform the JVM, and make the choice of technology based on that, is not wise. Given comparably fast runtimes, the choice of whether to write your program in Javascript or in Java, really is about programming language rather than performance. A hand-coded ultra-optimized NIO implementation in Node will perform comparably with one in Java, because they both will translate to roughly the same underlying system routines being called. If one significantly under-performs another, just means it's not ultra-optimized yet. In the end, it's about whether you want loose-typing, closure, and prototype or you want uber-strict OOP. Javascript is surely shorter and easier to write; but the uber-strictness of Java is intentional. Strictness allows you to enforce paradigms and patterns, which is especially important in very large applications. Java has tons of enterprise experience; Javascript has a lot to prove itself. In summary, node.js simply allows Javascript to be an alternative to full-fledged programming languages for writing any kind of application, that's all. Johnny http://blog.maxant.co.uk:80/pebble/2011/05/22/1306092969466.html#comments http://blog.maxant.co.uk:80/pebble/2011/05/22/1306092969466.html#comment1367554125139 Fri, 03 May 2013 04:08:45 GMT http://blog.maxant.co.uk:80/pebble/2011/11/12/1321129560000.html#comment1366635977781 Great, thank you so much! It works I added a List to the input object and am evaluating the &quot;contains&quot; in the rule like below. Rule wageUnitHour = new Rule(&quot;prewailingWageUnit&quot;, &quot;input.wageUnitsHour contains input.wageUnit &quot; , &quot;HOUR&quot;,3, &quot;com.rules.wage.unit&quot;, null); Anonymous http://blog.maxant.co.uk:80/pebble/2011/11/12/1321129560000.html#comments http://blog.maxant.co.uk:80/pebble/2011/11/12/1321129560000.html#comment1366635977781 Mon, 22 Apr 2013 13:06:17 GMT http://blog.maxant.co.uk:80/pebble/2011/11/12/1321129560000.html#comment1366623647300 Try adding two fields to the input object: wageUnit and wageUnitsHour (which is your arraylist). Then a rule like this might work: &quot;if(input.wageUnitsHour.contains(input.wageUnit))&quot;. Alternatively, can you build the list inside the rule? Ant Kutschera http://blog.maxant.co.uk:80/pebble/2011/11/12/1321129560000.html#comments http://blog.maxant.co.uk:80/pebble/2011/11/12/1321129560000.html#comment1366623647300 Mon, 22 Apr 2013 09:40:47 GMT