|
||||||||||
| PREV NEXT | FRAMES NO FRAMES | |||||||||
| Packages that use com.ca.jcs.processor | |
|---|---|
| com.ca.jcs | Contains all classes making up the implementation of CA Java Connector Server ("Java CS" or "JCS"), which supports connectors which take LDAP traffic in at the top level and convert it into the native language of the managed system with which they communicate. |
| com.ca.jcs.assoc | Collection of classes/interfaces concerned with the representation and processing of associations between objects. |
| com.ca.jcs.jdbc | |
| com.ca.jcs.jndi | This package provides support relating to the Java Naming and Directory Interface (JNDI) package of the JDK. |
| com.ca.jcs.meta | Contains components which are metadata driven or assist in the condensing of information derived from metadata to allow efficient processing. |
| com.ca.jcs.ora | |
| 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. |
| com.ca.jcs.sdk | This package contains a worked example demonstrating all core elements involved in implementation of a JCS hosted connector, such as: example supporting metadata and configuration files. |
| com.ca.jcs.sdkws | This package contains an example that demonstrates the implementation of a web service JCS hosted connector. |
| com.ca.jcs.stub | This package contains support for stub connector classes needed for connectors implemented entirely using scripting. |
| Classes in com.ca.jcs.processor used by com.ca.jcs | |
|---|---|
| AbstractAttributeStyleOpProcessor
Base class for attribute-style processors, that mandates a standardized constructor for maximum consistency. |
|
| 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. |
|
| 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. |
|
| 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. |
|
| OpProcessor
Defines basic JNDI operations (with the addition of some more specialised arguments) allowing operation-specific processor implementations. |
|
| OpProcessor.MethodName
An enumeration matching methods which can be targeted by OpBindings in this class. |
|
| 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. |
|
| Classes in com.ca.jcs.processor used by com.ca.jcs.assoc | |
|---|---|
| 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. |
|
| 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. |
|
| 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. |
|
| 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. |
|
| OpProcessor
Defines basic JNDI operations (with the addition of some more specialised arguments) allowing operation-specific processor implementations. |
|
| PostQueryAttributesProcessor
Optional interface that should be implemented by AttributeStyleOpProcessors
that wish to script specialized handling of query results. |
|
| Classes in com.ca.jcs.processor used by com.ca.jcs.jdbc | |
|---|---|
| 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. |
|
| 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. |
|
| 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. |
|
| 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. |
|
| 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. |
|
| 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. |
|
| Classes in com.ca.jcs.processor used by com.ca.jcs.jndi | |
|---|---|
| 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. |
|
| 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. |
|
| 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. |
|
| 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. |
|
| Classes in com.ca.jcs.processor used by com.ca.jcs.meta | |
|---|---|
| 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. |
|
| 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. |
|
| 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. |
|
| 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. |
|
| Classes in com.ca.jcs.processor used by com.ca.jcs.ora | |
|---|---|
| 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. |
|
| 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. |
|
| 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. |
|
| 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. |
|
| Classes in com.ca.jcs.processor used by com.ca.jcs.processor | |
|---|---|
| AbstractAttributeStyleOpProcessor
Base class for attribute-style processors, that mandates a standardized constructor for maximum consistency. |
|
| 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. |
|
| 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. |
|
| 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. |
|
| 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. |
|
| OpProcessor.MethodName
An enumeration matching methods which can be targeted by OpBindings in this class. |
|
| PostQueryAttributesProcessor
Optional interface that should be implemented by AttributeStyleOpProcessors
that wish to script specialized handling of query results. |
|
| ProxyChainEntry
|
|
| Classes in com.ca.jcs.processor used by com.ca.jcs.sdk | |
|---|---|
| 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. |
|
| 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. |
|
| 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. |
|
| 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. |
|
| Classes in com.ca.jcs.processor used by com.ca.jcs.sdkws | |
|---|---|
| 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. |
|
| 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. |
|
| 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. |
|
| 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. |
|
| Classes in com.ca.jcs.processor used by com.ca.jcs.stub | |
|---|---|
| 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. |
|
| 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. |
|
| 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. |
|
| OpProcessor
Defines basic JNDI operations (with the addition of some more specialised arguments) allowing operation-specific processor implementations. |
|
| OpProcessor.MethodName
An enumeration matching methods which can be targeted by OpBindings in this class. |
|
| 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. |
|
|
||||||||||
| PREV NEXT | FRAMES NO FRAMES | |||||||||