Scenarios for Requesting JSON Type Services

Following are some of the possible scenarios in which JSON type services can be requested. Many scenarios require that you "bridge" the differences between consumer requests and the native service (that is, differing HTTP methods and Content-Types). Three of the scenarios are discussed in more detail following the table:

Consumer Sends	Mediator Sends Request to Provider	Mediator Receives Response from Provider	Mediator Sends Response to Consumer	Requirement for Bridging?
GET	GET	JSON	JSON	Request Processing step bridging (see JSON Example 1: GET Request, JSON Response)
POST/JSON	POST/JSON	JSON	JSON	No bridging needed
GET	GET	XML	JSON	Response Processing step bridging
POST/JSON	GET	JSON	JSON	Request Processing step bridging
POST/JSON	GET	XML	JSON	Request Processing step bridging and Response Processing step bridging (see JSON Example 2: POST/JSON Request, JSON Response (where POST is not supported))
POST/JSON	XSLT/GET *	JSON	JSON	Request Processing step bridging
POST/JSON	XSLT/POST/XML *	XML	XML	Request Processing step bridging
POST/JSON	POST/JSON	JSON/XSLT *	JSON	Response Processing step bridging
GET	GET	JSON	XML	Request Processing step bridging and Response Processing step bridging (see JSON Example 3: GET Request, XML Response)
POST/XML	POST/JSON	JSON	JSON	Request Processing step bridging

HTTP Method/Request Content	Required Axis2 Content Type
GET or DELETE	application/x-www-form-urlencoded
POST or PUT/XML	application/xml
POST or PUT/Mapped JSON	application/json
POST or PUT/Badgerfish	application/json/badgerfish