sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Desruisseaux (Jira)" <>
Subject [jira] [Commented] (SIS-86) Refactor @Configuration annotation into a real Configuration class
Date Mon, 09 Sep 2019 12:46:00 GMT


Martin Desruisseaux commented on SIS-86:

A partial fix has been done in SIS 1.0 with the addition of {{org.apache.sis.setup.Configuration}}
class. Current version contains only a method for configuring the "SpatialMetadata" database
source. Future version should handle the other settings like loggings, but we want to review
our logging strategy in light of Java 9 {{System.Logger}} first.

> Refactor @Configuration annotation into a real Configuration class
> ------------------------------------------------------------------
>                 Key: SIS-86
>                 URL:
>             Project: Spatial Information Systems
>          Issue Type: Improvement
>          Components: Utilities
>            Reporter: Martin Desruisseaux
>            Assignee: Martin Desruisseaux
>            Priority: Major
>             Fix For: 1.1
> The {{@Configuration}} annotation is currently for identifying various static method
having a system-wide effect. We may consider regrouping all such methods in a central place,
maybe in a new {{org.apache.sis.setup}} package. We could provide pre-defined configuration
profiles, including:
> * {{STRICT}} - maximal level of strictness (duplicated values cause parsing errors, Bursa-Wolf
parameters mandatory for datum shifts, _etc._).
> * {{DEFAULT}} - the default setting as a compromise between {{STRICT}} and {{LENIENT}}:
duplicated values just produce warnings, but datum shifts still require Bursa-Wolf parameters.
> * {{LENIENT}} - still working even if the accuracy may be compromise (e.g. apply datum
shifts even in the absence of Bursa-Wolf parameters).

This message was sent by Atlassian Jira

View raw message