BPEL
Fully supported WS-BPEL 2.0 runtime engine and developer tooling, including documentation and quickstarts.
The ModeShape Disk Connector is being added to 5.2 for Tech Preview
EDS can now process the relational queries underlying XML document generation in parallel. This parallel processing results in improved performance when the system is populating independent sibling elements.
Users who upgraded to MySQL version 5.5 and tried to run SOA-P encountered an error message that stated, "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE=InnoDB'".
This was caused by the fact that 'TYPE=InnoDB' had been changed to 'ENGINE=InnoDB'. To rectify this issue, the BPEL engine has been updated to support the amended syntax.
There is now a data role injection point at which a different implementation can be used for role validation. This interface provides full control of the validation, instead of receiving SQL to validate.
A row-level security model to restrict user access to sensitive information has been added. Previously, this was not available for system- or user-defined functions, just for tables. The system is available when the SOA Platform is configured to use XACML authorisation.
A dynamic set of datasources are accessed through EDS. Each data source is represented as a different model within the VDB. Sometimes some data sources were not be available at the time Teiid executed the translator's getMetadata() method. A new method (markDataSourceAvailable(jndi name)) has been added that makes EDS read the appropriate translator's metadata when a new data source is detected.
A hook for the adminshell has also been added.
All of the Teiid examples have been converted to quickstarts in SOA 5.2. This makes them consistent with all of the other examples included with the SOA Platform.
The HttpGatewayServlet can now extract certificates from requests in addition to extracting of basic authentication details (username and password) via HttpServletSecUtil.
To make it easier for users to develop applications that interact with the ESB via the ESB API, all of the required JARs have now been relocated to a central jboss-as/client directory. Previously, they had been scattered, requiring the user to add them to the class-path individually.