Coherence Configuration Enhancements - Part 2 - Custom Configuration Namespaces

Coherence 12.1.2 Configuration EnhancementsPart 2: Custom Configuration NamespacesBrian OliverSenior Consulting Member of StaffCloud Application Foundation - Oracle Coherence

Oracle Fusion Middleware 12c Cloud Application Foundation

Coherence 12.1.2

The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

The Agenda…

Coherence 12.1.2 ConfigurationEnhancements…• Configuration Objects from elsewhere?

– How to I get an Object from framework X into Coherence?

• Introducing the Spring Namespace for Coherence 12.1.2

• Summary

Using Objects from Elsewhere…

Old Style Cache Store Configuration<cache-config xmlns="http://xmlns.oracle.com/coherence/coherence-cache-config" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="" xsi:schemaLocation="http://xmlns.oracle.com/coherence/coherence-cache-config coherence-cache-config.xsd">

<caching-scheme-mapping> <cache-mapping> <cache-name>dist-*</cache-name> <scheme-name>distributed-scheme</scheme-name> </cache-mapping> </caching-scheme-mapping>

<caching-schemes> <distributed-scheme> <scheme-name>distributed-scheme</scheme-name> <service-name>DistributedCache</service-name>

<backing-map-scheme> <read-write-backing-map-scheme>

<cachestore-scheme> <class-scheme> <class-name>MyOldStyleCacheStore</class-name> </class-scheme> </cachestore-scheme> </read-write-backing-map-scheme> </backing-map-scheme>

</caching-schemes></cache-config>

My Custom Cache Store Configuration<cache-config xmlns="http://xmlns.oracle.com/coherence/coherence-cache-config" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="" xsi:schemaLocation="http://xmlns.oracle.com/coherence/coherence-cache-config coherence-cache-config.xsd">

<caching-scheme-mapping> <cache-mapping> <cache-name>dist-*</cache-name> <scheme-name>distributed-scheme</scheme-name> </cache-mapping> </caching-scheme-mapping>

<caching-schemes> <distributed-scheme> <scheme-name>distributed-scheme</scheme-name> <service-name>DistributedCache</service-name>

<backing-map-scheme> <read-write-backing-map-scheme>

<cachestore-scheme> MY FRAMEWORK OBJECT HERE!!! </cachestore-scheme> </read-write-backing-map-scheme> </backing-map-scheme>

</caching-schemes></cache-config>

Objects from elsewhere?

• Use Case:– Provide an Object to Coherence (not have Coherence build one)– Use an external Container/ Factory / Framework to provide them– Coherence should just use but not instantiate Objects

• Historical Solution:– Use <class-scheme> with <class-factory-name> and <method-

name>… to specify a static factory

public static Object createObject(…);

Objects from elsewhere?

• For CDI / Spring / Guice et al support…– Extend internal DefaultConfigurableCacheFactory class– And… override internally defined instantiateAny(…) method– Or... configure a SpringAwareCacheFactory

• Oh no!!!– Can’t easily use both SpringAwareCacheFactory and Incubator…

together… Each implementation uses the same technique!

• Perhaps you need…– A Database Connection from a Database Connection Pool?– A JNDI Resource?– A Transaction Manager?– … are probably provided by another framework– … how to you “get” them into your “Cache Store”?

• @Injectables help but we need more!

Custom Configuration Namespaces…

Introducing the Spring Namespace<cache-config xmlns="http://xmlns.oracle.com/coherence/coherence-cache-config" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="" xmlns:spring="class://com.oracle.coherence.spring.SpringNamespaceHandler" xsi:schemaLocation="http://xmlns.oracle.com/coherence/coherence-cache-config coherence-cache-config.xsd class://com.oracle.coherence.spring.SpringNamespaceHandler coherence-spring-config.xsd">

<spring:bean-factory> <spring:application-context-uri>application-context.xml</spring:application-context-uri> </spring:bean-factory>

. . . <caching-schemes> <distributed-scheme> <scheme-name>distributed-scheme</scheme-name> <service-name>DistributedCache</service-name>

<backing-map-scheme> <read-write-backing-map-scheme> <cachestore-scheme> <spring:bean> <spring:bean-name>myCacheStoreBean</spring:bean-name> </spring:bean> </cachestore-scheme> </read-write-backing-map-scheme> </backing-map-scheme>

Why Coherence 12.1.2 Namespaces? They allow you to…

• Replace Standard Coherence Configurations– eg: Replace the <class-scheme> with <spring:bean>

• Refine Coherence Configuration Objects– eg: Change a defined Scheme or Cache Mapping

• Define new Coherence Configuration Objects– eg: Define a new Cache/Scheme/Mapping on-the-fly

Why Coherence 12.1.2 Namespaces? They allow you to…

• Define new Resources for @Injectables– eg: Define a Database Connection Pool in the Resource Registry

• Define new “features” for Coherence– eg: Define a new type of Cache or Service (or anything else)

• Or.. Completely replace Coherence Configurations– eg: Make up your own way to configure Coherence

Build Your Own…Imagine the possibilities…

Summary

• Coherence 12.1.2 introduces Custom Namespace Configurations– Allows integration of third-party frameworks directly into Coherence– Allows independent development of extensions– Allows customization of Coherence

Next Part?

• Developing your own Custom Namespaces– The Coherence Configuration Framework– The Coherence Configuration Model

Join the Coherence Community

http://coherence.oracle.com

@OracleCoherence

/OracleCoherence

blogs.oracle.com/OracleCoherence

Group: Oracle Coherence Users

/OracleCoherence

coherence.oracle.com/display/CSIGCoherence Special Interest Group

The proceeding is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

Coherence 12.1.2 Configuration EnhancementsPart 2: Custom Configuration NamespacesBrian OliverSenior Consulting Member of StaffCloud Application Foundation - Oracle Coherence

Oracle Fusion Middleware 12c Cloud Application Foundation

Coherence 12.1.2

Coherence Configuration Enhancements - Part 2 - Custom Configuration Namespaces

Technology

Coherence Configuration Enhancements - Part 1 - Injectables

WORKING WITH NAMESPACES

Applications of IFLA Namespaces

Coherence Configuration Enhancements - Part 4 - Cron as a Custom Configuration Namespace

IFLA Namespaces

XML Namespaces

Mastering PHP Namespaces PFCongres11

Coherence POF Configuration Generation

Namespaces, InfoSet, XML Formats

Advanced Namespaces and cgroups

Using Namespaces in XML

Oracle Fusion Middleware 12c - Oracle Coherence Community · • The com.tangosol.coherence.config package… – Defines the runtime* configuration model for Coherence 12.1.2 –

Chapter 3: XML Namespaces

NET35 Namespaces Poster LORES

Literal Notation for Arrays and Namespaces AdámBrudzewsky · for Arrays and Namespaces AdámBrudzewsky. 1 #dyalog17 Literal Notation for Arrays and Namespaces adam@dyalog.com Literal

Zoned Namespaces - SNIA

Linux Namespaces

IST346: Namespaces Directories Documentation

Namespaces for Kazimir

LSA2 - 02 Namespaces