Paul Sandoz wrote:
>
> You make a good point, the abstract error reporting needs to refer
> back to the concrete model for producing meaningful errors.
>
> The advantage to having a separate holistic validation step, rather
> than when the abstract model is being built, is that a set of
> errors/warnings can be reported using one set of code (also, some
> errors/warnings may only be produced when all information is
> available). It is especially important that we try to report as many
> errors as possible in one go because sometimes resources are only
> processed at runtime, which is the case for resources returned by
> sub-locators.
>
> However, i suppose there are some catastrophic errors when building
> the abstract model so i think it would be good to categorize what
> might be fatal building errors.
So it sounds like we need a combination of as you build errors and then
a mechanism to validate a model against a Resource class object.