clarencen/lshift — Issue #302: Support custom serialization in the agent
Author: clarencen
Created: 2011-11-14 22:42:26+00:00
State: open

To facilitate less intrusive integration with participants that are using a message tap pattern, it would be a good idea to be able to plug in a custom serialization mechanism into the agent. This task includes:

* Defining a robust plugin API for serialization providers
* Register themselves with the appropriate kernel frontend
* Respond to serialization requests
* Building a plugin loading mechanism that loads based on a named Spring context, e.g. load resources from

@@@
classpath: */diffa-*-extension.xml
@@@

in the plugin jar.

* Write some documentation about how to write your own provider