Dear Wiki user, You have subscribed to a wiki page or wiki category on "Olingo Wiki" for change notification.
The "Documentation/ProcessorInterfaces" page has been changed by MichaelBolz: https://wiki.apache.org/Olingo/Documentation/ProcessorInterfaces?action=diff&rev1=4&rev2=5 = Processor methods = == General method signature == - ... + General method signature is that the method name is a combination of the type of request (create/read/update/delete) and the to be handled EDM-Type (e.g. Entity or EntityCollection or …). + Only exception are the process methods of the BatchProcessor (processBatch(...)), ErrorProcessor (processError(...)) and all Action*Processor (e.g. processActionEntity(...) ). Because for this methods exists no direct mapping of the request type to an according create/read/update/delete. + Each method has following parameters: the Request as request:ODataRequest parameter, the response as response:ODataResponse parameter and the informationen for the request URI as uriInfo:UriInfo parameter. + Because the response for a request is also given as a parameter all methods does not have a return value (i.e. all are "void"). This architectural decision is inspired by the JavaEE-Servlet architecture (javax.servlet.*). + + Additional to listed parameters each method for which the response format is dependent on the HTTP Accept Header or OData $format option has the responseFormat:ContentType parameter which defines the content type after the content negotiation for the response. + + Additional to listed parameters each method for which the request contains a body part (e.g. POST/PUT requests) has the requestFormat:ContentType parameter which is the HTTP Content-Type header for the request. + + == General HTTP request to Processor method mapping == * HTTP GET -> readXxx(...) (example for Entity: * readEntity(request:ODataRequest, response:ODataResponse, uriInfo:UriInfo, responseFormat:ContentType):void * HTTP POST -> createXxx(...) (example for Entity:
