How are you marking them "deployable"?
I've seen this issue arise because the VDB was deployed either thru Teiid Designer or admin console. In this case, the VDB will be deployed in the standalone/data/contents folder somewhere (cryptic name). And if you then try to deploy the VDB by copying it to the deployments folder, before you un-deploy it, you will see this issue.
That is to be expected. Before you can deploy an artifact into JBoss EAP, you need to make sure there is no other SAME named deployment that already exists. Automatically overwriting the previously deployed artifact is not a desirable outcome. So, if one uses consistent deployment strategies this issue can be avoided.
But sometimes, people don't realize they will run into this issue when they copy the VDB to the deployments directory (for which this isn't replacing an existing file). I've found that some believe that the EAP discovery will handle both cases as if there is one deployment, regardless of how it is deployed.
1 of 1 people found this helpful
It is understandable that if once the VDB is deployed and next time if we try to deploy the same VDB again it should warn us and allow to take the respective action whether to undeploy old and redeploy new OR abort the current operation.
OR the error message could have been more clear as explained by Ramesh.
I am running the EAP/JBDV in JBDS and I will keep unmarking the VDBs for deployment before I deploy the new versions.
However, I am waiting for my another important question from morning is given in another thread.
I have a requirement to insert data into related multiple tables in the database through a single VDB that virtualizes multiple tables.
Any link to follow, I am asking this because there are not many links , many of which is not taking me till destination solution.
Or any easy steps here, would help.
For now, all the tables are in single database, Going forward it might be disparate backend systems too.