Exceptions

All SeedStack exceptions extend BaseException which is a RuntimeException. This means that you are not required to catch framework exceptions although you can do so if needed.

All SeedStack exceptions display a detailed information report about the failure. Consider this example:

org.seedstack.seed.SeedException: [CORE] Unexpected exception


Description
-----------
Unexpected exception during Seed startup or shutdown.

Causes
------

1. com.google.inject.ProvisionException: Unable to provision, see the following errors:
   
   1) Error injecting org.seedstack.seed.core.ConfigurationIT$Holder using
   org.seedstack.seed.core.internal.configuration.ConfigurationMembersInjector@17271176.
    Reason: [CORE] Unable to inject configuration value
     while locating org.seedstack.seed.core.ConfigurationIT$Holder
   
   1 error @(InjectorImpl.java:1025)

2. [CORE] Unable to inject value from configuration key 'missingProperty' in field 'configObject2' of class
   'org.seedstack.seed.core.ConfigurationIT.Holder'. @(ConfigurationMembersInjector.java:54)

3. [CORE] Missing mandatory configuration key 'missingProperty'. @(ConfigurationMembersInjector.java:48)

Fix
---
Ensure that the configuration key 'missingProperty' is present and that the configuration source is correctly detected.

Online information
------------------
http://seedstack.org/docs/seed/configuration#usage

Stacktrace
----------
...

You can find the following information in this exception report:

• The exception type: SeedException.
• The module and the error code: CORE and Unexpected exception.
• The textual description of the error: «Unexpected exception during Seed startup or shutdown».
• A list of causes which is built from the Java exception chaining mechanism:
  • A Guice ProvisionException which occurred when trying to inject a class,
  • A SeedException which occurred when the configuration custom injector failed to the configObject2 field,
  • Another SeedException which occurred because the missingKey configuration key was mandatory and is missing.
• The fix which is an advice on how to fix the root cause, i.e. the missing configuration key.
• The online information which is an URL pointing to a Web resource related to the root cause.
• The detailed stacktrace of the chained exceptions.