I’ll defer to our deployment processing gurus re the mount question.
As an aside though, for this to work with the deployment-scanner subsystem we’ll need to
add some logic. Right now it would just ignore the file.
On Jan 11, 2017, at 8:34 AM, Ramesh Reddy <rareddy(a)redhat.com>
For Teiid project (http://teiid.org
), we typically deploy a .xml or .VDB (zip archive)
file to define a virtual database artifact. We are planning to deliver a feature where a
virtual database is written in DDL, for this we would like to deploy a file artifact like
I have written deployment processors for it, and added DEPLOYMENT_ROOT mounter to
recognize the deployment artifact etc, however during the deployment scanning, WildFly
always looks at anything other than ".xml" file as zip archive, or a exploded
zip archive, so that it can do VFS mount on that file. I would like to add this
".ddl" extension file exactly similar to ".xml" file. Is there any way
to achieve this?
wildfly-dev mailing list
Manager, Senior Principal Software Engineer
JBoss by Red Hat