Ondra, isn't the intent to try to continually improve the XML rules so
they have more and more of the functionality of the Java rules?
On 03/02/2015 07:37 AM, Ondrej Zizka wrote:
Hi,
I'll try to sum up, someone may add or correct.
Groovy: That was an experiment, currently not finished AFAIK.
XML:
Pros: Should be easy and shorter, no need for recompilation, picked up
automatically from a known paths.
Cons: Only supports a subset of conditions and operations (simplier
ones); does not allow direct custom graph data manipulation.
Java:
Pros: Allows pretty much anything; easier debugging; IDE code
completion for Windup API;
Cons: Needs to be an full Forge addon (if not added to Windup core
codebase); needs more code (some of it boilerplate);
A bit more complex - author needs to know more of Windup
internals.
HTH,
Ondra
On 1.3.2015 12:39, Samuel Tauil wrote:
>
> Hi,
>
>
> Why are the advantages and disadvantages of creating a XML or Groovy
> based rule script as opposed to creating a Java Rule Add-on ?
>
> When would one approach be recommended over another ?
>
>
>
> Samuel Tauil
> Senior Solution Architect
> Global Partner Enablement
>
http://www.redhat.com/partners/partner-enablement
>
http://youtu.be/EdsvGcfIoJs
> Ext. 8426191
> Phone +55 11 3524-6191
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev