ActivationSpec and supportsDynamicUpdates

[fcorneli]

The JCA specs mentions the support of dynamic updates on configuration properties of ActivationSpec, but does not mention AFAIK how the resource adapter should behave related to the endpointActivation.
When a property on the ActivationSpec is changed at runtime, will the resource adapter walk through an endpointDeactivation-endpointActivation sequence or does the underlying worker needs to handle this itself?
And how to retrieve the active ActivationSpec bean instance at runtime from within a certain application? Should the resource adapter do a self-registration within JNDI so the application can access this?

The idea is that I provide a sane default configuration for my endpoints at deployment time, but that I can change the configuration at run-time without the need to restart my application. For example, when the Ethereum client node address changes.
See also:
https://github.com/e-Contract/ethereum-resource-adapter

Could someone highlight how to implement dynamic updates on ActivationSpec?