How do I prevent JBoss from trying to deploy...

[gman4911]

files with specific extensions? I have a Java app that I've converted into an MBean. This app uses a configuration file with a .conf extension. If I put the file into my deploy directory with the app jar file, JBoss tries to deploy the .conf file and exceptions are generated. I cannot put the configuration file into the jar file because it needs to be modified from time to time. Any ideas on the best way to handle this? TIA.

[gman4911]

Nevermind. Found a solution. :-)

[starksm64]

Use the URLDeploymentScanner Filter attribute in the conf/jboss-service.xml descriptor:

 <!-- The Filter specifies a java.io.FileFilter for scanned
 directories. Any file not accepted by this filter will not be
 deployed. The org.jboss.deployment.scanner.DeploymentFilter
 rejects the following patterns:
 "#*", "%*", ",*", ".*", "_$*", "*#", "*$", "*%", "*.BAK",
 "*.old", "*.orig", "*.rej", "*.bak", "*,v", "*~", ".make.state",
 ".nse_depinfo", "CVS", "CVS.admin", "RCS", "RCSLOG", "SCCS",
 "TAGS", "core", "tags"
 -->
 <attribute name="Filter">org.jboss.deployment.scanner.DeploymentFilter</attribute>