On Thu, Jul 3, 2008 at 4:29 PM, Luciano Resende <[EMAIL PROTECTED]> 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 > <[EMAIL PROTECTED]> wrote: > > Kevin, > > > > My understanding is that the initial model processing step of Tuscany > will > > only generate warnings for these types of error to enable the complete > model > > to get processed and so the maximum number of warnings can be generated > in a > > single pass. > > > > What I'm not sure about is whether the runtime will then try to execute a > > model that has generated a warning of this type. I hope that the runtime > > would refuse to attempt to run the model, since it clearly has a severe > > problem. I don't know whether the current runtime does refuse to run > such > > models, but my hope is that it would not do so. > > > > Other views? > > > > > > Yours, Mike. > > > > > > Kevin Williams wrote: > >> > >> I've noticed that loading a composite file containing duplicate > >> component names results in a warning. Wouldn't an exception make more > >> sense in this case? The Assembly Model spec does not allow > >> duplicates. > >> > > > > > > > > -- > Luciano Resende > Apache Tuscany Committer > http://people.apache.org/~lresende <http://people.apache.org/%7Elresende> > http://lresende.blogspot.com/ > Even if you lodge an error with the monitor it shouldn't stop the processing of other parts of the composite. The monitor is checked for errors in SCADomain and in the node implementation before the composite is activated and started. If an error is found the composite is not run and the runtime stops. So we could change this warning to an error. Simon
