Descriptor for Components (Inside Libraries)

The descriptor for components contains a subset of the attributes in the descriptor for applications

Table 1: Attributes in the `sap.app` namespace
Attribute	Comment
`id`	Mandatory
`type`	With value `component`; mandatory
`i18n`	Path relative to component; default is `"i18n/i18n.properties"` Path back to library is also possible, for example via `"../i18n/i18n.properties"`
`embeddedBy`	Mandatory, for example, `"../"`
`title`	Mandatory
`subTitle`
`description`
`ach`
`dataSources`
`cdsViews`
`resources`	Mandatory; must have value `resources.json` as file; it is generated by the library build with this name
`offline`
`sourceTemplate`

Table 2: Attributes in the `sap.ui` namespace
Attribute	Comment
`technology`	With value `UI5`; mandatory
`deviceTypes`
`supportedThemes`

Table 3: Attributes in the `sap.ui5` namespace
Attribute	Comment
`resources`
`dependencies`	`libs` `components`
`models`
`rootView`
`handleValidation`
`config`
`routing`
`extends`	`component` `minVersion`
`contentDensities`
`componentName`

Table 4: Attributes in the `sap.mobile` namespace
Attribute	Comment
`definingRequests`

Library Name Determination

SAPUI5 determines the library name by analyzing the component namespace (package) up to the part where the segment starts with a capitalized letter. If the library name that has been determined, does not fit your component, an additional library attribute needs to be filled in the component metadata in Component.js to specify the library your component belongs to.

Example:

sap.ui.core.UIComponent.extend("com.sap.fancylibrary.sub.CompLib.Component", {
    metadata : {
        "manifest" : "json",
        "library" : "com.sap.fancylibrary",
    ...
}