If there is a problem with a Reusable Component, it will generate an exception.
Every Reusable Component method, when called synchronously, using the Stateless Session Bean interface or Web service interface, is declared to produce a ReusableComponentException. To handle exceptions more specifically, you can receive subclasses of ReusableComponentException. Each Reusable Component has a specific subclass of ReusableComponentException, and this is what is generally produced. For example, the Aggregation Reusable Component produces an AggregationRUCException if the parameters in the XML or map form cannot be converted into a valid ISensorEvent. Some Reusable Components have additional specific exceptions, such as the Aggregation, Asset Management, and EPCIS Connector Reusable Components. See the details of those Reusable Components for more information on their specific exceptions.
The following are common exceptions that may be generated by any of the Reusable Components.