[teiid-designer-issues] [JBoss JIRA] (TEIIDDES-3151) OData4 specific MXD is not found
[
https://issues.jboss.org/browse/TEIIDDES-3151?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-3151:
----------------------------------------
attached a sample file: my_custom_med.mxd
Can be used to verify:
* register/unregister a MED
* Apply the custom MED to a source model
* Export source model DDL to verify it adds SET NAMESPACE ..... statement and
"my_custom_med:xxxxx" properties in OPTIONS() statement
* Add source model to VDB and verify Save As XML adds same DDL as above
* Add VDB to new project and Generate VDB Archive and Models and verify that source model
contains custom MED and same property values.
OData4 specific MXD is not found
---------------------------------
Key: TEIIDDES-3151
URL: https://issues.jboss.org/browse/TEIIDDES-3151
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 11.1
Reporter: Ramesh Reddy
Assignee: Barry LaFond
Priority: Blocker
Fix For: 11.1.1
Attachments: my_custom_med.mxd, odata4.mxd
While working on the case I found that there is no "odata4" specific MXD nor
the current odata MXD is updated with newer properties for the V4. Since server uses the
same namespace the current one needs to be updated.
A sample MXD (minus the namespace) is attached.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)