Servis-Rhino 4211B Betriebsanweisung Seite 119

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 298
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 118
"name": "Ted Cruz",
"office": "185 Dirksen Senate Office Building",
"party": "R",
"phone": "202-224-5922",
"state": "TX"
}
]
},
"statusCode": 200,
"statusReason": "OK",
"totalTime": 349,
"warnings": [
]
}
We have the ability to test a WL.Server.invokeHttp() execution directly from within
Worklight Studio. Before we explain that it more detail, let us think about what such a test actually
means. Given that this method calls a back-end service, testing this method will perform a call to a
back-end service. The configuration options of the invokeHttp function are supplied as a rich
set of parameters to that function. The act of "testing" this function really boils down to testing that
we have built the options to control it correctly and validating that the back-end service responds as
desired when actually called.
The way we perform the test is to build an HTTP Adapter and deploy it to the Worklight Server.
The implementation JavaScript of the adapter does not need to be enhanced or changed beyond its
default settings. Remember, it is the adapter's configuration that names where the REST request
will be sent. When we test an invokeHttp() function call, it will be the destination settings of
the adapter that will be used as destination of the REST request. Once the adapter is deployed, we
can right-click the adapter within the Worklight Studio project and select Run As > Invoke
Worklight Back-end Service:
Page 119
Seitenansicht 118
1 2 ... 114 115 116 117 118 119 120 121 122 123 124 ... 297 298

Kommentare zu diesen Handbüchern

Keine Kommentare