[
https://issues.jboss.org/browse/TEIID-2057?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2057:
---------------------------------------
This issue goes beyond just Mark's usage. All of the VDBService methods that update
the vdb do so based upon the runtime state, which can add ephemeral errors and omit the
ddl. I think we also need to correct that logic to do a full parse/save of the metadata
state.
Problem with dynamic VDB re-deploy when it contains a Virtual Model
-------------------------------------------------------------------
Key: TEIID-2057
URL:
https://issues.jboss.org/browse/TEIID-2057
Project: Teiid
Issue Type: Bug
Components: AdminApi
Affects Versions: 8.0
Reporter: Mark Drilling
Assignee: Ramesh Reddy
I am using the AdminAPI to add a View Model to a dynamic VDB. The initial deployment
succeeds - the VDB deploys and i can query the View.
However, then I retrieve the VDB via the Admin API. In debug, I can see on the view
model - that the schemaText field is now null. If I attempt to make other changes and
re-deploy, the re-deploy fails - the parser chokes on the null schemaText
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira