This topic applies to WebSphere Application Server Liberty V8.5.5.9 and earlier. For the latest Liberty topics, see the WebSphere Application Server Liberty documentation.
Liberty SPI utilities
Liberty provides service programming interfaces (SPI) to complete various tasks.
Subtopics
- Resource location symbols
Liberty user configuration is made more portable through the use of variables that represent symbolic locations. Use of these variables helps to prevent the coding of absolute paths that would make the user configuration brittle and less portable. Feature code that receives configuration properties might have to deal with values that contain such variables. - Monitoring local files for changes
Liberty has highly dynamic behavior, responding to changes in configuration, applications and other resources. Much of this dynamic behavior is based on monitoring of the local file system for changes. The service that performs this monitoring is available to all Liberty features through the FileMonitor SPI. The file monitor service is provided by the Liberty kernel, so you do not have to specify a feature in your server.xml file to make it available. - Configuring tracing and logging for features in the Liberty profile
You can use the tracing and logging mechanism of the Liberty profile for Liberty features. The logging service is part of the Liberty kernel so you do not have to specify a feature in your server.xml file to use it. Adding web services global handlers
Components that need to register web services handlers to all the web services end points must implement the Handler interface and register that implementation in the service registry.Exposing REST endpoints within Liberty
You can use the REST Handler framework in the Liberty SPI to expose new REST endpoints.
Parent topic: Developing a Liberty feature for Liberty


http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-libcore-mp&topic=rwlp_spi_utils
File name: rwlp_spi_utils.html