tag:blogger.com,1999:blog-2002636098451095610.post4275764782601565721..comments2023-12-22T11:14:03.004+01:00Comments on IBM Maximo Customization and Development: Custom Java Action Class ExampleBrunohttp://www.blogger.com/profile/13748160755424198810noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-2002636098451095610.post-4993290250149963452014-09-25T05:02:30.944+02:002014-09-25T05:02:30.944+02:00This comment has been removed by a blog administrator.21st Century Software Solutionshttps://www.blogger.com/profile/03192223264030252287noreply@blogger.comtag:blogger.com,1999:blog-2002636098451095610.post-68668881049996573652013-09-13T05:10:45.218+02:002013-09-13T05:10:45.218+02:00Very good example.
I would replace if (xxx.getMb...Very good example. <br /><br />I would replace if (xxx.getMbo(0) != null) for if (!xxx.isEmpty()), it is clearer to understand and that makes the source code a little more legible. I know it is not exactly the same, but for practical purposes these two "ways" can be used interchangeably.<br /><br />Also, I tend to use variable names ending with "set" when working with MboSets. Another alternative is using "plural" for sets and "singular" for Mbos when naming variables. Typically these differences come handy when you want to iterate a set and assign the "current" Mbo inside the loop to a local variable. <br /><br />I do tend to think these conventions also make the code a little more easy to understand (even by yourself in the future) ;-)<br /><br />jcxperhttps://www.blogger.com/profile/15210470363401627229noreply@blogger.comtag:blogger.com,1999:blog-2002636098451095610.post-31034927766501781022013-07-23T05:39:04.601+02:002013-07-23T05:39:04.601+02:00Very Useful post Bruno. Thank you very much for sh...Very Useful post Bruno. Thank you very much for sharing your knowledge with us :) TEJAhttps://www.blogger.com/profile/10168544518425368014noreply@blogger.com