You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 11, 2024. It is now read-only.
switch from Guice modules to iceland providers, might have to reorganize the source code so that functionality is more closely modelled after the interfaces and operations
change license of OSS (back to) GPL (because of SOS dependencies)
re-check licenses of depedencies
switch to latest Solr and fix compile time errors
move concrete logging dependencies and configurations to webapp module
SensorSearch operation of SIR (high), if SIR then also do DescribeSensor
JSON binding (high)
Autocomplete endpoint with document index database (high)
UI (medium)
Harvesting (medium)
re-add document database (becomes relevant only with external harvested SOS, or with millions of sensors)
concept of "internal" and "external" sensors to the document database (e.g. listen to SOS event bus and delete internal sensors on DeleteSensor@SOS)
Validation endpoints (low)
deactivate transactional interface of SIR (throw exceptions)
deactivate status operations of SIR (throw exceptions)
optional: JSON binding and autocomplete works with Angular UI
switch from XMLBeans to JAXB
Notes about modules
arsearch > not needed anymore, remove
common > only home dir config mechanism > replaced by iceland configuration, remove??
it > fix first! remove JS-harvesting stuff, ignore tests
misc > keep, of course, will use SOS code so change the license to GPL
service > actual business logic, keep all classes but focus on OpenSearch + SOS DAOs
sir-common >
sir-it > SIR integration tests
sir-json > keep as needed for JSON encoding
sor-common > Sensor Observable Registry > drop it.
sor > Sensor Observable Registry > drop it.
website > keep as independent search client / landing page, remove some unneeded code (SOR, all the Java classes, JSPs, and login-related stuff, remove all "under development", ..), test update Angular
remove Swagger
Adjustments for SOS-integration
extend data model to include "internal" and "external" sensor descriptions
internal = in SOS database using SOS DAOs, need some internal harvesting for search DB
external = in Solr using OSS DAOs, or just use Lucene internally without Solr?
fromt the outside (to a client) there is no distinguishment between the
check Esri Geoportal Server how they can automatically create a Solr instance at installation time - or do they just use Lucene?
switch configuration to use iceland's Settings API
add internal harvesting (e.g. add internal sensors to the search database)
Things to consider/steps to be taken:
Switch to Iceland
oss-icelandwebapp-bundle, see comment below by @autermannNotes about modules
arsearch> not needed anymore, removecommon> only home dir config mechanism > replaced by iceland configuration, remove??it> fix first! remove JS-harvesting stuff, ignore testsmisc> keep, of course, will use SOS code so change the license to GPLservice> actual business logic, keep all classes but focus on OpenSearch + SOS DAOssir-common>sir-it> SIR integration testssir-json> keep as needed for JSON encodingsor-common> Sensor Observable Registry > drop it.sor> Sensor Observable Registry > drop it.website> keep as independent search client / landing page, remove some unneeded code (SOR, all the Java classes, JSPs, and login-related stuff, remove all "under development", ..), test update AngularAdjustments for SOS-integration