you mean how to tell it to use my-configuration-file.xml when launching ?
Goto the Runtime you created (you can access it from the server editor) and select the my-configuration-file.xml instead of standalone.xml.
Thanks. So, it turns out that the error I get is due to the following problem ( quote from github thread)
" It seems that there are some problems with the Wildfly adapter, as the __TransformerFactory redirector doesn't redirect to the TransformerFactory of the Wildfly xalan module (inside modules/system/layers/base/org/apache/xalan) as it should, but to the internal JDK TransformerFactory. This problem doesn't exists when running the very same code within Eclipse using the JBoss7 Adapter, therefore I'm pretty sure it's some issue in the Wildfly Adapter (or Wildfly itself)."
See this thread for more details:
We were experiencing this same behavior when running our server in domain mode. Transformations that worked fine in standalone mode were breaking in domain mode.
The solution for us was to include a jboss-deployment-structure.xml file that explicitly imported the xalan module:
<?xml version="1.0" encoding="UTF-8"?> <jboss-deployment-structure> <deployment> <dependencies> <module name="org.apache.xalan" services="import" /> <module name="org.apache.xerces" services="import" /> </dependencies> </deployment> </jboss-deployment-structure>
Very interesting, thanks for sharing!
A new feature to be released in our upcoming GA (also available in CR1) is that projects that declare a jboss-modules dependency in their manifest.mf will have those jars added to the classpath. (See Manifest module information - JBoss Modules - Project Documentation Editor). We don't currently parse the jboss-deployment-structure.xml to add jars to the classpath, but, if you think we should, you could open a jira / enhancement request for our tools to also take that file into account when generating a project's classpath.