Nesting Development Components 

Use

You can organize your software by nesting development components (DCs). See Nested Development Components.

Procedure

You can also use a component node to start creating a DC. In this case, you create a child DC. The selected component is automatically registered as a parent component in the child component.

...

...

       1.      In the Development Configurations perspective, choose your DC.

       2.      In the context menu of the DC, choose Create Child DC.

       3.      In the dialog that appears, specify:

                            a.      The name of the vendor of the DC.

                            b.      The name of the DC. For more information about names, see Component Names and Tips for Naming Components.

You cannot change the name of the DC at a later time. If you configured a name service, it now performs a name reservation.

                            c.      Specify the Caption, Language, and Domain of the DC.

                            d.      Specify whether or not the DC is local.

If the checkbox labeled Local Development Component is enabled, the DC is created locally. In this case, the files of the DC are located only on the local disk; they are not shared with the development landscape. You can add local DCs later to the content of the Design Time Repository (DTR).

                            e.      Select a component type. See Types of Development Components.

       4.      Choose Next.

       5.      Make the settings, depending on the selected component type. In most cases, you can simply accept the proposed settings.

       6.      Choose Finish.

Changes in the Design Time Repository

Creating a new component triggers changes in the DTR. Unless the DC is local, you must now add the created files to an activity. For a new component, create a new activity.

A window showing open activities appears:

...

       1.      Enter the name and description of the new activity.

       2.      Select the created activity and confirm with OK.

You can now work with the new DC.

For an overview of the files in this activity, switch to the Open Activities view.

If you do not want to add certain changes to an activity or you want to include a local component in the NWDI at a later time, you need detailed knowledge of which files and folders are actually submitted to version control and which exist only on the local file system.

You should not submit any files to version control that are stored in folders named bin or have a name starting with gen.

Result

The component is now visible in the Development Configurations perspectives Inactive DCs and Local DCs, in the Resource perspective and in the perspective that belongs to the selected component type (for example, Java, Web Dynpro, J2EE).

A child component additionally appears under DC MetaData à DC Definition → Child DCs of the parent component.