[
https://jira.jboss.org/browse/TEIID-1219?page=com.atlassian.jira.plugin.s...
]
Ramesh Reddy resolved TEIID-1219.
---------------------------------
Assignee: Ramesh Reddy (was: Steve Hawkins)
Fix Version/s: 7.1.1
Resolution: Cannot Reproduce Bug
The cause of this was due to the invalid index file generated in the Designer, not
anything to do with the Teiid merge functionality.
Metadata for XML Document models not being showing up after Admin API
mergeVDB() call.
--------------------------------------------------------------------------------------
Key: TEIID-1219
URL:
https://jira.jboss.org/browse/TEIID-1219
Project: Teiid
Issue Type: Bug
Affects Versions: 7.1
Reporter: Barry LaFond
Assignee: Ramesh Reddy
Fix For: 7.1.1
Attachments: TestPartsWSPreview.zip
Testing the Preview Data feature in pre-7.1 Teiid Designer with 7.1 Teiid has resulted in
errors previewing Web Service models because the XML Document model metadata isn't
being being property merged and exposed.
The logged console exception is:
[PROCESSOR] Processing exception 'Group does not exist:
PartsOracle_Output_View.PARTS_OutputView' for request 48+ANjgClxMi.0. Exception type
org.teiid.api.exception.query.QueryPlannerException thrown from
org.teiid.query.resolver.util.ResolverUtil.handleUnresolvedGroup(ResolverUtil.java:852).
Enable more detailed logging to see the entire stacktrace.
Looking through Designer's DTP connection in data source explorer, it's appears
that the XML Doc model isn't part of the VDB, so I'm assuming the merge
doesn't property handle XML.
NOTE: that creating a real VDB from the SAME model set in Designer, then deploying, DOES
show the model. Accessing the Metadata from Designer's JDBC Import connection shows
that the XML Document nodes are there.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira