Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#545 closed enhancement (fixed)

List of SECORE hosts in petascope.properties

Reported by: pcampalani Owned by: pcampalani
Priority: major Milestone: 9.0
Component: petascope Version: development
Keywords: secore fallback Cc:
Complexity: Medium

Description

Petascope is currently configurable to have an ordered list of SECORE resolvers to support its coverage metadata understanding, to fallback in case one or more hosts are in outage.

This feature was initiated changeset:te5758d4 (feature_PetascopeSecore branch), but the fallback behaviour is applied only when the configured SECORE hosts are needed, that is when compounding single CRSs and when testing equalities on two URIs.

Ideally, the configured host should be used as well when fetching a CRS definition: the resolver host in this case is hardwired in the CRS URI, and can or cannot be pointing to one of the configured resolvers (if a new URI is added in ps9_crs pointing to resolver ACME, there's no harm).

Change History (2)

comment:1 Changed 3 years ago by pcampalani

  • Resolution set to fixed
  • Status changed from new to closed

I forgot I already implemented that fallback behaviour also when fetching CRS definitions:

public static CrsDefinition getGmlDefinition(String givenCrsUri) throws PetascopeException, SecoreException {
...
    for (String resolverUri : ConfigManager.SECORE_URLS) {
                lastUri = CrsUri(resolverUri,
                        CrsUri.getAuthority(givenCrsUri),
                        CrsUri.getVersion(givenCrsUri),
                        CrsUri.getCode(givenCrsUri));
                crsUris.add(lastUri);
        }

        // Start parsing
        for (String crsUri : crsUris) {
...

comment:2 Changed 3 years ago by pcampalani

Order of the resolvers' list is also kept (changeset:d08b7dd).

Note: See TracTickets for help on using tickets.