Uses of Package
com.mastfrog.acteur

Packages that use com.mastfrog.acteur
  • Class
    Description
    A single piece of logic which can Reject an HTTP request Validate an HTTP request and allow the next Acteur in the chain to process it Initiate an HTTP response Acteurs are aggregated into a list in a Page.
    A test which can be performed on a request, for example, to decide about branching
    A web application.
    A registry of resources (for example, streams or JDBC objects) which should be closed if the connection terminates while a response is being processed.
    Converts byte buffers and maps to objects
     
    Encapsulates either an object indicating success, or a throwable indicating failure, which is written to a response using DeferredComputationResultActeur (added automatically to the chain if you use Acteur.then(CompletableFuture).
    An HTTP request or similar, which is passed to Pages for their Acteurs to respond to.
    Generates JSON help for the application; HelpPage converts this into HTML.
     
    Really an aggregation of Acteurs and a place to set header values; in recent versions of Acteur it is rarely necessary to implement this - instead, simply annotate your entry-point Acteur with @HttpCall and one will be generated for you under-the-hood, and use @Precursors and @Concluders to specify Acteurs that should run before/after that one.
    Logger which can be injected, which takes care of actually logging each request and response.
    Abstraction for a response
    Abstraction over Netty's channel/ByteBuf to insulate from changes there.
     
     
    The output condition of an Acteur.
  • Class
    Description
    A single piece of logic which can Reject an HTTP request Validate an HTTP request and allow the next Acteur in the chain to process it Initiate an HTTP response Acteurs are aggregated into a list in a Page.
    A web application.
    Really an aggregation of Acteurs and a place to set header values; in recent versions of Acteur it is rarely necessary to implement this - instead, simply annotate your entry-point Acteur with @HttpCall and one will be generated for you under-the-hood, and use @Precursors and @Concluders to specify Acteurs that should run before/after that one.
  • Class
    Description
    A single piece of logic which can Reject an HTTP request Validate an HTTP request and allow the next Acteur in the chain to process it Initiate an HTTP response Acteurs are aggregated into a list in a Page.
     
    Really an aggregation of Acteurs and a place to set header values; in recent versions of Acteur it is rarely necessary to implement this - instead, simply annotate your entry-point Acteur with @HttpCall and one will be generated for you under-the-hood, and use @Precursors and @Concluders to specify Acteurs that should run before/after that one.
    Abstraction for a response
  • Class
    Description
    A single piece of logic which can Reject an HTTP request Validate an HTTP request and allow the next Acteur in the chain to process it Initiate an HTTP response Acteurs are aggregated into a list in a Page.
    An HTTP request or similar, which is passed to Pages for their Acteurs to respond to.
     
    Really an aggregation of Acteurs and a place to set header values; in recent versions of Acteur it is rarely necessary to implement this - instead, simply annotate your entry-point Acteur with @HttpCall and one will be generated for you under-the-hood, and use @Precursors and @Concluders to specify Acteurs that should run before/after that one.
  • Class
    Description
    A single piece of logic which can Reject an HTTP request Validate an HTTP request and allow the next Acteur in the chain to process it Initiate an HTTP response Acteurs are aggregated into a list in a Page.
    An HTTP request or similar, which is passed to Pages for their Acteurs to respond to.
    Really an aggregation of Acteurs and a place to set header values; in recent versions of Acteur it is rarely necessary to implement this - instead, simply annotate your entry-point Acteur with @HttpCall and one will be generated for you under-the-hood, and use @Precursors and @Concluders to specify Acteurs that should run before/after that one.
    Abstraction for a response
  • Class
    Description
    A single piece of logic which can Reject an HTTP request Validate an HTTP request and allow the next Acteur in the chain to process it Initiate an HTTP response Acteurs are aggregated into a list in a Page.
    Really an aggregation of Acteurs and a place to set header values; in recent versions of Acteur it is rarely necessary to implement this - instead, simply annotate your entry-point Acteur with @HttpCall and one will be generated for you under-the-hood, and use @Precursors and @Concluders to specify Acteurs that should run before/after that one.
  • Class
    Description
    A web application.
    An HTTP request or similar, which is passed to Pages for their Acteurs to respond to.
     
  • Class
    Description
    An HTTP request or similar, which is passed to Pages for their Acteurs to respond to.
  • Class
    Description
    A single piece of logic which can Reject an HTTP request Validate an HTTP request and allow the next Acteur in the chain to process it Initiate an HTTP response Acteurs are aggregated into a list in a Page.
     
    Really an aggregation of Acteurs and a place to set header values; in recent versions of Acteur it is rarely necessary to implement this - instead, simply annotate your entry-point Acteur with @HttpCall and one will be generated for you under-the-hood, and use @Precursors and @Concluders to specify Acteurs that should run before/after that one.