Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GH-52 Add com.adobe.aio.aem.event.management a Java OSGI bundle hosting OSGI Components wrapping aio-lib-java-events-mgmt #53

Merged
merged 1 commit into from
Mar 18, 2022

Conversation

francoisledroff
Copy link
Collaborator

No description provided.

@francoisledroff francoisledroff merged commit ea8e6ab into adobe:main Mar 18, 2022
* AEM has to register against Adobe I/O Events API management, in order to be assigned a
* providerId, and then to be able to register its event metadata
*/
public interface EventProviderRegistrationService extends StatusSupplier {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@francoisledroff Shouldn't the AEM OSGI bundle transparently map the same interface as our core java SDK?

For example, in this interface we cherry-picked only these two methods getRegisteredProvider and registerEventMetadata. Any reason for not implementing ALL the methods that we have in ProviderService and RegistrationService in two separate OSGI interfaces?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All AEM interfaces have a subset of methods. For instance, in EventPublishService also, we have one method out of many present in PublishService

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants