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.

• NetBeans Issue 178853

  When using the new feature that allows you to map a partner link role node to a variable or EndpointReferenceType node, the generated pseudoComp element has an incorrect namespace defined in its type and qName attributes.

  To work around this issue, modify the namespace prefixes for type and qName to the prefix for http://schemas.xmlsoap.org/ws/2004/08/addressing.

• Issue 2592

  When you configure a BPEL process to send a callback address, it involves copying a partner link value to a variable. If this address is intended for a service that is not within the same JVM, the associated partner link port type, messages, binding, and services all need to be defined in one WSDL document.

• Issue 2681

  Failover does not work correctly when validation is enabled for the BPEL Service Engine.

  To work around this issue, disable validation in the service engine runtime properties.

• NetBeans Issue 167638

  If you save changes on the JavaScript Editor using the Save button, an IllegalStateException occurs.

  To work around this issue, save the BPEL process after any changes are made on the JavaScript Editor.

• Deployment fails for BPEL projects if the BPEL Service Engine has monitoring enabled but has persistence disabled in its runtime properties.

  To work around this issue, enable persistence for the BPEL Service Engine if monitoring is enabled.

• When implemented with the Database BC, the BPEL Service Engine generates a NullPointerException after shutting down the Database BC.