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

Add support for camel-olingo2 #1281

Closed
jamesnetherton opened this issue Aug 9, 2016 · 4 comments
Closed

Add support for camel-olingo2 #1281

jamesnetherton opened this issue Aug 9, 2016 · 4 comments
Assignees
Labels
Milestone

Comments

@jamesnetherton
Copy link
Collaborator

http://camel.apache.org/olingo2.html

@jamesnetherton jamesnetherton added this to the 4.3.0 milestone Aug 9, 2016
@jamesnetherton jamesnetherton self-assigned this Aug 17, 2016
@jamesnetherton
Copy link
Collaborator Author

Partially blocked on this: https://issues.apache.org/jira/browse/CAMEL-10260

We could add the missing dependency to WFC to temporarily work around the problem, but maybe it's better / easier to wait for the 2.18 release.

jamesnetherton added a commit to jamesnetherton/wildfly-camel that referenced this issue Aug 22, 2016
@jamesnetherton
Copy link
Collaborator Author

Turns out this is more complicated than I thought:

https://issues.apache.org/jira/browse/OLINGO-894

https://issues.apache.org/jira/browse/OLINGO-899

@tdiesler tdiesler removed the blocked label Sep 29, 2016
@jamesnetherton
Copy link
Collaborator Author

Thinking about this some more, the above mentioned issues are only a problem for Olingo servers. Since the camel component is essentially an Olingo client, the problem only occurs for testing purposes where we need some sample datasource to test against.

@jamesnetherton
Copy link
Collaborator Author

Done

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

No branches or pull requests

2 participants