here is me scanner mbean <!-- ==================================================================== --> <!-- Deployment Scanning --> <!-- ==================================================================== -->
<!-- An mbean for hot deployment/undeployment of archives. --> <!-- Uncomment (and comment/remove version below) to enable usage of the DeploymentCache <depends optional-attribute-name="Deployer">jboss.deployment:type=DeploymentCache --> <depends optional-attribute-name="Deployer">jboss.system:service=MainDeployer <!-- The URLComparator can be used to specify a deployment ordering for deployments found in a scanned directory. The class specified must be an implementation of java.util.Comparator, it must be able to compare two URL objects, and it must have a no-arg constructor. Two deployment comparators are shipped with JBoss: - org.jboss.deployment.DeploymentSorter Sorts by file extension, as follows: "sar", "service.xml", "rar", "jar", "war", "wsr", "ear", "zip", "*" - org.jboss.deployment.scanner.PrefixDeploymentSorter If the name portion of the url begins with 1 or more digits, those digits are converted to an int (ignoring leading zeroes), and files are deployed in that order. Files that do not start with any digits will be deployed first, and they will be sorted by extension as above with DeploymentSorter. --> org.jboss.deployment.DeploymentSorter <!-- org.jboss.deployment.scanner.PrefixDeploymentSorter --> <!-- 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" --> org.jboss.deployment.scanner.DeploymentFilter 5000 <!-- URLs are comma separated and resolve relative to the server home URL unless the given path is absolute. If the URL ends in "/" it is considered a collection and scanned, otherwise it is simply deployed; this follows RFC2518 convention and allows discrimination between collections and directories that are simply unpacked archives. URLs may be local (file:) or remote (http:). Scanning is supported for remote URLs but unpacked deployment units are not. Example URLs: deploy/ scans ${jboss.server.url}/deploy/, which is local or remote depending on the URL used to boot the server ${jboss.server.home}/deploy/ scans ${jboss.server.home)/deploy, which is always local file:/var/opt/myapp.ear deploy myapp.ear from a local location file:/var/opt/apps/ scans the specified directory http://www.test.com/netboot/myapp.ear deploys myapp.ear from a remote location http://www.test.com/netboot/apps/ scans the specified WebDAV location --> deploy/,d:\Siyaya\siyaya.ear <!-- Indicates if the scanner should recursively scan directories that contain no "." in their names. This can be used to group applications and services that must be deployed and that have the same logical function in the same directory i.e. deploy/JMX/ deploy/JMS/ ... --> True My sever is installed in c:\jboss3.2.3 my applicatftnio is in d:\siyaya directory View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3838138#3838138 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3838138 ------------------------------------------------------- This SF.Net email is sponsored by: GNOME Foundation Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event. GNOME Users and Developers European Conference, 28-30th June in Norway http://2004/guadec.org _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user