Web Service Shell 2 Released
Web Service Shell version 2 is a major update that allows the addition of multiple endpoints, more flexibility in service names and the ability to proxy more than one file.
Web Service Shell version 2 is a major update that adds the capability to define multiple endpoints and adds more flexibility in naming services. Incremental improvements include adding a new logging method and more consistent error messages. The core concept of providing a web service that can be configured via simple properties files to utilize external resources remains the same.
- Configure multiple, arbitrary endpoints. Previously, only one endpoint, “query” was provided. Now it is possible to define multiple endpoints and define endpoint names by configuration. Each endpoint may have its own list of supported media types and may include static or dynamic HTTP response header adjustments.
- The web service naming convention (and URL path) has been generalized to support simple or multi-level naming conventions while still supporting the original, three level FDSN standard of “/fdsnws/<service>/<majorversion>/“
- Endpoints that return content proxied from other resources (e.g. files or other endpoints) are supported. In version 1, only one endpoint, “application.wadl” was available to deliver XML content. In version 2, multiple proxy endpoints may be configured, along with respective media types. Also, endpoint “application.wadl” may be removed if it is not needed.
- A new loggingMethod to support RabbitMQ has been added.
- Time values in usage log messages are standardized to UTC time so that time is not affected by other system settings.
- Version 2 has improved consistency for error messages
- A few unused parameters are removed
Changes needed for upgrading a service from version 1 to version 2
- Configuration file naming conventions have changed slightly to support generalized service naming capability.
- Additional syntax is used to define endpoints plus their respective parameters see WSS 2.2 Documentation at https://seiscode.iris.washington.edu/projects/webserviceshell/wiki/Web_Service_Shell for details on naming conventions and configuration parameter changes.