[
https://issues.jboss.org/browse/TEIID-3912?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3912:
---------------------------------------
What is the benefit in the separation?
Also I think the client has different dependency structure on the
Olingo
The translator has a org/apache/olingo/client/common module that is identical to the
server org/apache/olingo/common module - it even in the module.xml declares itself as the
org.apache.olingo.common module. It seems like the duplicate module in the translator
could be removed.
Beyond that the odata client and server modules are different, but that would remain even
if translator referenced the server odata module.
Centralize type handling for odata4
-----------------------------------
Key: TEIID-3912
URL:
https://issues.jboss.org/browse/TEIID-3912
Project: Teiid
Issue Type: Quality Risk
Components: OData
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 9.0
There is similar type handling logic in both the server odata4 and translator odata4
modules. This should be combined to remove duplication.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)