Interface AppConfiguration
- All Known Implementing Classes:
SimpleAppConfiguration
- Since:
- 1.35
-
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final StringService URL name for a user-facing "dashboard" specific to a single SolarNode.static final StringService URL name for a user-facing "dashboard" specific to a single SolarNode.static final StringService URL name for the SolarQuery app.static final StringService URL name for the SolarUser app. -
Method Summary
Modifier and TypeMethodDescriptionGet a mapping of named service URLs.
-
Field Details
-
SOLARUSER_SERVICE_NAME
Service URL name for the SolarUser app.- See Also:
-
SOLARQUERY_SERVICE_NAME
Service URL name for the SolarQuery app.- See Also:
-
SOALRNODE_DASHBAORD_SERVICE_NAME
Service URL name for a user-facing "dashboard" specific to a single SolarNode.This URL can reasonably be expected to support a
nodeIdvariable.- See Also:
-
SOLARNDOE_DATAVIEW_SERVICE_NAME
Service URL name for a user-facing "dashboard" specific to a single SolarNode.This URL can reasonably be expected to support a
nodeIdvariable.- See Also:
-
-
Method Details
-
getServiceUrls
Get a mapping of named service URLs.The keys of the returned maps represent logical names for the associated URL values. The keys will be application-dependent, and should include values for well-defined application services. For example a URL to the application terms of service might be included under a key tos.
URL values are permitted to contain variables in the form
{var}that consumers of the URLs can replace with appropriate values. The variable names must be named so their intended use is obvious, for examplenodeIdfor a SolarNode ID.Some common service URL names are defined as constants on this interface. Implementations are recommended to use these keys when it makes sense, and to add any other values needed by the application.
- Returns:
- named service URLs, never null
-