All Packages from org.jboss.deployment.cache.* to org.jboss.deployment.scanner.*

Home >> All >> org >> jboss >> [ deployment Javadoc ]

•

• org.jboss.deployment: Javadoc index of package org.jboss.deployment.

Package Samples:

• org.jboss.deployment.cache: Core deployment framework and services.
• org.jboss.deployment.scanner: Core deployment framework and services.

Classes:

• PrefixDeploymentSorter: This class is a comparator to sort deployment URLs based on the existence of a numeric prefix. The name portion of the URL is evaluated for any leading digits. If they exist, then they will define a numerical ordering for this comparator. If there is no leading digits, then they will compare as less than any name with leading digits. In the case of a tie, the DeploymentSorter is consulted (@see org.jboss.deployment.DeploymentSorter). Ex.these names are in ascending order: test.sar, crap.ear, 001test.jar, 5test.rar, 5foo.jar, 120bar.jar
• SubDeployerSupport: An abstract SubDeployer . Provides registration with MainDeployer as well as implementations of init, create, start, stop and destroy that generate JMX notifications on completion of the method.
• JARDeployer: This deployer exists to prevent deployment of packages whose deployers are not yet deployed. It will accept only jar/zip format files or directories that don't have a META-INF directory, or if they do, don't have any .xml files there. It assumes any package with a META-INF/*.xml file needs a specialized deployer. JARDeployerMBean.java is generated by XDoclet.
• AbstractDeploymentScanner: An abstract support class for implementing a deployment scanner. Provides the implementation of period-based scanning, as well as Deployer integration. Sub-classes only need to implement DeploymentScanner.scan() 55 .
• DeploymentFilter: A simple filter to for the URLDeploymentScanner. Three arrays are maintained for checking: a prefix, suffix, and match array. If the filename starts with any of the prefixes, ends with any of the suffixes, or exactly matches any of the matches, then the accepts method will return false.
• JBossEntityResolver: Local entity resolver to handle standard J2EE DTDs as well as JBoss specific DTDs. Function boolean hadDTD() is here to avoid validation errors in descriptors that do not have a DOCTYPE declaration.
• FileDeploymentStore: A local file based DeploymentStore .
• DeploymentCache: A Deployer-like service which intercepts deploy/undeploy calls to MainDeployer and provides local caching of target URLs using local disk.
• DeploymentScanner: Provides the basic interface for a deployment scanner. A deployment scanner scans for new, removed or changed deployments.
• SubDeployer: The common interface for sub-deployer components which perform the actual deployment services for application components.
• DeploymentInfo: Service Deployment Info . Every deployment (even the J2EE ones) should be seen at some point as Service Deployment info
• ClasspathExtension: A service that allows one to add an arbitrary URL to a named LoaderRepository. Created: Sun Jun 30 13:17:22 2002
• DeploymentInfoComparator: This comparator takes a delegate comparator that can compare URLs, and applies that to DeploymentInfo objects
• Deployer: The interface which a deployer must implement. Clients should use the MainDeployer to deploy URLs.
• MainDeployer: The main/primary component for deployment. MainDeployerMBean is generated by xdoclet.
• URLDeploymentScanner: A URL-based deployment scanner. Supports local directory scanning for file-based urls.
• ClientDeployer: An XMBean resource implementation of a deployer for j2ee application client jars
• DeploymentStore: Provides the interface for abstracting the actual storage of cached deployments.
• NetBootFile: Represents a file/directory representation read from a distant HTTP server
• DeploymentException: Thrown by a deployer if an application component could not be deployed.

Home | Contact Us | Privacy Policy | Terms of Service