Home >> All >> org >> apache >> cactus >> spi

•	org.apache.cactus.spi.client.* (3)	•	org.apache.cactus.spi.client.connector.* (2)
•	org.apache.cactus.spi.server.* (2)

Package Samples:

• org.apache.cactus.spi.client.connector: Contains Cactus client-side SPI classes required to implement new protocols other than the Cactus-implemented ones.  
• org.apache.cactus.spi.server
• org.apache.cactus.spi.client

Classes:

• ProtocolHandler: Any communication protocol (e.g HTTP) used to connect between Cactus client side and Cactus server side must implement this lifecycle interface. This interface is part of the connector SPI. Here is the lifecycle followed by Cactus core: Call createRequest() 55 to create a request object that will be passed to the begin() and beginXXX() methods. They will in turn enrich it with values set by the user. Call begin() and beginXXX() methods. Call runTest(junit.framework.Test, junit.framework.Test, org.apache.cactus.Request) 55 to execute the tests. Call createResponseObjectFactory(org.apache.cactus.spi.client.connector.ProtocolState) ...
• ProtocolState: Hold protocol-related information that need to be exchanged during the lifecycle of the ProtocolHandler . For example the HTTP protocol handler needs to pass the HTTP connection around to the different lifecycle methods. However, as this kind of state information is highly protocol dependent, we needed to abstract out the state information, hence this tagging interface. The implementation is free to have any kind of methods. These methods will only be used in the ProtocolHandler implementation classes.
• TestController: Controller interface that simulates a bit the controller from the MVC model in that this controller implementation classes are in charge of extracting data from the request and calling the test method to execute. Note that this is independent of the protocol (HTTP, JMS, etc).
• ImplicitObjects: Tagging interface for implicit objects. Implicit objects are objects that are instanciated by the containers and that need to be made visible to your test case classes.
• ResponseObjectFactory: Constructs response object that are passed as parameter to endXXX() and global end() methods.

Home | Contact Us | Privacy Policy | Terms of Service