Does Content Delivery have `ItemTypes.SCHEMA`?

Question

I'm trying to understand this question: Not able to get list of schema names when I pass publication ID and with ItemTypeCriteria schema by using Broker API and this strikes me as odd (pointed out in my answer):

ItemTypeCriteria IsSchema = new ItemTypeCriteria(ItemTypes.SCHEMA);

As far as I know, in the CD API, we can get back items such as:

• Component IDs
• ComponentPresentations (based on a Component + Template)
• Pages
• Custom Metadata

But can you get a list of schemas back?

Following the example, I couldn't get ItemTypes.SCHEMA to work without Com.Tridion. But does that belong in CD?

Answer 1

Content Delivery does have Schemas (if they are published, which by default they will), your cd_deployer_conf.xml should have the following module:

<Module Type="SchemaDeploy" Class="com.tridion.deployer.modules.SchemaDeploy"/>

But they are not queryable as a list, the following will return you zero results always:

Criteria criteria = new ItemTypeCriteria(8);
Query query = new Query(criteria);
string[] result = query.ExecuteQuery();

While if you use ItemTypeCriteria(16) or ItemTypeCriteria(64) you will get all the Components or Pages in your Broker DB.

They used to be there for Schema validation, not sure if and how that still can be used through the available APIs.

Answer 2

Yes, com.tridion.ItemTypes.SCHEMA belongs in CD. The cd_core.jar (part of content delivery api) has com.tridion.ItemTypes, this also defines ItemTypes.SCHEMA.

The com.tridion.ItemTypes is also documented in the Java API documentaiton (HTML apidocs), but not in the .NET documentation (chm file). That may be a documentation bug in the .NET documentation, or would it not be available in .NET? I did not try.

It makes sense that the Content Delivery API is aware of schemas and the broker even stores them. After all, you are able to query on schema id and schema name.

I think you cannot query a list of schemas like you would query Tridion.ContentDelivery.DynamicContent..ComponentPresentation.

Answer 3

It makes sense to me. What does not make sense is that the Schemas table only contains Schemas of Components published as DCPs. Components published embedded statically on pages do not get Schemas inserted into he Broker DB as far as I can tell.