Closed bstopp closed 2 years ago
yes we could do that, but that would add quite a bit of complexity, right ? I would advocate our user should use the one workspace per AEM and add APIs to it, if needed.
I mean that - Customer's AEM environment may want to connect to multiple AIO Workspaces/Projects. To publish or listen to events in different IMS orgs. With the current setup this isn't possible, as far as i can tell.
This is out of scope for this project. It will have to wait for AEM Eventing project.
I'm not sure I follow. Doesn't the aem
folder contain all of the AEM Eventing projects?
Yes, this library is how it works today. Tomorrow, once AEM Eventing project completes, it will replace the current approach.
Hm. Let me try re-framing the question:
How would, in either model, a single AEM instance (using the libraries contained here) authenticate to multiple AIO IMS Orgs?
Once AEM Eventing project is done, this library will not be used for integration.
Customers may want to integrate to multiple AIO Workspaces/Projects from AEM. The current implementation is limited to one.