We use the MVP and Activities&Places patterns in Guvnor. These are something that the programmer should just know how to use, nothing is forcing us to use them and it is easy to go around them by mistake or intentionally.
Some are checks for dirty code, some for bugs: * The presenter or model contains UI or GWT components * The presenter is missing an unit test * The view contains too much logic * GWT EventBus is passed into activity classes in constructor or in some other method than the Activity.start() method * Classes that should be created with GWT.create() are created using new * There is a Place that does not lead to any Activity * There is an Activity, but no Place that would lead to it * There is an event raised and pushed into the eventbus, but no GWT event handler * The event handler exists, but there is no event created to match it Toni On Sep 20, 2011, at 4:05 PM, Jiri Svitak wrote: > The thesis would be aimed at verifying Drools Java code. With Findbugs you > can find bugs in every Java project, but in this case the Findbugs would use > user defined bug patterns (based on JIRAs/Bugzillas). > Drools verifier is intended to verify correctness of user's DRL using static > analysis. > > Model checking is more difficult to do. It executes code, so I would have to > create environment for it to run, for example an application which uses > Drools. Then verify some property of the system. > > > On 09/19/2011 06:18 PM, Mauricio Salatino wrote: >> >> Exactly, I thought that the main point is verify the correctness of the >> Rules, If I misunderstood that sorry.. >> If you are talking about only finding bugs in the Drools code, it will be >> the same as finding bugs in any other project right? >> I'm just curious.. >> >> Best Regards! >> >> On Mon, Sep 19, 2011 at 1:14 PM, Wolfgang Laun <[email protected]> >> wrote: >> On 19 September 2011 17:57, Mauricio Salatino <[email protected]> wrote: >> Hi Jiri, >> Drools Verifier do that for you? Am I right? >> >> I think this is a misunderstanding. Looking at Drools' Java code takes a >> Java bug finding program such as findbugs. What Drools Verifier does is: >> look at DRL code written by Drools users. >> >> Findbugs applied to Drools code is a good idea, but I would opt for this to >> include fundamental code that's used by Drools and responsible for a >> considerable number of JIRAs. >> >> -W >> >> >> Toni Rikkola is the man behind drools verifier, you can talk with him to >> improve what he has now. I know that Esteban was also playing with that and >> adding the concept of Working Set. You can talk with him as well. >> Cheers >> >> On Mon, Sep 19, 2011 at 12:43 PM, Ansgar Konermann >> <[email protected]> wrote: >> If I'm eligible to vote, please go for option 1. >> >> Am 19.09.2011 17:14 schrieb "Jiri Svitak" <[email protected]>: >> >> _______________________________________________ >> rules-dev mailing list >> [email protected] >> https://lists.jboss.org/mailman/listinfo/rules-dev >> >> >> >> >> -- >> - CTO @ http://www.plugtree.com >> - MyJourney @ http://salaboy.wordpress.com >> - Co-Founder @ http://www.jugargentina.org >> - Co-Founder @ http://www.jbug.com.ar >> >> - Salatino "Salaboy" Mauricio - >> >> >> _______________________________________________ >> rules-dev mailing list >> [email protected] >> https://lists.jboss.org/mailman/listinfo/rules-dev >> >> >> >> _______________________________________________ >> rules-dev mailing list >> [email protected] >> https://lists.jboss.org/mailman/listinfo/rules-dev >> >> >> >> >> -- >> - CTO @ http://www.plugtree.com >> - MyJourney @ http://salaboy.wordpress.com >> - Co-Founder @ http://www.jugargentina.org >> - Co-Founder @ http://www.jbug.com.ar >> >> - Salatino "Salaboy" Mauricio - >> >> >> >> _______________________________________________ >> rules-dev mailing list >> [email protected] >> https://lists.jboss.org/mailman/listinfo/rules-dev > > _______________________________________________ > rules-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/rules-dev
_______________________________________________ rules-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-dev
