Re: [rules-dev] refactoring drools
Hi,
I forgot to post the links I already found:
http://community.jboss.org/wiki/RefactoringRules
http://vimeo.com/5157458
But this is very Eclipse-specific. The problem is:
How do you change the design of a big rule based system if the demands
to it changed? Which common practices do exist?
What do you do with code smells, e.g. duplicate rules.
The answers to the rest of your questions:
Am 09.04.2010 07:02, schrieb Wolfgang Laun:
On Fri, Apr 9, 2010 at 1:21 AM, Franz
Schwab<franz.schwab(a)gmx.net> wrote:
> Hi,
> I'm a computer science student and am writing the related-work part for
> my diploma thesis and would be interested in (scientific) papers or
> information about refactoring or transformation possibilities which can
>
Could you please be more specific? I have heard the term "refactoring"
in connection with certain modifications of a (Java) source program.
Is that the idea?
And "transformation" can be almost anything that produces a B from an A...
http://en.wikipedia.org/wiki/Code_refactoring
> be done with drools / jboss rules in order to improve design of a
> knowledge base
>
How do you define "knowledge base"? Does this mean that you have a measure
for the quality of KBs?
Lets say a rule "based system" instead of "knowledge base"
in the terms
of drools.
or simply to delete bad smells.
http://en.wikipedia.org/wiki/Code_smell
?? If I were inclined to be funny, I'd say you start by opening a
window; but so
I just ask you to be more specific.
No, window is already opened :-)
Thanks, Franz
-W
I have to admit that I
> never worked with drools, as I said I just need that for the
> related-work part.
> Could you please give me some hints?
> Thanks,
> Franz
> _______________________________________________
> 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