The RoutingObjectAdapter interface is responsible for obtaining context information that the ApplicationRoutingStrategy uses to route data for indexing and querying. This interface has two subinterfaces, ContextRoutingObjectAdapter (for indexing) and RequestRoutingObjectAdapter (for querying). These subinterfaces differ mainly in terms of where they obtain the context information.

ContextRoutingObjectAdapter

Classes that implement the atg.endeca.index.configuration.ContextRoutingObjectAdapter interface use the atg.repository.search.indexing.Context object to determine the current indexing context. The Context object provides a central place to store data and state information, such as the current site and locale, during an indexing job.

There are three ContextRoutingObjectAdapter classes in the atg.endeca.index.configuration package, which correspond to the three ApplicationRoutingStrategy classes discussed above:

So, for example, if you are using SiteApplicationRoutingStrategy as your routing strategy, you should use SiteContextRoutingObjectAdapter for determining the indexing context.

RequestRoutingObjectAdapter

Classes that implement the atg.endeca.assembler.configuration.RequestRoutingObjectAdapter interface use the atg.servlet.DynamoHttpServletRequest object and other objects that hold request-specific state, such as SiteContext objects, to determine the current context for querying.

There are three RequestRoutingObjectAdapter classes in the atg.endeca.assembler.configuration package, which correspond to the three ApplicationRoutingStrategy classes discussed above:

So, for example, if you are using SiteApplicationRoutingStrategy as your routing strategy (and SiteContextRoutingObjectAdapter for determining the indexing context), you should use SiteRequestRoutingObjectAdapter for determining the querying context.