Home >	Contents >	Index >

Template Tags TOC   |    Alpha TOC   |    Tag Family TOC   |    Purpose TOC   |    Annotated TOC   |    Index

Asset Tags

Assets are the core of Sites. Assets are objects that can be created, edited, inspected, deleted, duplicated, placed into workflow, searched for, checked out and in with revision tracking, previewed, and published. You use the asset tags to extract the information from the Sites database about your assets that you want to display on your on-line site.

When you use an asset:load tag to retrieve an asset from the database, Sites loads an instance of the asset into memory as an object. You then have access to that instance of the asset with the other asset tags until either the session is flushed (the root element exits) or the name that is used for the asset object is overwritten.

Assets can have parent-child relationships that are set up either through named associations or through unnamed relationships. Named associations are defined, asset-type-specific relationships represented as fields in the asset forms. Unnamed relationships are established, for example, when you select assets from the generic Select list boxes on the Page form.

Sites stores information about assets in the following database tables:

• Primary database table that holds assets of its type. For example, each page asset has a row in the Page table and each article asset has a row in the Article table. These tables store information such as the asset's name, its object ID, who created it, which template it uses, and so on. You use the asset tags to extract information from these tables.

• AssetRelationTree table, if the asset has named associations or unnamed relationships with other assets. Use the asset:children tag to extract information from this table.

• AssetPublication table, which specifies which management sites (publications) give you access to the asset through Site's asset entry and edit forms. If the asset is shared between more than one site, there is a row entry for each pubid. A pubid is a unique value that identifies a site.

• SitePlanTree table, if the asset is a page asset. For information about this table, see Site Plan Tags .

To create types of assets, you use the AssetMaker forms in the Sites administrative User Interface. For more information about asset type development, see the Oracle WebCenter Sites Developer's Guide.

Note Each JSP file containing Sites JSP asset tags must have the following directive at the top: <%@ taglib prefix="asset" uri="futuretense_cs/asset.tld" %>

		Home >	Contents >	Index >
	Oracle JSP Tag Reference Copyright (c) 2013, 2019, Oracle and/or its affiliates. All rights reserved.