Interface BrailleTranslatorFactoryService
- 
- All Known Implementing Classes:
- DefaultBypassTranslatorFactoryService,- LiblouisBrailleTranslatorFactoryService,- SwedishBrailleTranslatorFactoryService
 
 public interface BrailleTranslatorFactoryServiceProvides an interface for a BrailleTranslatorFactory service. The purpose of this interface is to expose an implementation of a BrailleTranslatorFactory as a service. To comply with this interface, an implementation must be thread safe and address both the possibility that only a single instance is created and used throughout and that new instances are created as desired. 
- 
- 
Method SummaryAll Methods Instance Methods Abstract Methods Default Methods Modifier and Type Method Description Collection<TranslatorSpecification>listSpecifications()Returns a list of supported specifications.BrailleTranslatorFactorynewFactory()Creates a new braille translator factory.default voidsetCreatedWithSPI()Informs the implementation that it was discovered and instantiated using information collected from a file within theMETA-INF/servicesdirectory.booleansupportsSpecification(String locale, String mode)Returns true if the translator factory supports the given specification.
 
- 
- 
- 
Method Detail- 
supportsSpecificationboolean supportsSpecification(String locale, String mode) Returns true if the translator factory supports the given specification.- Parameters:
- locale- the translator locale
- mode- the translator grade, or null for uncontracted braille
- Returns:
- returns true if the translator factory supports the specification
 
 - 
listSpecificationsCollection<TranslatorSpecification> listSpecifications() Returns a list of supported specifications.- Returns:
- returns a list of specifications
 
 - 
newFactoryBrailleTranslatorFactory newFactory() Creates a new braille translator factory.- Returns:
- returns a new braille translator factory
 
 - 
setCreatedWithSPIdefault void setCreatedWithSPI() Informs the implementation that it was discovered and instantiated using information collected from a file within the META-INF/servicesdirectory. In other words, it was created using SPI (service provider interfaces).This information, in turn, enables the implementation to use the same mechanism to set dependencies as needed. If this information is not given, an implementation should avoid using SPIs and instead use declarative services for dependency injection as specified by OSGi. Note that this also applies to several newInstance() methods in the Java API. The class that created an instance with SPI must call this method before putting it to use. 
 
- 
 
-