Who already implemented reusable Components?

What is a Component?

Every UI5 application is a Component!

Because we always extend:

sap.ui.core.UIComponent

which extends

sap.ui.core.Component

UI5 applications can be reused in another application

In this case we have a rootView

But we can also expose a Control

						
							...
							metadata : {
								"abstract": true,
								rootView : null, // the rootView to open
								publicMethods: [ "render" ],
								aggregations: {
									/**
									 * The root control of the UIComponent.
									 *
									 * The root control should be created inside the function
									 * {@link sap.ui.core.UIComponent#createContent}.
									 */
									"rootControl": { 
										type: "sap.ui.core.Control",
										multiple: false, 
										visibility: "hidden" 
									}
								},
								...
							}
						
					

Use-cases for reusable Components

• Search helps/Value Help Dialogs
• Information Dialog views
• Lists and Tables

Components Vs Controls

Components can create models and work with Back-ends

Controls can't

Reusable Component example: AttachmentManager

Initial goals:

• Wrapper for UploadCollection
• UploadSet implementation
• Standardize working with attachments and links

You can also go too far with implementing reusable components

You can propagate the models from the application to the ComponentContainer
So the risk exists that you make a Reusable Component app dependent...

Routing in Nested Components in 1.60

Tom Van Doorslaer's post

Routing in Nested Components from 1.72

Jiawei Cao's post

GitHub Repositories:

• Component Library (including attachmentManager)
• Routing in Nested Components in UI5 1.60 (Products Component)
• Routing in Nested Components in UI5 1.60 (Suppliers Component)
• Routing in Nested Components from UI5 1.72 (Products Component)
• Routing in Nested Components from UI5 1.72 (Suppliers Component)
• Routing in Nested Components from UI5 1.72 (Nested Component)