Package com.ca.jcs.processor

Contains components implementing processing of LDAP operations like add() / modify() search etc, where three styles are supported: attribute-style, method-style and script-style.

See:
Description

Interface Summary

AttributeStyleOpProcessor	This style of op processor is the most commonly used one, and relies on metadata to define the datamodel and mappings for all objects to be handled for the parent connector.
MethodStyleOpProcessor	Implemented by connector processor components whose implementation is largely independent of the actual JNDI operation being performed, such as handling method-style and script-style op bindings.
MethodStyleOpProxyHandler.AttributeHandler
OpProcessor	Defines basic JNDI operations (with the addition of some more specialised arguments) allowing operation-specific processor implementations.
OpProcessorStyleFactory	Delineates responsibility for creating all styles of op processors supported in the JCS framework, where the lack of support for a particular style is signalled by returning null from the associated create*() methods.
PostQueryAttributesProcessor	Optional interface that should be implemented by AttributeStyleOpProcessors that wish to script specialized handling of query results.

Class Summary

AbstractAttributeStyleOpProcessor	Base class for attribute-style processors, that mandates a standardized constructor for maximum consistency.
AbstractAttributeStyleOpProcessorAssocDirect	Base class for attribute-style processors which implement direct associations.
AbstractAttributeStyleOpProcessorAssocIndirect	Base class for attribute-style processors which implement indirect associations.
AbstractBaseProcessor	Created this class so that we can mandate a constructor taking some fields we know every concrete baseConnector will need access to, for maximum clarity.
AbstractMethodStyleOpProcessor	Created this class so that we can mandate a constructor taking some fields we know every concrete baseConnector will need access to, for maximum clarity.
AbstractScriptStyleOpProcessor	Created this class so that we can mandate a constructor taking some fields we know every concrete baseConnector will need access to, for maximum clarity.
AttributeStyleOpProcessorChain	Holder of a chain of proxies around an ultimate concrete AttributeStyleOpProcessor implementation.
ConnectorAttributesProcessor	Handles operating on the top-level connector object itself, and handles converting tracking of connection related connector level attributes into activate() on a concrete BaseConnector etc.
ConnectorProcessorProxyHandler	Base class for all proxies wrapping all styles of op processor implemented for a connector, for instance for use in implementing resilient connectivity (ability to recover when communication is lost to the managed target system temporarily) or for translating exceptions from the connector domain to the LdapNamingException domain.
MetaOpBindingsProxyHandler	Helps out MetaConnector by handling dispatching of method-style and script-style operation binding calls to the registered processors, after evaluating guard conditions for relevance.
MethodStyleOpProxyHandler	Delegated to by MetaOpBindingsProxyHandler to take care of method-style op bindings.
MethodStyleOpProxyHandler.AddOpAttributeHandler
MethodStyleOpProxyHandler.ModifyOpAttributeHandler
MethodStyleOpProxyHandler.SimpleOpAttributeHandler
ProxyChainEntry
RetryOpProcessorProxy	This proxy that can wrap any of a connectors processors (attribute-style/method-style etc) and provide resilient retrying when transient connection-related failures (aka "soft failures") are encountered, based on the retryGroupMap configured on a connector's ConnectorConfig JavaBean (usually configured from /conf/connector.xml using Spring XML).

Enum Summary

OpProcessor.MethodName

An enumeration matching methods which can be targeted by OpBindings in this class.

Package com.ca.jcs.processor Description

Contains components implementing processing of LDAP operations like add() / modify() search etc, where three styles are supported: attribute-style, method-style and script-style.

Attribute-style is the most commonly used style and managed by metadata defining both the datamodel and mappings for it (refer datamodel.xsd) and example shipped with the SDK sample (sdk_metadata.xml). Implementationally the other two styles require an attribute-style processor to function (as they are implemented using Java proxy objects), so one will always be present for a concrete connector (even if it is a "null" processor with all its methods stubbed out). Method-style and script-style are managed through operation bindings, which allow processing to occur before (timing=pre), instead op (timing=op) or after (timing=post) LDAP operations. Refer to opbindings.xsd for specification of the XML structures used to configure such opbindings on a connector.

$Id: package.html 47098 2010-01-22 01:36:37Z khaam03 $