Jean-Sebastien Delfino wrote:
Luciano Resende wrote:
Maybe some warnings should be flaged as FATAL, and an exception would
be thrown at the end of the model processing ?
On Thu, Jul 3, 2008 at 8:12 AM, Mike Edwards
My 2c:
- the model processing should issue Warnings or Errors and continue
processing models after both
- the runtime should be able to start/stop/invoke an artifact with
Warnings, not an artifact with Errors
- we need to pay very close attention to what's a Warning and what's an
Error
- by artifact I meant composite/component/service/reference, for example
if my composite contains 4 components, 3 OK and 1 with an error, then do
we want to allow the 3 components that are OK to be started and invoked?
I'd say yes, but I understand that other people may say no :)
Jean-Sebastien,
I'm in agreement with your view here - but it is also important to be precise about what artifacts
are in error.
In the case which prompted this thread, it is the composite itself which has a problem - two
components with the same name means that it is the composite that is broken, even if the individual
components are in themselves fine. So in this case, the runtime should fail to run the whole
composite. If there are other composites being loaded and they are OK, then sure, there is no
reason to prevent them running.
Yours, Mike.
