1. Developing SOA Applications with Oracle SOA Suite
  2. Completing Your Application
  3. Deploying SOA Composite Applications
  4. Patching Running Instances of a SOA Composite
  5. Using the SOA Patch Developer Mode in JDeveloper

Using the SOA Patch Developer Mode in JDeveloper

Use the SOA Patch Developer mode in Oracle JDeveloper to create a patch, containing fixes, for your deployed composite. The patch created in this mode can be applied to the currently deployed composite without changing the version number of the deployed composite. You can apply the patch to runtime even if the composite has running instances.

To use the SOA Patch Developer mode in JDeveloper:
  • If you already have your project open in JDeveloper, you need to switch to the SOA Patch Developer mode. Select Tools > Switch Roles > SOA Patch Developer from the Oracle JDeveloper menu bar.
    Tools > Switch Roles > SOA Patch Developer
    The Confirm Restart dialog appears.

    Confirm Restart dialog

    The dialog reminds you of the fact that you can make only limited edits in the SOA Patch Developer mode. Click OK to restart JDeveloper.

  • If you do not have Oracle JDeveloper open, start JDeveloper and select the SOA Patch Developer role in the Select Role dialog.
    Select Role dialog
After JDeveloper starts in the SOA Patch Developer mode, you’d notice that the composite editor has the SOA Patch mode label. This reminds you that you can only make edits that are compatible with the patch mode.

SOA Patch Mode appears on top right

Also, when you are editing a BPEL component, for example, the BPEL editor has the Patch mode label.

Patch Mode label appears on BPEL editor.

Only certain activities in the BPEL process are available for editing, the rest of them appear in gray. Also, notice that the Components window shows only those components that are available for use in the SOA Patch Developer mode. A number of properties appear in read-only mode.