> but I guess some other user noob like me could be fooled by a subtle rule like that, because teiid seems to "recognize" the file: there is no error or warning of any kind... the system gives you no clue that the only problem is in the xml file name... could this be better handled in teiid or is a eap issue?
That's a good usability question. At the core EAP doesn't care. It's generic deployment method allows you to deploy a file and then it's up to the various deployers installed to determine what to do with the contents. The admin api just wraps the generic deployment method and does not presume you are deploying a vdb zip or xml. Our deployment logic is only looking to check the file extension so it doesn't have to guess at and parse every deployed file to see if it's a vdb. We could add some logic for a specific vdb deployment routine in the admin api that ensures the teiid naming conventions are used, but otherwise there's not much we should do.
The Admin API "deploy" method is generic purpose deploy for all the artifacts, currently you can deploy any of JAR, RAR or WAR or any other deploy able artifacts. Teiid Designer uses this to deploy the JDBC JAR files and RAR files. That is reason the checking for vdb name pattern is not added to the method. We could certainly log an warning if that is XML file I guess.
In previous versions of Teiid <= 7.x, it had explicit methods like "deployVDB".