||This type of exception is thrown when processing an ActionDocument and a given Contract or
Provider Implementation and a general failure occurs.
||This type of exception is thrown when a given Contract or Provider Implementation has something
wrong related to service binding.
||This exception gets thrown from inside the Service Directory when instantiation of implementations
include resource and service injection.
||This is a base exception type for some exceptions that are missing required bits of meta-data information.
||Annotations are a primary way that service information is captured by service developers and
passed along to the framework; if a required annotation is missing, the framework will not know
what to do with the service.
||This type of exception is thrown when a given Contract or Provider Implementation does not implement
a required interface.
||This is thrown when a dynamic proxy cannot be created.
||When an attempt to bind a service implementation to a service definition fails, you often will get
this exception thrown.
||This is a root exception of most of the framework's exceptions and errors.
||These types of exceptions need to be mapped to acceptable types for proper passage through the proxy.
||When a service is registered but is in a state that makes it impossible to handle requests,
you will see this exception.
||This self-describing exception occurs when trying to access an implementation
via a versioned implementation name.
||This self-describing exception occurs when a service is requested that is unknown to the
directory (not registered).