Simple example of how to define client endpoints using the same techniques as the server routes.
Note that the client will automatically reject (with a 400) any unknown or missing parameters, as per the
specified route. The response is also decorated with the anonymised route, allowing for collection of
metrics about timing and number of requests going to the downsteam systems.
This example also shows how you can re-use the RouteSpec across client and servers, thus allowing really simple
stub/fake implementations of remote systems to be created.
Linear Supertypes
App, DelayedInit, AnyRef, Any
Ordering
Alphabetic
By Inheritance
Inherited
ClientSideAndSharedRouteSpecExample
App
DelayedInit
AnyRef
Any
Hide All
Show All
Visibility
Public
All
Value Members
final def!=(arg0: Any): Boolean
Definition Classes
AnyRef → Any
final def##(): Int
Definition Classes
AnyRef → Any
final def==(arg0: Any): Boolean
Definition Classes
AnyRef → Any
defargs: Array[String]
Attributes
protected
Definition Classes
App
Annotations
@deprecatedOverriding("args should not be overridden", "2.11.0")
Simple example of how to define client endpoints using the same techniques as the server routes. Note that the client will automatically reject (with a 400) any unknown or missing parameters, as per the specified route. The response is also decorated with the anonymised route, allowing for collection of metrics about timing and number of requests going to the downsteam systems.
This example also shows how you can re-use the RouteSpec across client and servers, thus allowing really simple stub/fake implementations of remote systems to be created.