Jersey filter/Interception binding

looks like mainly 3 ways to define the filter/interceptor
1. global binding
by the @Provider annotation and implement the Client/ContaineRequest/ResponseFilter
this would apply to all request/response

2.named binding
by create new annotation of @NameBinding, which annotate the customFilter and resources together to bind them

3. Dynamic binding
by implement the dynamicFeature, which then would check the resource and register/provide corresponding filters for that resource

ref: https://dzone.com/articles/binding-strategies-for-jax-rs-filters-andintercept

The RPC didn’t feel so long ago

It didn’t seems like a century old ago, when the stub and skeleton was widely used, and WSDL2Java & Java2WSDL was pretty convenient and “cool”:

  1. A Java program executes a method on a stub (local object representing the remote service)
  2. The stub executes routines in the JAX-RPC Runtime System (RS)
  3. The RS converts the remote method invocation into a SOAP message
  4. The RS transmits the message as an HTTP request

it’s now an Optional in Java EE7, but good to see it’s still there.

https://java.net/projects/jax-rpc/