AEM as a Cloud Service: components and services request in dev.tools are not working #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- instead of bundle reference, bundle ID is passed. - constant naming and value correspondent adjustment
|
thanks! - looks good |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed fix description:
When the bundle tracker (JaxRsBundleTracker) registers ComponentFactory (i.e. ServletContainerBridge), there is
a dictionary created and a reference to the bundle is placed into this dictionary. This produces the error in AEM cloud manager.
This reference can be changed to bundle ID and some correspondent adjustments need to be taken.
Fixes #5