Context objects are arbitrary POJOs, so you can define and implement them in the way most suitable for your application.

If you want to reuse some of the functionality provided by CoreMedia Adaptive Personalization, a specific ContextSource for example, you need to implement the required interfaces. In particular, most ContextSource implementations require a ContextFactory or a ContextCoDec implementation for your context, which provide the knowledge of how to create, serialize, and deserialize an instance of your context. Most of them also use the DirtyFlagMaintainer interface, writing a context object back into their respective stores only if the context's dirty flag is set.

Figure 4.5. A ContextSource implementing typical interfaces

If your context objects contains properties that should be available in selection rules, simply implement the PropertyProvider interface.

Figure 4.6. PropertyProvider Interface