]
Barry LaFond edited comment on TEIIDDES-2346 at 10/14/15 11:34 AM:
-------------------------------------------------------------------
This was completed as part of TEIIDDES-2401
* Modeler Explorer and Server view contents show -vdb.xml files as VDBs and allow
deploy/undeploy (See attached screenshots)
was (Author: blafond):
This was completed as part of TEIIDDES-2401
* Modeler Explorer and Server view contents show -vdb.xml files as VDBs and allow
deploy/undeploy
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
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.