Yes, I think if the exception came from malformed input files (invalid
XML, invalid Java source, etc), then this is definitely what we should
be doing.
On 08/10/2014 11:30 PM, Ondrej Zizka wrote:
Hi all,
Some thoughts for the future:
Windup is that kind of tool that should be robust and try to do
something sensible even with malformed input.
Currently, we throw an exception whenever something unexpected happen,
and halt the app.
I think we should rather continue processing other items, and then
include even those failed in the report, saying why it failed.
Therefore, we should capture the exceptions in the rules, at different
levels, into collections if needed, then turn them into vertices, and
link them to the item during whose processing the exception occured.
Then add it to the report.
Duplicated exceptions can be just summarized.
This is how it worked in WindRide.
Ondra
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev