As the discussions are ON for the improvements in error handling, currently I would like to take up the task of moving the test cases available in itest/validation module to their respective module code. I believe, this can be done independently w.r.t to the current discussions.
so will start to work on TUSCANY-3152. On Thu, Jul 16, 2009 at 2:29 AM, Simon Laws <[email protected]>wrote: > Kelvin raised TUSCANY-3132 to track any improvements we need to make > to error handling. Now's as good time as any so I kicked off by adding > a couple of sub tasks. > > TUSCANY-3150 - we need to report more accurate context along with out > errors > This needs us to either maintain context in the manager as we > process the hierarchy or throw exception and catch them on the way up. > > TUSCANY-3151 - to stop the runtime when it first encounters an error. > At the moment we accumulate errors as well as warnings and it's just > seems to lead to confusing output > Not sure if this is absolutely necessary but it seems like it would > simplify things. We could throw the exception from the manager but > we'd have to check that this will bubble to the top successfully so > needs to be considered in the context of 3150 > > TUSCANY-3152 - it would seen sensible to have the validation tests > located alongside the functionality they are tested rather than in a > separate itest. The itest is quite difficult to debug as it stands. > > Any more thoughts on this? > > Simon > -- Thanks & Regards, Ramkumar Ramalingam
