[windup-dev] Problems with XML

Brad Davis bdavis at redhat.com
Wed Dec 10 09:57:54 EST 2014


I think maybe the processor itself would be aware of whether it should be iterative or single.  For example, Classification should know "I may get a set of results, but I only need one result to properly classify this resource".  While, Hints should know "If I get a set of results, I should add it to each one." 

That is my thought anyway.

Brad Davis
Senior Manager, Red Hat Consulting
Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com 


----- Original Message -----
From: "Lincoln Baxter, III" <lincolnbaxter at gmail.com>
To: "Matej Briskar" <mbriskar at redhat.com>, "Windup-dev List" <windup-dev at lists.jboss.org>
Sent: Tuesday, December 9, 2014 11:50:58 PM
Subject: [windup-dev] Problems with XML



Matej, 

This XML is repeated in almost all the rules we have so far... 

<perform> 
<iteration> 
<hint .... > 
</iteration> 
</perform> 

This XML mayactually be creating a nested iteration over no elements. One iteration created by default in the <perform> method, the next one by the subsequent <iteration>... 

Iteration is implied if omitted, so this may be the problem, not sure. 
I am going to look into this more tomorrow. But if you get to it before I do, this may be a place to start looking. Try removing the <iteration> tags and putting the child nodes into <perform> directly. 

-- 
Lincoln Baxter, III 
http://ocpsoft.org 
"Simpler is better." 

_______________________________________________
windup-dev mailing list
windup-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev


More information about the windup-dev mailing list