Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep

  org.enhydra.httpServerTest.common.* (3)
org.enhydra.httpServerTest.server.* (5)org.enhydra.httpServerTest.server.application.* (3)
org.enhydra.httpServerTest.server.application.presentation.* (2)org.enhydra.httpServerTest.server.common.* (1)
org.enhydra.httpServerTest.server.servlet.* (1)

Package Samples:

org.enhydra.httpServerTest.common
org.enhydra.httpServerTest.server.application.presentation
org.enhydra.httpServerTest.server.application
org.enhydra.httpServerTest.server.common
org.enhydra.httpServerTest.server.servlet

Classes:

HttpResponseObject: This class is the data structure that is shared between the client and server tests. The life cycle of this class begins when a client thread's run() method is invoked. The first step in each of the SingleUserGetRequestThread and SingleUserPostRequestThread is to initialize a golden response object of this type from the thread's supplied configuration data. On success of this initialization, each of these threads construct an HTTP request also based on its configuration data. The request is sent to the server which then generates a new object of this type populated with all the request information ...
BasicTestApp: This is the basic application class object for the http server test. This class is very limited in its functionality and simply provides static references to a temporary directory location, setable through the appication configuration file, and a counter. The temorary directory is used for caching of files that are uploaded. The counter is used to ensure that each thread of this application, handling uploaded files, will create a unique sub-directory, under the specified temporary directory, to write to. This allows each thread to only account for uploaded files that occured on the current request ...
BasicTest: This class is the generic server side test presentation object that client side test threads talk to. This class respondes to every request comming in by constructing an HttpResponseObject and returning it in the response as an XML stream. The response object returned contains information about all data received via the request. This presentation object properly handles GET and POST method request and multi-part mime encodings.
BasicTestServlet: This class is a generic server side test servlet that client side test threads talk to. This class respondes to every request coming in by constructing an HttpResponseObject and returning it in the response as an XML stream. The response object returned contains information about all data received via the request. This presentation object properly handles GET and POST method request and multi-part mime encodings.
RequestDispatchForwardTest: This class is the generic server side test presentation object that client side test threads talk to. The purpose of this presentation object is to test the RequestDispatcher. All this class does is to forward all requests to the BasicTest.po. In doing so, the client will verify that no request information was lost.
HttpResponseObjectParser: This class uses the Xerces SAX parser to parse the http response and populate an HttpResponseObject object. This class implements a factory mechanism for retrieving a single response object from the input XML. Any errors encountered while parsing the XML file or stream will cause an exception to be thrown.
FileUploadMangler: This file implements the FilenameMangler to ensure that files uploaded to the server are save with unique file names on the file system.
HttpServerTestUtils: This class provides static data and methods that are shared by both the client and server sides of this test. See below for details.

Home | Contact Us | Privacy Policy | Terms of Service