Skip to end of metadata
Go to start of metadata

Overview

The WOAdaptor layer of WebObjects can be thought of as a broker of requests and responses. Its role in the framework is to:

  1. Receive incoming requests of some type (typically HTTP)
  2. Package them into a WORequest
  3. Dispatch the WORequest to the WOApplication
  4. Receive the WOResponse back from the WOApplication
  5. Send the response back across whatever protocol the adaptor handles

In most cases, you will be dealing with WODefaultAdaptor, which provides support for HTTP. However, adaptors could receive requests from any number of sources. As an example, Project Wonder includes ERIMAdaptor, which provides support for requests and responses over Instant Messaging networks.

Netty WOAdaptor

The Wonder ERWOAdaptor framework includes a new WOAdaptor based on Netty.
JBoss Netty, Grizzly and Apache Mina are frameworks for Java NIO. But Netty is widely regarded in the industry as being the fastest and most scalable...

How To Use

  1. Include the ERWOAdaptor framework in your app project and rebuild.
  2. Run the app with the property -WOAdaptor WONettyAdaptor

Limitations

Currently, there is a fixed file size limit for file uploads. This is settable via a property WOFileUpload.sizeLimit. It defaults to 100MB.

AJP Adaptor

The LEWOStuff frameworks include a WOAdaptor which can be used to supply requests from an AJP supplier such as Apache2.