[JBoss JIRA] (TEIIDDES-2346) Deployment and undepoyment of Dynamic VDBs is not yet supported
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2346?page=com.atlassian.jira.plu... ]
Matus Makovy updated TEIIDDES-2346:
-----------------------------------
Labels: release_notes verified_jbdsis-8.0.4.CR2 (was: )
> Deployment and undepoyment of Dynamic VDBs is not yet supported
> ---------------------------------------------------------------
>
> Key: TEIIDDES-2346
> URL: https://issues.jboss.org/browse/TEIIDDES-2346
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.6
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-8.0.4.CR2
> Fix For: 9.0.4, 9.2
>
> Attachments: deploy-dynamic-vdb-action.png, undeploy-dynamic-vdb-action.png
>
>
> Attempted to *undeploy* a dynamic VDB on my server and Designer threw an exception. (see below)
> We should detect dynamic VDBs in our local VDB cache and maybe display differently (decoration) as well as dissallow Undeploy VDB on selection, or call the approprieate method *undeployDynamicVdb()* instead.
> {code}
> org.teiid.adminapi.AdminProcessingException: {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014807: Management resource '[(\"deployment\" => \"DynamicProducts.vdb\")]' not found"}}
> at org.teiid.runtime.client.admin.v8.Admin8Factory$AdminImpl.execute(Admin8Factory.java:548)
> at org.teiid.runtime.client.admin.v8.Admin8Factory$AdminImpl.undeploy(Admin8Factory.java:782)
> at org.teiid.runtime.client.admin.v8.Admin8Spec.undeploy(Admin8Spec.java:73)
> at org.teiid.runtime.client.admin.ExecutionAdmin.undeployVdb(ExecutionAdmin.java:773)
> at org.teiid.designer.runtime.TeiidServer.undeployVdb(TeiidServer.java:669)
> at org.teiid.designer.runtime.ui.views.TeiidServerActionProvider$4.run(TeiidServerActionProvider.java:236)
> {code}
> 1) ExecutionAdmin.undeployVdb() calls: *adminSpec.undeploy(admin, appendVdbExtension(vdbName), vdb.getVersion())*, so this call is assuming a *.vdb* extension, which fails for dynamic VDBs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (TEIIDDES-2346) Deployment and undepoyment of Dynamic VDBs is not yet supported
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2346?page=com.atlassian.jira.plu... ]
Matus Makovy closed TEIIDDES-2346.
----------------------------------
> Deployment and undepoyment of Dynamic VDBs is not yet supported
> ---------------------------------------------------------------
>
> Key: TEIIDDES-2346
> URL: https://issues.jboss.org/browse/TEIIDDES-2346
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.6
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-8.0.4.CR2
> Fix For: 9.0.4, 9.2
>
> Attachments: deploy-dynamic-vdb-action.png, undeploy-dynamic-vdb-action.png
>
>
> Attempted to *undeploy* a dynamic VDB on my server and Designer threw an exception. (see below)
> We should detect dynamic VDBs in our local VDB cache and maybe display differently (decoration) as well as dissallow Undeploy VDB on selection, or call the approprieate method *undeployDynamicVdb()* instead.
> {code}
> org.teiid.adminapi.AdminProcessingException: {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014807: Management resource '[(\"deployment\" => \"DynamicProducts.vdb\")]' not found"}}
> at org.teiid.runtime.client.admin.v8.Admin8Factory$AdminImpl.execute(Admin8Factory.java:548)
> at org.teiid.runtime.client.admin.v8.Admin8Factory$AdminImpl.undeploy(Admin8Factory.java:782)
> at org.teiid.runtime.client.admin.v8.Admin8Spec.undeploy(Admin8Spec.java:73)
> at org.teiid.runtime.client.admin.ExecutionAdmin.undeployVdb(ExecutionAdmin.java:773)
> at org.teiid.designer.runtime.TeiidServer.undeployVdb(TeiidServer.java:669)
> at org.teiid.designer.runtime.ui.views.TeiidServerActionProvider$4.run(TeiidServerActionProvider.java:236)
> {code}
> 1) ExecutionAdmin.undeployVdb() calls: *adminSpec.undeploy(admin, appendVdbExtension(vdbName), vdb.getVersion())*, so this call is assuming a *.vdb* extension, which fails for dynamic VDBs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (TEIIDDES-2671) Dynamic VDB Editor is set as default for all XML files
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2671?page=com.atlassian.jira.plu... ]
Andrej Podhradsky closed TEIIDDES-2671.
---------------------------------------
Verified with JBDS 8.1.0.GA + JBDS-IS 8.0.4.CR2 (contains Teiid Designer 9.0.4.Final-v20151016-1346-B1206)
> Dynamic VDB Editor is set as default for all XML files
> ------------------------------------------------------
>
> Key: TEIIDDES-2671
> URL: https://issues.jboss.org/browse/TEIIDDES-2671
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors
> Affects Versions: 9.0.4
> Environment: JBDS 8.1.0.GA + JBDS-IS 8.0.4.CR1 (Teiid Designer 9.0.4.CR1-v20150917-2111-B1187 )
> Reporter: Andrej Podhradsky
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 9.0.4, 9.2
>
>
> Dynamic VDB Editor is set as default for all XML files. As a consequence opening an XML file fails due to
> org.eclipse.ui.PartInitException: File blueprint.xml is not a dynamic VDB
> In the example above the blueprint.xml should be opened by Camel Editor.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months