export org.apache.olingo.server.core.uri.parser in OSGI #25
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
|
JIRA OLINGO-1206 created to track this |
|
Can anyone from the Olingo team comment on this? |
|
Typically any exported classes have to correspond the API layers in the server/api module so that direct usage of the parser classes is discouraged. This is because to keep the Parser class API internal. Maybe we can create that layer then can have this. I can help with this, but we need to start with JIRA to understand the requirements. |
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.
Seems reasonable to export the org.apache.olingo.server.core.uri.parser package in OSGI. We use it in Apache Camel to properly retrieve the UriInfo.