Content Delivery API namespaces and Java packages
Content Delivery modules turn the content in your Content Manager into a fully-functional, dynamic Web site.
Querying content
.NET Namespace: Tridion.ContentDelivery.DynamicContent.Query
Java package: com.tridion.broker.querying
To help you assemble content on a Web page dynamically, the Content Broker Query API lets you set one or more filters and run a query against the database. For example, you can query the database for all Component Presentations whose contents have changed in the last 5 days.
Query content based on Keywords
.NET Namespace: Tridion.ContentDelivery.Taxonomies
Java package: com.tridion.taxonomies
The TaxonomyRelationManager class in this namespace lets you retrieve items on the basis of Keywords. This is a more specific case of the Content Broker Query API.
Retrieving Taxonomies
.NET Namespace: Tridion.ContentDelivery.Taxonomies
Java package: com.tridion.taxonomies
The TaxonomyFactory class in this namespace lets you retrieve the taxonomy (Categories and Keywords) of an item.
Retrieving metadata
.NET Namespace: Tridion.ContentDelivery.Meta
Java package: com.tridion.meta
Use this API to retrieve the various types of metadata of specific item:
- System metadata
- Custom metadata
- Categories and Keywords
You retrieve metadata for a specific type of item by using one of the 'meta factories':
BinaryMetaFactoryComponentMetaFactoryComponentPresentationMetaFactoryPageMetaFactoryPublicationMetaFactory
You can also retrieve the metadata of a Page based on its full URL. This is done using the DynamicMetaRetriever class in the Tridion.ContentDelivery.DynamicContent namespace.
Retrieving content without executing its code
.NET Namespace: Tridion.ContentDelivery.DynamicContent
Java packages: com.tridion.content and com.tridion.dcp
Use this API to retrieve the contents of an item, without executing its code. For example, links remain unresolved. This is best suited for static content items. For example, you can use this API to retrieve a binary item from the database and save it to disk.
You retrieve the raw contents of a specific type of item by using one of the 'factories':
BinaryFactoryComponentPresentationFactoryPageContentFactory
Retrieving content and executing its code
.NET Namespace: Tridion.ContentDelivery.DynamicContent
Java package: com.tridion.dynamiccontent
Use this API to retrieve the contents of an item and execute its code. This is best suited for dynamic content items.
Use the following classes to retrieve content and execute its code:
ComponentPresentationAssembler- This works for Component Presentations rendered in XML, JSP and ASCX, on the file system, and in a subdirectory of the Web application. If you published to Render Engine Language (REL), none of these restrictions apply.
PageContentAssembler- This works only for Pages published to REL.
Resolving dynamic links
.NET Namespace: Tridion.ContentDelivery.Web.Linking
Java package: com.tridion.linking
Use this API to resolve dynamic links to binary items, (dynamic) Components, or Pages, using one of the following classes:
BinaryLinkComponentLinkDynamicComponentLinkPageLink
Ambient Data Framework
.NET Namespace: Tridion.ContentDelivery.AmbientData
Java package: com.tridion.ambientdata
Use this API to develop Claim Processors that gather and transform Web site data.
User Generated Content
Java packages: com.tridion.ugc.taglib.model, com.tridion.ugc.taglib.validation, com.tridion.ugc.validation
Use this (Java only) API to work programmatically with comments and ratings.
Profiling and Personalization
.NET Namespace: Tridion.ContentDelivery.Web.WAI
Java package: com.tridion.personalization
Use this API to work with profiling, the creation of a visitor profile, and personalization, the personalized Web site response to such a profile.