-
1. Re: Two properties files for two instance of same application
nickarls Jun 7, 2016 12:41 AM (in response to armahdi)If you have Test.war and Prod.war, won't you still have to set the context root in jboss-web.xml? And if your config file is on the root classpath of the WARs, each one would pick up their own one, right? You can have multiple deployment-scanners in WF but personally, I would just go the simple way with separate maven profiles, properties and filtering for the XML- and properties files...
-
2. Re: Two properties files for two instance of same application
armahdi Jun 7, 2016 1:16 AM (in response to nickarls)Well the property files are not in root of the wars, As per convention in wildfly, you supply properties files in module directory and supply that module name in jboss-deployment-structure.xml which is standard per application and does not change from test to prod. These property files remain pretty much the same over different version of the same application in the same environment test or prod. So they are externalized in modules and they are picked up by wildfly and loaded whenever they are mentioned in a jboss-deployment-structure.xml.
-
3. Re: Two properties files for two instance of same application
nickarls Jun 7, 2016 1:38 AM (in response to armahdi)Hmm, well in that case two slots in a module might be an approach. Of course the jboss-deployment-structure.xml would still have to be filtered. You can have multiple module roots in WF, too, I think but they are probably per instance.