| Home >> All >> org >> apache >> cactus >> [ internal Javadoc ] |
• org.apache.cactus.internal: Javadoc index of package org.apache.cactus.internal.
Package Samples:
• org.apache.cactus.internal.client.connector.http: Contains the classes implementing of the client side of Cactus.
• org.apache.cactus.internal.server.runner: Contains the classes implementing the server side of Cactus.
• org.apache.cactus.internal.configuration: Contains Cactus internal implementation classes.
• org.apache.cactus.internal.util
• org.apache.cactus.internal.server
• org.apache.cactus.internal.client
Classes:
• ServletExceptionWrapper: Wrapper around a Throwable object. Whenever an exception occurs in a test case executed on the server side, the text of this exception along with the stack trace as a String are sent back in the HTTP response. This is because some exceptions are not serializable and because the stack trace is implemented as a transient variable by the JDK so it cannot be transported in the response. However, we need to send a real exception object to JUnit so that the exception stack trace will be printed in the JUnit console. This class does this by being a Throwable and overloading the printStackTrace() methods ...
• AutoReadHttpURLConnection: Wrapper class for the real HttpURLConnection to the test servlet that reads the complete input stream into an internal buffer on the first call to getInputStream(). This is to ensure that the test servlet is not blocked on i/o when the test caller asks for the results. The wrapper returns the buffered input stream from getInputStream and delegates the rest of the calls. This class is final so we don't have to provide access to protected instance variables and methods of the wrapped connection.
• ClientTestCaseCaller: Provides the ability to run common code before and after each test on the client side. All the methods provided are independent of any communication protocol between client side and server side (HTTP, JMS, etc). Any protocol dependent methods must be provided and implemented in the org.apache.cactus.spi.client.connector.ProtocolHandler implementation class.
• AbstractCactusTestCase: Base class for all Cactus test case extensions. Note: We must not add any method that can be called by the end user to this class as users will those methods and it will create a runtime dependency to this class. We will then have to break binary compatibility if we wish to move this class around or change its implementation.
• AbstractTestAbstractCactusTestCase: Test class that intercepts all exceptions (and assert them) coming from test case classes that inherits from it. This class is used to unit test the AbstractCactusTestCase class.
• ConnectionHelper: Helper class to open an HTTP connection to the server redirector and pass to it HTTP parameters, Cookies and HTTP headers. It enables different possible implementations of an HTTP connection (ex: using the JDK HttpURLConnection or using Jakarta HttpClient).
• ServletTestController: Servlet Controller that extracts the requested service from the HTTP request and executes the request by calling a ServletTestCaller . There are 2 services available : one for executing the test and one for returning the test result.
• FilterTestController: Filter Controller that extracts the requested service from the HTTP request and executes the request by calling a FilterTestCaller . There are 2 services available : one for executing the test and one for returning the test result.
• JspTestController: JSP Controller that extracts the requested service from the HTTP request and executes the request by calling a JspTestCaller . There are 2 services available : one for executing the test and one for returning the test result.
• AbstractWebTestController: Controller that extracts the requested service from the HTTP request and executes the request. Examples of requests are: executing a given test, returning the test result, verifying that the controller is correctly configured, etc.
• WebResponseObjectFactory: Constructs Web response objects. Supports both Cactus org.apache.cactus.WebResponse and HttpUnit com.meterware.httpunit.WebResponse response object creation.
• HttpProtocolState: HTTP-specific state information to be passed to the different org.apache.cactus.spi.client.connector.ProtocolHandler lifecycle methods.
• ServerTestCaseCaller: Provide the ability to execute Cactus test case classes on the server side. It mimics the JUnit behavior by calling setUp() , testXXX() and tearDown() methods on the server side.
• AbstractWebImplicitObjects: Holder class that contains the instances of the implicit objects that exist for all web requests. Namely they are HttpServletRequest , HttpServletResponse and ServletContext .
• AbstractWebTestCaller: Responsible for instanciating the TestCase class on the server side, set up the implicit objects and call the test method. This class provides a common abstraction for all test web requests.
• WebRequestImpl: Extends BaseWebRequest to add properties specific to the Cactus Web Redirectors.
• AssertionFailedErrorWrapper: Same as ServletExceptionWrapper except that this exception class extends JUnit AssertionFailedError so that JUnit will print a different message in it's runner console.
• TestTestCaseImplementChecker: Unit tests for the TestCaseImplementChecker class.
• BaseWebRequest: Contains all HTTP request data for a test case but independently of the fact that there is or there is not a Cactus redirector. It is the data that will be sent to the server side.
• TestAbstractCactusTestCase: Unit tests of the AbstractCactusTestCase class.
• TestXMLFormatter: Unit tests for XMLFormatter .
• WebImplicitObjects: Interface for implicit objects that exist for all web requests ( HttpServletRequest , HttpServletResponse and ServletContext ).
| Home | Contact Us | Privacy Policy | Terms of Service |