Remove JAXB and XML, use GSON for JSON

This review converst apex-pdp to use GSON for JSON handling. In order to
preserve backward compatibility with the JAXB format of JSON, custom
handling of maps was required. Therefore, the policy-common
StandardCoder could not be used.

There are a lot of small changes, removing annotations from concepts and
tweaking of test data. However, this cleans up the code base so it is
worth doing.

Issue-ID: POLICY-1820
Change-Id: I213fa64f6d7f3f1df8d10f111d9fbedbe80f9fe0
Signed-off-by: liamfallon <liam.fallon@est.tech>
160 files changed
tree: 810e07f7d5cf270582264c40245372f597c713a2
  1. auth/
  2. context/
  3. core/
  4. examples/
  5. model/
  6. packages/
  7. plugins/
  8. releases/
  9. services/
  10. testsuites/
  11. tools/
  12. .gitignore
  13. .gitreview
  14. docker_build.sh
  15. docker_merge.sh
  16. docker_verify.sh
  17. INFO.yaml
  18. LICENSE.txt
  19. pom.xml
  20. README.md
  21. version.properties
README.md

Copyright (C) 2016-2018 Ericsson. All rights reserved. This file is licensed under the CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE Full license text at https://creativecommons.org/licenses/by/4.0/legalcode

This source repository contains the ONAP Policy APEX PDP Engine code. The settings file only needs to support the standard Maven repositories (e.g. central = http://repo1.maven.org/maven2/), and any proxy settings needed in your environment.

To build it using Maven 3, run: mvn clean install