BPEL Service Engine

For BPEL SE stop/restart issues, see JBI Management.

The following are known issues for the BPEL Service Engine:

• NetBeans Issue 148288

  If a BPEL project is deleted using the Delete Source option and a new project is then created that reuses the same name, the newly created project's Properties window cannot be opened.

  To work around this issue, stop and then restart the NetBeans IDE.

• Issue 555

  The BPEL Service Engine only creates connection pools and data sources for the Derby database. This functionality is available to assist developers and is not available for other databases or in a cluster. The BPEL Service Engine does create the persistence tables automatically for all supported databases, but only in standalone mode; this feature is not available in cluster mode. If you create connection pools, data sources, and tables before you install the BPEL Service Engine, it is possible to install the component with persistence enabled. Otherwise, installing to the cluster will fail.

  To work around the issue of tables not being automatically created, you can create the tables in standalone mode and then add the BPEL SE to the cluster. For more information, see Setting Up the BPEL Database in Configuring GlassFish ESB for Clustering.

• Issue 1802

  When an optional node is missing in the input message, an invalidVariable exception is thrown. This should not occur since the node is not required. This is due to an issue with BPEL case and message variables of the schema type.