[
https://issues.jboss.org/browse/TEIIDDES-3163?page=com.atlassian.jira.plu...
]
Barry LaFond resolved TEIIDDES-3163.
------------------------------------
Resolution: Done
master:
https://github.com/Teiid-Designer/teiid-designer/commit/01046321bd21dbd32...
* main problem was that the DynamicVdb class needed a destination file defined, so in the
*update* use-case, the existing file was used.
* added notion of a /tmp/-vdb.xml file location that is used to generate the vdb.xml. At
end of process user can cancel or *overwrite*. In both cases the temp -vdb.xml is
deleted.
Translator override properties can not be updated after re-generating
a dynamic vdb
-----------------------------------------------------------------------------------
Key: TEIIDDES-3163
URL:
https://issues.jboss.org/browse/TEIIDDES-3163
Project: Teiid Designer
Issue Type: Bug
Components: Dynamic VDBs
Affects Versions: 11.1.1
Environment: Devstudio 11.1.0 CR1 (Teiid Desinger 11.1.1)
Reporter: Hiroki Daicho
Assignee: Barry LaFond
Fix For: 11.1.2
Attachments: reproducer_project.zip
If dynamic vdb has already generated, Translator override properties can not be modified
by regenerate dynamic vdb.
1. Add Translator override property to vdb (testvdb.vdb). e.g. prop1 -> 100
2. generate dynamic vdb (testvdb-vdb.xml).
{code}
<property name="prop1" value="100"/>
{code}
3. Modify the propery in vdb (testvdb.vdb). e.g. prop1 -> 199
4. generate dynamic vdb (testvdb-vdb.xml).
5. the property is not updated to 199 in the dynamic vdb xml.
{code}
<property name="prop1" value="100"/>
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)