10:43 a.m.
If I'm eligible to vote, please go for option 1.
Am 19.09.2011 17:14 schrieb "Jiri Svitak" <jsvitak(a)redhat.com>:
10:57 a.m.
New subject: Formal verification of Drools - master's thesis
Hi Jiri,
Drools Verifier do that for you? Am I right? 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 <
ansgar.konermann(a)googlemail.com> wrote:
If I'm eligible to vote, please go for option 1.
Am 19.09.2011 17:14 schrieb "Jiri Svitak" <jsvitak(a)redhat.com>:
_______________________________________________
rules-dev mailing list
rules-dev(a)lists.jboss.org
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 -
11:14 a.m.
New subject: Formal verification of Drools - master's thesis
On 19 September 2011 17:57, Mauricio Salatino <salaboy(a)gmail.com> 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 <
ansgar.konermann(a)googlemail.com> wrote:
> If I'm eligible to vote, please go for option 1.
> Am 19.09.2011 17:14 schrieb "Jiri Svitak" <jsvitak(a)redhat.com>:
>
> _______________________________________________
> rules-dev mailing list
> rules-dev(a)lists.jboss.org
> 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
rules-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
11:18 a.m.
New subject: Formal verification of Drools - master's thesis
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 <wolfgang.laun(a)gmail.com>wrote:
On 19 September 2011 17:57, Mauricio Salatino
<salaboy(a)gmail.com> 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 <
> ansgar.konermann(a)googlemail.com> wrote:
>
>> If I'm eligible to vote, please go for option 1.
>> Am 19.09.2011 17:14 schrieb "Jiri Svitak" <jsvitak(a)redhat.com>:
>>
>> _______________________________________________
>> rules-dev mailing list
>> rules-dev(a)lists.jboss.org
>> 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
> rules-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-dev
>
>
_______________________________________________
rules-dev mailing list
rules-dev(a)lists.jboss.org
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 -
8:05 a.m.
New subject: Formal verification of Drools - master's thesis
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
<wolfgang.laun(a)gmail.com <mailto:wolfgang.laun@gmail.com>> wrote:
On 19 September 2011 17:57, Mauricio Salatino <salaboy(a)gmail.com
<mailto:salaboy@gmail.com>> 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
<ansgar.konermann(a)googlemail.com
<mailto:ansgar.konermann@googlemail.com>> wrote:
If I'm eligible to vote, please go for option 1.
Am 19.09.2011 17:14 schrieb "Jiri Svitak"
<jsvitak(a)redhat.com <mailto:jsvitak@redhat.com>>:
_______________________________________________
rules-dev mailing list
rules-dev(a)lists.jboss.org <mailto:rules-dev@lists.jboss.org>
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
rules-dev(a)lists.jboss.org <mailto:rules-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/rules-dev
_______________________________________________
rules-dev mailing list
rules-dev(a)lists.jboss.org <mailto:rules-dev@lists.jboss.org>
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
rules-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
8:17 a.m.
New subject: Formal verification of Drools - master's thesis
Really don't mean to sidetrack or anything this thread. I think the
stuff discussed is really awesome, just from my experience with a master
thesis it should include something "novel". Just asking what is this
"novel" part in what you are planning to do? If this is a project for a
masters degree, then forget my question :)
Thanks.
On 9/20/11 9:05 AM, 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
> <wolfgang.laun(a)gmail.com <mailto:wolfgang.laun@gmail.com>> wrote:
>
> On 19 September 2011 17:57, Mauricio Salatino <salaboy(a)gmail.com
> <mailto:salaboy@gmail.com>> 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
> <ansgar.konermann(a)googlemail.com
> <mailto:ansgar.konermann@googlemail.com>> wrote:
>
> If I'm eligible to vote, please go for option 1.
>
> Am 19.09.2011 17:14 schrieb "Jiri Svitak"
> <jsvitak(a)redhat.com <mailto:jsvitak@redhat.com>>:
>
> _______________________________________________
> rules-dev mailing list
> rules-dev(a)lists.jboss.org <mailto:rules-dev@lists.jboss.org>
> 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
> rules-dev(a)lists.jboss.org <mailto:rules-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/rules-dev
>
>
>
> _______________________________________________
> rules-dev mailing list
> rules-dev(a)lists.jboss.org <mailto:rules-dev@lists.jboss.org>
> 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
> rules-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-dev
_______________________________________________
rules-dev mailing list
rules-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
8:30 a.m.
New subject: Formal verification of Drools - master's thesis
Oh great.. sorry for the confusion!
On Tue, Sep 20, 2011 at 10:05 AM, Jiri Svitak <jsvitak(a)redhat.com> 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 <wolfgang.laun(a)gmail.com>wrote:
> On 19 September 2011 17:57, Mauricio Salatino <salaboy(a)gmail.com> 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 <
>> ansgar.konermann(a)googlemail.com> wrote:
>>
>>> If I'm eligible to vote, please go for option 1.
>>> Am 19.09.2011 17:14 schrieb "Jiri Svitak"
<jsvitak(a)redhat.com>:
>>>
>>> _______________________________________________
>>> rules-dev mailing list
>>> rules-dev(a)lists.jboss.org
>>> 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
>> rules-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/rules-dev
>>
>>
>
> _______________________________________________
> rules-dev mailing list
> rules-dev(a)lists.jboss.org
> 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
listrules-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/rules-dev
_______________________________________________
rules-dev mailing list
rules-dev(a)lists.jboss.org
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 -
9:02 a.m.
New subject: Formal verification of Drools - master's thesis
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 <wolfgang.laun(a)gmail.com>
wrote:
> On 19 September 2011 17:57, Mauricio Salatino <salaboy(a)gmail.com> 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
<ansgar.konermann(a)googlemail.com> wrote:
> If I'm eligible to vote, please go for option 1.
>
> Am 19.09.2011 17:14 schrieb "Jiri Svitak" <jsvitak(a)redhat.com>:
>
> _______________________________________________
> rules-dev mailing list
> rules-dev(a)lists.jboss.org
> 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
> rules-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-dev
>
>
>
> _______________________________________________
> rules-dev mailing list
> rules-dev(a)lists.jboss.org
> 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
> rules-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-dev
_______________________________________________
rules-dev mailing list
rules-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
11:18 a.m.
New subject: Formal verification of Drools - master's thesis
From: rules-dev-bounces(a)lists.jboss.org [mailto:rules-dev-bounces@lists.jboss.org] On
Behalf Of Wolfgang Laun
Sent: 19 September 2011 17:15
To: Rules Dev List
Subject: Re: [rules-dev] Formal verification of Drools - master's thesis
On 19 September 2011 17:57, Mauricio Salatino
<salaboy@gmail.com<mailto:salaboy@gmail.com>> 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.
[Swindells, Thomas] I'd agree, but I think this ideally would include the bytecode
output by drools - not the user specific parts (if users put issues in their code it's
their own fault) but the boiler plate code it produces.
-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
<ansgar.konermann@googlemail.com<mailto:ansgar.konermann@googlemail.com>>
wrote:
If I'm eligible to vote, please go for option 1.
Am 19.09.2011 17:14 schrieb "Jiri Svitak"
<jsvitak@redhat.com<mailto:jsvitak@redhat.com>>:
_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org<mailto:rules-dev@lists.jboss.org>
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
rules-dev@lists.jboss.org<mailto:rules-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/rules-dev
________________________________
**************************************************************************************
This message is confidential and intended only for the addressee. If you have received
this message in error, please immediately notify the postmaster(a)nds.com and delete it from
your system as well as any copies. The content of e-mails as well as traffic data may be
monitored by NDS for employment and security purposes. To protect the environment please
do not print this e-mail unless necessary.
NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United
Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603
8808 40-00
**************************************************************************************
4820
days inactive
4821
days old
8 comments
7 participants
participants (7)
-
Ansgar Konermann -
Jiri Svitak -
Mauricio Salatino -
Swindells, Thomas -
Tihomir Surdilovic -
Toni Rikkola -
Wolfgang Laun