Releases: adobe/aio-lib-java
aio-lib-java-1.0.6
Version 1.0.6
Bug fixes
- GH-142 fixing
aio-lib-osgi
: it now exportsio.openapitools.jackson.dataformat.hal.*
packages #143 (francoisledroff) - GH-138 fixing the createorUpdate provider service method #139 (francoisledroff)
aio-lib-java-1.0.2
- GH-136 test bug fix: void catching unwanted Conflict exception when testing createGetUpdateDelete events providers #137 (francoisledroff)
aio-lib-java-1.0.0
Version 1.0.0
New Features
-
aligning
aio-lib-java-events-mgmt
with the latest version of the IO Events APIs- with major update of IO Events registration sdk API (see
Breaking Changes
section below) - This version also introduces new features to::
-
update an existing registration
Optional<Registration> updateRegistration(String registrationId, RegistrationUpdateModel.Builder registrationUpdateModelBuilder)
-
List all registrations in a workspace
List<Registration> getRegistrationsForWorkspace()
-
Get all registrations for an org in a paginated response
Optional<RegistrationPaginatedModel> getAllRegistrationsForOrg(long page, long size)
-
- with major update of IO Events registration sdk API (see
-
The SDK also now uses a Jackson Object Mapper with support for JSON Hypertext Application Language (HAL) models. More details on HAL can be obtained here: https://stateless.group/hal_specification.html
Breaking Changes
Change in Registration API
This release updates the SDK to use the latest IO Events Registration API where registrations are now defined in the context of a project and workspace. More details on the APIs can be found here: https://developer.adobe.com/events/docs/api/#tag/Registrations
Old to new method mappings
The mappings from the old to the new methods are as follows:
Optional<Registration> createRegistration(RegistrationInputModel.Builder registrationInputModelBuilder) -> Optional<Registration> createRegistration(RegistrationCreateModel.Builder registrationCreateModelBuilder)
Full Changelog
- fix: address review comments #133 (sangeetha5491)
- Add support for Registration V2 API #132 (sangeetha5491)
- Add support for Registration V2 API #126 (sangeetha5491)
aio-lib-java-0.1.8
aio-lib-java-0.1.8
maven central released failed with a 500
from the nexus server,
we released it again as aio-lib-java-0.1.10
- GH-134 JDK-8193462 / JDK-8222091 workaround #135 (francoisledroff)
aio-lib-java-0.1.6
- GH-21 and GH-104 jdk8 support and move of the xdm IO Events Model here as a new module #130 (francoisledroff)
- Made the code compatible with java 8 #129 (pulguptaAdobe)
aio-lib-java-0.1.10
Version 0.1.10
no code change compared to aio-lib-java-0.1.8
but as the maven central released failed with a 500
from the nexus server, we released it again as aio-lib-java-0.1.10
Reminder: aio-lib-java-0.1.8
release changelog:
- GH-21 and GH-104 jdk8 support and move of the xdm IO Events Model here as a new module #130 (francoisledroff)
- Made the code compatible with java 8 #129 (pulguptaAdobe)
aio-lib-java-0.1.4
Version 0.1.4
No real sdk change with this release, we worked here on a more consistent set of integration tests : introducing a new test-only aio-lib-java-events-test
module
Changelog
- GH-127 moving the integration test with re-usable
testers
in a newaio-lib-java-events-test
module #128 (francoisledroff)
aio-lib-java-0.1.2
Version 0.1.2
Docs:
Here are our various documentation pointers:
- our JavaDocs
- our various modules github README.md files
- as for our
AEM
package please refer to our AIO Events - AEM Installation Guide
Changes:
This new major version brings integrations tests against all AIO Events API (see GH-114) as well better alignment with the latest AIO Events API changes. This allows the AEM package to allow to support the recommended CloudEvents event envelope delivery format (see GH-102)
The CloudEvents
event envelope looks like this :
{
"datacontenttype": "application/json",
"specversion": "1.0",
"source": "urn:uuid:'"${provider_id}"'",
"type": "'"${event_code}"'",
"id": "'"${your_event_id}"'",
"data": "your event json payload"
}'
when the legacy adobe_io
envelope looks like :
{
"event_id": "'"${your_event_id}"'",
"event": "your event json payload"
}'
Breaking change
This can be considered a breaking change: as with this change (GH-114), the default AEM AIO event delivery format is nowcloud_events_v1
and not adobe_io
anymore.
Upgrading existing AEM deployment may thus break former integration. However this can be easily overridden by the AEM admin/developer by updating the Adobe I/O Events' Provider Configuration
OSGI configuration and setting event.delivery.format
to adobe_io
.
For AEMaaCS you will need to add the a com.adobe.aio.aem.event.management.internal.EventProviderConfigSupplierImpl.cfg.json
osgi config file in your CloudManager git repo with the following setting:
{
"event.delivery.format": "adobe_io"
}
Changelog
- GH-102 mapping the new Provider Registration input model allowing to specify the
event_delivery_format
#120 (francoisledroff) - GH-114 adding unit and integration tests #117 (francoisledroff)
- GH-121 fixing the javadocs #122 (francoisledroff)
aio-lib-java-0.0.46
- GH-112 adding the Provider model's instanceId #113 (francoisledroff)
aio-lib-java-0.0.44
- GH-110 removing the deprecated Registration Type #111 (francoisledroff)
- Updates to Feign Header Processing #77 (bstopp)