ome.services.blitz.util

Class ApiConsistencyCheck

java.lang.Object

ome.services.blitz.util.ApiConsistencyCheck

All Implemented Interfaces:

org.springframework.beans.factory.config.BeanPostProcessor

public class ApiConsistencyCheck
extends Object
implements org.springframework.beans.factory.config.BeanPostProcessor

Checks all servant definitions (see: ome/services/blitz-servantDefinitions.xml) to guarantee that the RMI and the Blitz APIs match.

Since:

3.0-Beta3

Author:

Josh Moore, josh at glencoesoftware.com

See Also:

ticket:894

Constructor Summary

Constructors

Constructor and Description
ApiConsistencyCheck()

Method Summary

Methods

Modifier and Type	Method and Description
static boolean	matches(Class apiType, Class opsType) Defines what Class types match.
Object	postProcessAfterInitialization(Object arg0, String arg1) Apply this BeanPostProcessor to the given new bean instance after any bean initialization callbacks (like InitializingBean's afterPropertiesSet or a custom init-method).
Object	postProcessBeforeInitialization(Object arg0, String arg1) No-op

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

ApiConsistencyCheck

public ApiConsistencyCheck()

Method Detail

postProcessAfterInitialization

public Object postProcessAfterInitialization(Object arg0,
                                    String arg1)
                                      throws org.springframework.beans.BeansException

Description copied from interface: org.springframework.beans.factory.config.BeanPostProcessor

Apply this BeanPostProcessor to the given new bean instance after any bean initialization callbacks (like InitializingBean's afterPropertiesSet or a custom init-method). The bean will already be populated with property values. The returned bean instance may be a wrapper around the original.

In case of a FactoryBean, this callback will be invoked for both the FactoryBean instance and the objects created by the FactoryBean (as of Spring 2.0). The post-processor can decide whether to apply to either the FactoryBean or created objects or both through corresponding bean instanceof FactoryBean checks.

This callback will also be invoked after a short-circuiting triggered by a InstantiationAwareBeanPostProcessor.postProcessBeforeInstantiation(java.lang.Class<?>, java.lang.String) method, in contrast to all other BeanPostProcessor callbacks.

Specified by:

postProcessAfterInitialization in interface org.springframework.beans.factory.config.BeanPostProcessor

Parameters:

arg0 - the new bean instance

arg1 - the name of the bean

Returns:

the bean instance to use, either the original or a wrapped one

Throws:

org.springframework.beans.BeansException - in case of errors

See Also:

InitializingBean.afterPropertiesSet(), FactoryBean

postProcessBeforeInitialization

public Object postProcessBeforeInitialization(Object arg0,
                                     String arg1)
                                       throws org.springframework.beans.BeansException

No-op

Specified by:

postProcessBeforeInitialization in interface org.springframework.beans.factory.config.BeanPostProcessor

Parameters:

arg0 - the new bean instance

arg1 - the name of the bean

Returns:

the bean instance to use, either the original or a wrapped one

Throws:

org.springframework.beans.BeansException - in case of errors

See Also:

InitializingBean.afterPropertiesSet()

matches

public static boolean matches(Class apiType,
              Class opsType)

Defines what Class types match.

Parameters:

apiType -

opsType -