See: Description
| Interface | Description |
|---|---|
| Conversion.Converter<V,T> |
Converts a object of type V to a object of type T.
|
| Class | Description |
|---|---|
| BeanManager |
Bean Manager is used to create and remove bean instances, to find
beans by their name, and to query over beans.
|
| CacheManager<V> |
CacheManager is responsible for maintain cache entries of configurables.
|
| Conversion |
Conversion is responsible for converting values using registered converters.
|
| Conversion.Converter.ObjectToStringConverter |
This is the fallback string converter that simply does a toString on the
provided object.
|
| Conversion.Converter.StringToBooleanConverter | |
| Conversion.Converter.StringToEnumConverter |
This class can convert any enum to a string.
|
| Conversion.Converter.StringToNumberConverter |
This class can convert all number types such as BigDecimal, BigInteger, Byte, Double,
Float, Integer, Long, and Short.
|
| Conversion.Converter.StringToObjectConverter |
General purpose converter that is able to convert a String to an object if the
object have a suitable static valueof method or a single argument String constructor.
|
| Conversion.UniqueId | |
| NotificationManager | |
| NotificationManager.Observer | |
| SchemaManager |
SchemaManager is responsible for management and storage of schemas.
|
| Exception | Description |
|---|---|
| Conversion.ConversionException |
Each SPI deals with a very specific concern within the architecture and service providers are free to implement any of them. A key design goal for each SPI is to be decoupled from other SPI to enable providers to create modular implementations that are orthogonal and cohesive with respect to other SPI. This enables interaction between unforseen combinations of service providers.
Provider services are registered and automatically bound to core functionality when
the application is started/loaded. It is the responsibility of the core to glue/mediate communication
between different providers. The mechanism used is the standard ServiceLoader
at the moment, but other lookup/registrations (OSGi, CDI SPI extensions, JNDI etc) are envisioned.
A Test Compability Kit (TCK) is available for providers to verify that their implementation behaves correctly.
Each SPI have a default implementation that will be used if no other is provided.
The following SPIs are available at the moment:
BeanManagerSchemaManagerspi.ValidationManagerorg.deephacks.tools4j.support.conversion.ConverterThe following SPIs are envisioned in the future:
Copyright © 2013. All Rights Reserved.