Provide a bundle that uses the ServiceTracker OSGi mechanism to manage the set of Validator implementations.
When invoked to validate a particular model, it can iterate through each implementation.
Validation results should be Scribble Logger (or possibly another name) - which is responsible for reporting errors etc in an appropriate manner for the environment.
Question: Should the Validation and other mechanisms (e.g. Analysis) be model specific - i.e. do we need a ProtocolValidationManager and ProtocolValidator?
Some validations might be independent of whether it is protocol, conversation, or some other interaction based description derivative. The validator implementations could always check - or simply process the elements that it understands.
Provide a bundle that uses the ServiceTracker OSGi mechanism to manage the set of Validator implementations.
When invoked to validate a particular model, it can iterate through each implementation.
Validation results should be Scribble Logger (or possibly another name) - which is responsible for reporting errors etc in an appropriate manner for the environment.
Question: Should the Validation and other mechanisms (e.g. Analysis) be model specific - i.e. do we need a ProtocolValidationManager and ProtocolValidator?
Some validations might be independent of whether it is protocol, conversation, or some other interaction based description derivative. The validator implementations could always check - or simply process the elements that it understands.