Show TOC

Editing Development ComponentsLocate this document in the navigation structure

Use

To change a development component (DC) you have to perform the following steps:

  1. Select the appropriate perspective to work in the SAP NetWeaver Developer Studio.

  2. Synchronize the files of the DC in the local file system with the Design Time Repository (DTR) files.

  3. Make the change known to the repository, that is, you perform a check out.

  4. Edit the source files of the DC.

  5. Locally build the component.

  6. Copy the changes into the repository, that is, you perform a check in.

    Note

    Note that the context menu of a DC may look different depending on whether the DC is stored as a source or as an archive. This is because you do not need to create a project for a DC that is stored as an archive.

Prerequisites

You have imported a development configuration in the Developer Studio and are logged on to the SAP NetWeaver Development Infrastructure.

Procedure

Selecting the Appropriate Perspective

You edit a component in the perspective that corresponds to its type. To open the appropriate perspective in the menu path choose Start of the navigation path Window Next navigation step Open Perspective Next navigation step Other End of the navigation path .

For example, if the DC is of type Web Dynpro, you edit it in the Web Dynpro perspective. If it is of type J2EE, then edit it in the J2EE Development perspective, and so on.

Note

All projects appear in the Resource perspective .

Synchronizing the Files of the Component in the Local File System

Either you must synchronize the component or - if none exists - create a project for it. More information: Synchronizing a DC in a Local File System .

Checking Out the Files for Changing

Checking out the files for changing is necessary for old projects. After the synchronization, the files are stored read-only on the local file system. Before you can change individual files of this component, you must check them out for editing.

  1. To check out a file or folder, choose the required file or folder in the tree.

  2. From the context menu, choose Start of the navigation path DTR Next navigation step Edit End of the navigation path .

  3. In the dialog that appears, select an existing activity or create a new activity.

    You need an activity to combine changes that belong together. Therefore, select only suitable activities (activities of the same DC) for your changes or create a new activity. As long as an activity has not been checked in, it is in open state, and you can always add other files to it.

  4. To assign your file(s) to this activity, choose OK .

    Note

    If you assigned versions to a particular activity by mistake, as long as the activity is still open, that is, the activity is not checked in, you can:

    • Move individual versions to another existing or a newly created activity.

    • Rename the activity when you check it in (in case only the activity name was misleading and the activity contains only versions that belong together).

Editing the Source Files

  1. To change the source files of a component, select the perspective that corresponds to the component type.

  2. In the context menu of the component, choose either:

    • Start of the navigation path DTR Next navigation step Edit End of the navigation path : Other users can also check out this file.

    • Start of the navigation path DTR Next navigation step Edit (Exclusive) End of the navigation path: The file is locked for other users until you check it back in.

    An activity is created.

  3. Make your changes.

  4. Save your changes.

Locally Building the DC

Note

Before you check in your changes to the DTR, you should compile (build, make) the DC on your machine. If a local test environment exists, test your changes now. Only if compilation goes through (and local testing is successful) should you check in your changes.

  1. Open the perspective that belongs to the component type.

  2. In the context menu of the DC to be built, choose Build .

    A dialog box appears.

  3. Check the selected action and the DCs concerned in the dialog window and make changes, if necessary.

    The development environment automatically recognizes which components have changed and need to be built, and marks them accordingly. However, you can always change these selections, for example, if you want to enforce the building of a component.

    Note

    If errors occur during the DC build, you can view them in the General User Output view.

Checking In Changes Into the Repository

After you made sure that your changes do not trigger compilation errors, check in your activity with the changes you made.

  1. Switch to the Open Activities view.

    Note

    You can integrate this view in any perspective using the menu path Start of the navigation path Window Next navigation step Show View Next navigation step Other Next navigation step Design Time Repository Next navigation step Open Activities End of the navigation path.

  2. In the context menu of the activity, choose Checkin .

    Note

    The following distinction between active and inactive workspace only applies when a Component Build Service is used:

    Since the development takes place in the inactive workspace, your changes become visible only for those persons who are using the same inactive workspace. This means that the developers working on the same DC (in the same compartment and configuration) see the changes directly after their release.