Skip to content

export org.apache.olingo.server.core.uri.parser in OSGI#25

Open
johnpoth wants to merge 1 commit intoapache:masterfrom
johnpoth:odata4-osgi
Open

export org.apache.olingo.server.core.uri.parser in OSGI#25
johnpoth wants to merge 1 commit intoapache:masterfrom
johnpoth:odata4-osgi

Conversation

@johnpoth
Copy link
Copy Markdown
Member

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.

@johnpoth
Copy link
Copy Markdown
Member Author

JIRA OLINGO-1206 created to track this

@davsclaus
Copy link
Copy Markdown

Can anyone from the Olingo team comment on this?

@rareddy
Copy link
Copy Markdown
Contributor

rareddy commented Feb 27, 2018

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants