Home Area Assets

• Base Asset
• Named Asset
• Folder Contained Asset
• Reference Asset
• Stylesheet Asset
• Template Asset
• Dublin Aware Asset
• Expiring Asset
• Symlink
• Block
• Feed Block
• Index Block
• Text Block
• XHTML Block
• XML Block
• Publishable Asset
• File
• Folder
• Page

NEWS & TIPS

• Site Access Keys
• Top: Alt+t
  Previous: Alt+,
  Next: Alt+.
  Up: Alt+;
  (Note: use Ctrl on the Mac)

Folder Contained Asset

A Folder Contained Asset is defined in the following WSDL:

<complexType name="folder-contained-asset"> <complexContent> <extension base="impl:named-asset"> <sequence> <!-- The parent folder relationship. Change this to move an asset --> <choice> <element maxOccurs="1" minOccurs="1" name="parentFolderId" type="xsd:string"/> <element maxOccurs="1" minOccurs="1" name="parentFolderPath" type="xsd:string"/> </choice> <!-- The path of an asset. This is the other way (in addition to the id) to uniquely identify an asset. When creating this will be left blank. When editing, specify this to uniquely identify an asset. --> <element maxOccurs="1" minOccurs="0" name="path" type="xsd:string"/> </sequence> </extension> </complexContent> </complexType>

As the WSDL shows, folder-contained-asset extends from named-asset. Additionally, all folder-contained-assets are capable of specifying a parentFolderId or a parentFolderPath for defining the parent folder relationship. Furthermore, the folder-contained-asset defines the other way for identifying an asset in Cascade Server: the Path property. This is used to identify only the asset being edited. To move an asset, you would change the parentFolderId or parentFolderPath property, NOT the path property. For example, to move a page /intranet/default to /intranet/pages/default, the SOAP request would contain, in part:

<m:path>/intranet/default</m:path> <m:parentFolderPath>/intranet/pages</m:parentFolderPath>

The first element, Path, defines the Path of the existing asset (where it resides when the request is being made). The second element, parentFolderPath, specifies the destination (where it will reside once the request is completed).

To calculate the Path of any asset in Cascade Server, use the following: path = parentFolderPath + "/" + name.

Now we will come across four things that build on folder-contained-asset: dublin-aware-asset, reference, stylesheet, and template. The first is another "abstract" classification - it does not correspond to any specific Cascade Server asset; instead, it defines more fields that appear in a subset of Assets. The other three - reference, stylesheet, and template - are indeed asset types with which most users are familiar.

Comments

Wiki | Edit