| Home >> All >> org >> apache >> cactus >> integration |
| • | org.apache.cactus.integration.ant.* (82) | • | org.apache.cactus.integration.maven.* (9) |
Package Samples:
• org.apache.cactus.integration.ant.deployment.webapp: Contains classes that support deployment aspects like parsing deployment descriptors and extracting resources from deployment archives.
• org.apache.cactus.integration.ant.container.weblogic: Contains classes and interfaces that constitute the support for container startup and shutdown in the Ant integration.
• org.apache.cactus.integration.ant.util: Contains the tasks and types provided for integration of Cactus with Ant.
• org.apache.cactus.integration.maven.test
• org.apache.cactus.integration.maven
• org.apache.cactus.integration.ant.container.enhydra
• org.apache.cactus.integration.ant.container.jboss
• org.apache.cactus.integration.ant.container.orion
• org.apache.cactus.integration.ant.container.resin
• org.apache.cactus.integration.ant.container.tomcat
• org.apache.cactus.integration.ant.container
• org.apache.cactus.integration.ant.deployment.application
• org.apache.cactus.integration.ant.deployment
• org.apache.cactus.integration.ant
Classes:
• RunServerTestsTask: Task to automate running in-container unit test. It has the following syntax when used in Ant : <runservertests testURL="&t;url>" starttarget="<start target name>" stoptarget="<stop target name>" testtarget="<test target name>"/> where <url> is the URL that is used by this task to ensure that the server is running. Indeed, the algorithm is as follow : Checks if server is running by trying to open an HTTP connection to the URL, If it fails, call the start target and loop until the HTTP connection the URL can be established, Call the test target. This target is supposed ...
• AntLog: Support class that lets classes log to Ant using the Commons Logging API. This is not intended to be a general solution, rather as a thin separation layer to not have to pass around full-blown Ant Project , Target or Task objects just to enable logging. Note that as there is no log level in Commons-Logging that corresponds to Ant's VERBOSE level (the level between INFO and DEBUG ), the TRACE level of Commons-Logging gets mapped to VERBOSE , which is probably inappropriate for components that do not know they are using the AntLog class.
• CactusScanner: Process org.apache.tools.ant.types.FileSet and extracts classes that are Cactus tests. As a Cactus test can be a simple JUnit test case wrapped in a Cactus suite, it is very difficult to find out only Cactus tests. Thus, in this version, we are only finding JUnit tests. A class is considered to be a JUnit Test Case if: It extends junit.framework.TestCase It is not abstract It has at least one method that starts with "test", returns void and takes no parameters
• TestCactifyWarTask: Unit tests for CactifyWarTask . TODO: test whether all files contained by the source WAR are also added to the cactified WAR TODO: test whether the mergewebxml is actually merged into the cactified web.xml
• CactusScannerTag: Cactus Jelly Tag that scans Ant FileSets and return a list of qualified class name that are Cactus TestCases (i.e. ServletTestCase, JspTestCase or FilterTestCase) or subclasses of Cactus TestCases. Note: This is useful when used with the <junit> Ant task for example, in order to find out the list of tests to execute.
• EarParser: Parse an EAR descriptor to extract meaninful information for Cactus, the results being stored in a EarDeployableFile object.
• WarParser: Parse an WAR descriptor to extract meaninful information for Cactus, the results being stored in a WarDeployableFile object.
• TestWebXmlMerger: Unit tests for WebXmlMerger . TODO: we need more tests for the security sections and the various references
• AbstractServerRun: Abstract class for starting/stopping an application server. When this application is first called to start the server, a listener socket is set up. Then, we it is later called to stop the server, we connect to the listener socket and tell the server to stop.
• GenericContainer: A generic container that can be nested in the org.apache.cactus.integration.ant.CactusTask to support complete customization of the container lifecycle from a build file.
• TestApplicationXmlVersion: Unit tests for ApplicationXmlVersion .
• TestApplicationXml: Unit tests for ApplicationXml .
• TestResources: Verify that resources included with the cactus.resources.dirs properties are found in the resulting cactified WAR. Note that we're testing this by executing this code inside the container.
• AbstractContainer: Abstract base class for supporting specific containers as nested elements in the org.apache.cactus.integration.ant.CactusTask .
• MockContainer: Mock implementation of the Container interface.
• TestWebXmlVersion: Unit tests for WebXmlVersion .
• TestWarArchive: Unit tests for WarArchive .
• DefaultAntTaskFactory: Default AntTaskFactory for creating Ant tasks.
• TestAbstractContainer: Unit tests for AbstractContainer .
• TestResin3xTask: Unit tests for Resin3xTask .
• TestContainerRunner: Unit tests for ContainerRunner .
• CactusWar: Implements the nested element cactuswar of the cactifyear task. This element can be configured exactly as the cactifywar task with som additions as context within the ear file.
• TestWebXml: Unit tests for WebXml .
• TestJarArchive: Unit tests for JarArchive .
| Home | Contact Us | Privacy Policy | Terms of Service |