How to Rename, Move, and Delete Artifacts in the Applications Window

Table 2-12 describes the refactoring tasks that you can perform in the Applications window, along with known limitations. Carefully review these restrictions before using this feature.

Table 2-12 Refactoring Component Artifacts

Action	Applications Window Steps
Rename a service component or binding component artifact	Right-click a component file, and select Refactor > Rename. Note the following restrictions: Component implementation files (.bpel, .mplan, and so on) are not renamed when the component is renamed in the SOA Composite Editor. This does not cause issues. If you want to rename the implementation files to the same name, use the Applications window. You cannot rename human workflow, subprocess, or business rule components. Renaming or moving of business rule and human task artifacts is not supported. For example, you can rename a human task schema file (for example, HumanTaskPayload.xsd), but references to this XSD in the .task file are not updated. You cannot rename port types, operations, and elements in the WSDL and XSD editors. Do not rename a directory or artifact with blank spaces. Spaces in names lead to invalid references. You cannot rename SOA projects and composites.
Delete a service component, binding component, or BPEL subprocess artifact	Right-click a component file, and select Refactor > Delete. Note the following restrictions: When you delete an artifact in the Applications window, you are prompted with a message that includes a Show Usages option. When Show Usages is selected, any usages or references to the artifact from within files are displayed. When the Delete option is executed, only the subprocess file is deleted and no references are removed. Ensure that you first select Show Usages and manually remove references to the file to delete.
Move a service component or binding component to another folder	Right-click a component file, and select Refactor > Move. Note the following restrictions: Moving a database adapter artifact causes problems because the database adapter has many artifacts that are implicitly referenced by name and must be in the same directory. You cannot move component implementation files (.mplan, .bpel, .sbpel, .task, .rules, .spring, and so on) in the Applications window. However, these files can be renamed. Do not move a directory or artifact name with blank spaces. Spaces in names lead to invalid references. If you move an XSLT file, you lose capabilities such as the current expansion/scrolled state and which item was last selected in the XSLT Map Editor. This is because a NonDeployedFiles directory is created in the same folder as the XSLT file. This folder is the default place for test files, dictionary files, report files, DVM/XREF test support files, and so on. This directory is not moved if an XSLT file is moved because the folder contains files used for multiple XSLT files and there is no direct connection between the XSLT file and the file names that may be in the folder.

Action

Applications Window Steps

Rename a service component or binding component artifact

Right-click a component file, and select Refactor > Rename.

Note the following restrictions:

Component implementation files (.bpel, .mplan, and so on) are not renamed when the component is renamed in the SOA Composite Editor. This does not cause issues. If you want to rename the implementation files to the same name, use the Applications window.
You cannot rename human workflow, subprocess, or business rule components.
Renaming or moving of business rule and human task artifacts is not supported. For example, you can rename a human task schema file (for example, HumanTaskPayload.xsd), but references to this XSD in the .task file are not updated.
You cannot rename port types, operations, and elements in the WSDL and XSD editors.
Do not rename a directory or artifact with blank spaces. Spaces in names lead to invalid references.
You cannot rename SOA projects and composites.

Delete a service component, binding component, or BPEL subprocess artifact

Right-click a component file, and select Refactor > Delete.

Note the following restrictions:

When you delete an artifact in the Applications window, you are prompted with a message that includes a Show Usages option. When Show Usages is selected, any usages or references to the artifact from within files are displayed. When the Delete option is executed, only the subprocess file is deleted and no references are removed. Ensure that you first select Show Usages and manually remove references to the file to delete.

Move a service component or binding component to another folder

Right-click a component file, and select Refactor > Move.

Note the following restrictions:

Moving a database adapter artifact causes problems because the database adapter has many artifacts that are implicitly referenced by name and must be in the same directory.
You cannot move component implementation files (.mplan, .bpel, .sbpel, .task, .rules, .spring, and so on) in the Applications window. However, these files can be renamed.
Do not move a directory or artifact name with blank spaces. Spaces in names lead to invalid references.
If you move an XSLT file, you lose capabilities such as the current expansion/scrolled state and which item was last selected in the XSLT Map Editor. This is because a NonDeployedFiles directory is created in the same folder as the XSLT file. This folder is the default place for test files, dictionary files, report files, DVM/XREF test support files, and so on. This directory is not moved if an XSLT file is moved because the folder contains files used for multiple XSLT files and there is no direct connection between the XSLT file and the file names that may be in the folder.