commit | 9997d62c464a0e9a88eef56dbd6f01cede744688 | [log] [tgz] |
---|---|---|
author | Gilad Weinbach <gweinbach@yotpo.com> | Mon Jun 29 18:36:18 2020 +0300 |
committer | Gilad Weinbach <gweinbach@yotpo.com> | Mon Jun 29 18:36:18 2020 +0300 |
tree | 4dcf83930cdc1bac64e2008bbee040030db6745a | |
parent | 554ea6e6993ed0e268f7c23e5e7ecb332f3a72dc [diff] | |
parent | 7e5fc429b9bb2eb2b8f58b21263a35117d02d6e1 [diff] |
Merge branch 'master' into refresh-index * master: (132 commits) Update rest/src/main/java/org/apache/unomi/rest/RestServer.java Add customizer to make the try out URL work. UNOMI-356 Refactor REST API - A new RestServer class is responsible for creating a single JAX RS Server - Service beans must register with the OSGi service registry and setup the following property: osgi.jaxrs.resource=true (this property comes from OSGi R7 so that we can then migrate to OSGi R6 JAX RS whiteboard once we are on OSGI R7) - All JAX RS service beans are now register, not just the ones in the "rest" subproject - Swagger UI is integrated by default, although we might make it optional in the future. - Upgraded all OSGi JARs from version 4.3.1 to 6 - Remove usage of Blueprint in the "rest" subproject as it is no longer needed, it is replaced by OSGi DS annotations - Removal of Miredot Maven plugin to generate REST API documentation as it is replaced by Swagger/OpenAPI generation. UNOMI - 355 Add long value type (#170) UNOMI-352 Working on getting custom event types to work properly (not yet complete) UNOMI-352 Implement event type registry for GraphQL feat(org.apache.unomi.services.cfg) - add an environment variable for a configuration property UNOMI-346 Analyze/study event type registration system UNOMI-286 Event type definitions & set value type for property types This commit adds the following: - Event type definitions : possibility to define event types and retrieve them through the REST API. - Set value type for property types. Make it possible to define complex property types that may include other property types and therefore define complex object structures to be accepted as property types. Event types may also use this possibility to define their complete structure. fix(SetEventOccurenceCountAction) - fix future timestamp check Fix typo in documentation UNOMI-347 move totalCount to the connection level UNOMI-347 rename GraphQL fields UNOMI-347 improve query results UNOMI-341 - Refactor ServiceManager - Use vars to avoid repeated calls to bundleContext Reorganize documentation - Extract configuration into seperate section - Add new migration section - Done for master & 1.5.x documentation UNOMI-341 - Refactor ServiceManager More fixes on integrations tests, but not fully done yet. UNOMI-343 Fix integrations tests that are currently broken - Improve logging & add timeouts to Future gets in integration tests ...
Apache Unomi stores user profile information and is mostly used to provide a backend server for A/B testing and personalization. To do so it implements the currently under development OASIS Context Server specification.
The source code is available under the Apache License V2
You can find all the updated documentation, including building and deployment instructions, on the Apache Unomi web site.