Red Hat Training

A Red Hat training course is available for JBoss Enterprise SOA Platform

5.2.0 Release Notes

JBoss Enterprise SOA Platform 5

Changes in this Release


These notes document the changes found in this release of the JBoss Enterprise SOA Platform and the associated Enterprise Data Services product.
The JBoss Enterprise SOA Platform is a certified, tested, and supported environment for developing Enterprise Application Integration and SOA solutions.
For the latest version of these release notes please refer to the online copy available at

1. Overview

JBoss Enterprise SOA Platform is a certified, tested, and supported platform for developing Enterprise Application Integration and Service Oriented Architecture solutions.
It integrates a number of stable and scalable open source frameworks and solutions including Hibernate, Seam, JBoss Transactions, JBoss Clustering, the JBoss Application Server, and JBoss Enterprise Service Bus (ESB) to provide an infrastructure for enterprise SOA applications.
These community developed and enterprise certified and supported products have been combined and tested to provide a solid, robust, and scalable platform. Powered by legendary JBoss innovation and backed by Red Hat engineering and quality assurance, JBoss Enterprise SOA Platform is the platform of choice for a new generation of enterprise applications.

2. Frequently Asked Questions

Q: Where is the documentation?
Q: Where are the installation instructions?
Q: Which operating systems, Java Virtual Machines and database servers are supported?
Q: Why isn't the included Hypersonic database supported?
Q: What components are included in this product?
Q: What Technology Previews are included in this release?
Q: I'm running an earlier version. What problems might I have migrating to this version?
Q: Where can I find out more details about my support entitlements?
Q: Where do I go to obtain the source code?
Q: Where do I go to report errors in the documentation?
Q: What is JBoss Enterprise Data Services Platform ?
Q: Where can I get the source code?
Where is the documentation?
You can find the JBoss Enterprise SOA Platform documentation at
You can also find many articles about specific usecases at the Red Hat Customer Portal Knowledge Base:
Javadoc packages are available for download with the software at the Red Hat Customer Portal:


Red Hat recommends reading the Getting Started Guide first as it contains instructions for installing and configuring the product.
Where are the installation instructions?
Complete installation instructions for the JBoss Enterprise SOA Platform can be found in the SOA Getting Started Guide at
Which operating systems, Java Virtual Machines and database servers are supported?
For a complete list of the supported operating systems, Java Virtual Machines (JVMs) and database servers on which you can run the JBoss Enterprise SOA Platform, refer to
Why isn't the included Hypersonic database supported?
The default configuration includes the embedded Hypersonic database. This configuration is included only for evaluation and demonstration purposes. It is not supported in a production environment.
You can read about this at
The product now comes with H2, an in-memory reference database.
What components are included in this product?
The list of components can be found here:
What Technology Previews are included in this release?
The JBoss Enterprise SOA Platform includes the following Technology Preview features:
  • Support for the Apache Camel gateway
  • HornetQ
  • Support for SAML Tokens
  • ModeShape Disk Connector (only comes with EDS)
Technology Preview features are not supported, may not be functionally complete, and are not intended for production use. These features are included to provide customers with early access to upcoming product innovations, enabling them to test functionality and provide feedback during the development process.
Red Hat JBoss support will provide commercially reasonable efforts to resolve any reported issues that customers experience when using these features.
I'm running an earlier version. What problems might I have migrating to this version?
To find out about the common problems you may encounter as well as those issues that have been fixed in this release, refer to Section 4, “Known Issues” and Section 3, “Resolved Issues”
Where can I find out more details about my support entitlements?
Details of support policies can be found at the following URLs:
Where do I go to obtain the source code?
The source code for this and earlier JBoss Enterprise SOA Platform releases can be downloaded from the Red Hat Customer Portal at
Where do I go to report errors in the documentation?
Go to and choose to enter a new bug against the appropriate version of the JBoss SOA Platform.
What is JBoss Enterprise Data Services Platform ?
JBoss Enterprise Data Services Platform is a new product that extends the JBoss Enterprise SOA Platform to provides services for data virtualization, federation and integration.
JBoss Enterprise Data Services Platform includes the following features:
  • Open source Data Virtualization engine based on the Teiid community project.
  • Data Services tooling is Integrated with JBoss Developer Studio v4 (Eclipse 3.6).
  • Data caching and staging enhancements.
  • Metadata repository based on Modeshape community project.
  • Management through admin-console. Management and Monitoring through JBoss Operations Network.
  • Updated data source support.
You can find out more about JBoss Enterprise Data Services Platform at
Where can I get the source code?
The source code for this JBoss Enterprise Data Services Platform release can be downloaded from the Red Hat Customer Portal,

3. Resolved Issues

The following issues have been fixed in this release of the JBoss Enterprise SOA Platform.
The EDS plug-in would only display zero for every metric except for the Session Count. This was due to an issue with the way long-running queries were calculated. A code fix has been applied and, as a result, the correct metrics are now displayed.
Note that the 32-bit version of the Windows operating system is no longer a supported configuration. However, if you are continuing to run 32-bit Windows, it is worth being aware that with the default settings, very little memory in the process' address space for thread stack and other allocations (by default on Windows half of the address space is reserved for the system). This results in this type of error when you run SOA: java.lang.OutOfMemoryError: requested 842040 bytes for Chunk::new. Out of swap space? To fix this, you can decrease heap or configure a smaller thread stack size (such as -Xss128k). You could also try to change the partitioning of the process space.
When the user tried to deploy an ESB application from the Web Administration Console, they would encounter this error: "Failed to create Resource Quickstart_helloworld.esb - cause: java.lang.NullPointerException:null". This happened because the DeploymentName was null. It is now added automatically so users will no longer encounter this problem.
Due to a bug in the process method the HTTP request payload was not extracted to the console correctly. This has been fixed by a change to the method.
The bpel_management quick start's readme file contained incorrect information pertaining to a file name. This has now been corrected.
If the user redeploys the bpm_orchestration quick start multiple times, a race condition could occur, which lead to an java.lang.NoClassDefFoundError. A code fix has now been applied to address this. As a result, users will no longer see this error.
EDS now comes equipped with a quick start that demonstrates how to connect to and query Modeshape using the JCR API
The ESB still contained references to some old files, even though these had long been removed. These files were jbossesb-listener.xml and jbossesb-gateway.xml. The references have now been deleted.
Running a Join operation against two text files was extremely slow. This was because the join planning converted the bushy tree into a linear tree with a nested table join at the top which, in turn, forced a re-evaluation of one of the nested tables for each row. This has now been changed so that planning is more selective. As a result, running a Join operation against text files is now faster.
As the jcr*.jar was removed from SOA, the JCR Node mapping has now also been removed from jbpm.varmapping.xml. This was to prevent users from encountering java.lang.NoClassDefFoundError messages.
The BPEL engine installer has been enhanced so that it now supports the standalone server edition of the JBoss Enterprise SOA Platform.
If the user loaded and queried resultset caching when the production configuration was used with Teiid logging set to DEBUG and "set showplan debug" was active, a would occur. (This did not happen when queries were sourced by the cache.) The code has been changed so that users will no longer encounter this error when they use these settings when querying the resultset cache.
if the user deployed an ESB that contained an http-gateway as one of its ESB Service listeners and the archive name was less than four characters in length, an java.lang.StringIndexOutOfBoundsException would occur. This was because the code was trying to strip .war file extensions, which were not applicable in this case. The code has now been modified and, as a result, users will no longer encounter this exception. While profiling thesystem, users found that the org.jbpm.job.executor.JobExecutorThread.getWaitPeriod(int) and org.jbpm.job.executor.JobExecutorThread.getNextDueDate() methods were taking 2.58 seconds to run. This was due to the lack of an index on the query. This code has been fixed in the latest version of JBPM and, as a result, the methods now run more quickly.
If Wise encountered an error it could not handle, it would terminate the pipeline. A code fix has been applied so that exceptions are now handled in a consistent manner.
The main LOG4J configuration file, jboss-log4j.xml, used category elements for the logger definition. EDS cames with newer logger elements for particular logger definitions. Thus, if the customer installed EDS on the SOA-P he or she would have two different logger definitions in the jboss-log4j.xml file. These settings have now been unified so there is no longer any conflict between them.
The org.teiid.SECURITY log message has been enhanced to include the client's IP Address. This functionality was needed by some customers to meet security compliance requirements.
If a virtual procedure was previewed and then changed and saved, the preview would still gives the results from the previous transformation. Users had to close and then reopen JBoss Developer Studio and re-open to see the correct result. A coding patch has now been applied to fix this. Consequently, previews now update to reflect the correct results.
A previous change to the format of ClientTransaction to include a recovery flag broke the Wire protocol for older clients. A software change has now been applied that fixes this regression meaning that the Wire protocol will work once more.
The EDS Query Planner was not correctly resolving an alias within a "group by" clause. Within the plan a self-join was needed. A code update has fixed this problem and, as a result, aliases are now resolved correctly.
SOAPProxy threw a SAXParseException when the the WSDL was missing a soapAction and the message had attachment. A code fix has rectified this problem and, as a result, users will no longer encounter this exception.
An exception that occurred on rollback was obscuring the original exception on commit in DbPersistenceService.endTransaction(). As a result, users could not see the cause of the problem. An upgrade to the jBPM has fixed this issue so users can now see the errors.
The DefaultJMSPropertiesSetter did not filter out properties prefixed with JMS. It has been modified so that it now does so.
ContentBasedRouter failed when input data contained a byte-order mark (BOM). A new ESB BOMFilter action has been added to the enterprise service bus that is able ensure that byte-order marks can now be handled by the software so users will no longer see this failure. The BOMFilter action should be added to the action-chain in order to filter out byte order marks.
The refreshMatView no longer refreshed the data with "teiid-cache-manager-jboss-beans.xml" enabled in a single-node environment. A software upgrade has resolved this issue so the refreshMatView now works as expected when clustering is enabled.
Users can now enable push-down functions for specific data without having to code these in Java.
If the metadata returned for SQL is using an alias, the alias will be returned in the getColumnLabel() call, instead of getColumnName() method call. To turn on backwards compatibility support, and reverse that, add the useJDBC4ColumnNameAndLabelSemantics=false property to the connection URL.
If an internal materialized view was used, a node which had never had a copy of an IMV cache would return zero rows instead of querying the source to see if another node had cached the cluster. An upgrade to the software has now fixed this issue so users will find that the cache is interrogated correctly.
If an internal materialized view in was being used in EDS, a node which re-joined the cluster ignored the cluster's cache. This caused synchronisation issues. A patch has resolved this issue. As a result, nodes that rejoin the cluster now know to interrogate the cache.
In org.teiid.jdbc.StatementImpl, the batchedUpdates member would not be instantiated if there were no batched updates so clearBatch() would throw a null-pointer exception. A code fix has been applied to ensure it now instantiates correctly, so users will no longer encounter this exception.
HibernateStringUpdateLog getters always returned null. The code in the HibernateStringUpdateLog class has now been updated so that the correct result is returned.
There were two different and conflicting versions of Spring included with SOA. The redundant versions have been removed and replaced with a single, up-to-date version of the software.
Enhancements have been made to the way that Modeshape indexes are built, leading to performance improvements. The XSD and WSDL sequencers have also been added to the standard configuration.
If the user ran DeployProcessTask with the 'process' attribute, a NullPointerException would result. A code change has been applied to fix this issue. Consequently, users will no longer encounter this NullPointerException.
The text table was not checking for valid input. If a value had an invalid entry the entire file was read into memory. Readline logic has been added to read characters one at a time and validate them against an expected maximum value.
If the input file for a Freemarker transformation contained a name-space declaration, users would encounter an freemarker.core.NonStringException. A fix has been applied so that these name-spaces are now stripped out, meaning users will no longer see the error.
SpringSource Spring Framework 2.5.x before 2.5.6.SEC02, 2.5.7 before 2.5.7.SR01, and 3.0.x before 3.0.3 allows remote attackers to execute arbitrary code via an HTTP request containing class.classLoader.URLs[0]=jar: followed by a URL of a crafted .jar file. These files have, therefore, been updated. For more information, see
The BPEL-SB SAML example failed because of empty tag listeners. These have now been removed. As a result, this example now works correctly.
When the user attempted to query a relational model created from the Salesforce importer and the criteria returned zero rows, a Null Pointer Exception was encountered. A coding change has fixed this problem. As a result, an empty resultset is now given instead.
Users can now configure jBPM's asynchronous token functionality via XML settings.
VDB deployments through the AdminApi caused the application server to leak server sockets and listening threads, which could cause failures due to too many file handles being opened. A patch has been applied to fix this issue. As a result, server sockets and listening threads are no longer leaked so users will no longer encounter these failures.
Customers that built virtual databases that were accessed via ODBC would see the following Exception in the error logwhen the MAX_INT default was used: FunctionExecutionException. A code fix has been applied to resolve this issue.
Modeshape was responding slowly the first time users queried it for data. A coding change has been applied and it now responds more quickly.
Users would encounter this error when deploying an ESB archive (either zipped or exploded) through the JON console: java.lang.NoSuchMethodError. An update to the plug-in pack has fixed this error, so users can now deploy the archives without encountering problems.
The coding for "not disjunctive" conditional criteria was inaccurate. This has now been fixed so users can add these conditions and find that they will be interpreted accurately by the software.
Users would encounter a stack overflow error: java.lang.StackOverflowError. This was caused by a bug in the entry removal code. This code has now been rectified, so users will no longer see this problem. The expiration queue logic was updated at the same time to ensure that it is properly bounded.
Partially-qualified names were subject to visibility rules and could conflict with session-level tables. To rectify this, the runtime metadata was adjusted to resolve transformations as if it were the design-time metadata.
If the user tried to import ESB5 examples and the SOA run-time was misnamed, it would display a different level of error and, subsequently, less detail than if no SOA run-time was installed at all. The code has now been altered so that it displays the correct error level and details.
The setSpecificEPR initialised a type extension if none were already present, but this could not be done safely as it lead to concurrent failures. Any modifications to an EPR should only have been done at the construction point. The code has been changed so this is now the case.
Numerous SOA-P 5.1 quick starts included .settings and .project build files. These did not affect users but they have now been removed from the release to make it cleaner.
There was a performance degradation when BPEL processes consumed webservices. At the time, the BPEL engine was using ODE2.0 with Axis2. It has been upgraded to use JBossWS-native against ODE1.3.3 and the performance issue has gone.
If the user deployed a BPEL process on SOA-P 5.1 with the CXF stack configured, the WSDL would be invalid, leading to an java.lang.Exception: javax.wsdl.WSDLException. To fix this problem, the Saxon JARs found in the riftsaw.sar/lib were replaced with single a saxon version 9.2 jar. As a result, users will no longer encounter this exception.
User could not have both EBWS and SOAPProxy deployment types on the same deployment. This was because the EsbWebServiceDeployer created a list of publishers which was used to initialise the publishers property in the EsbDeployment, via EsbDeployer and EsbMetaData. Unfortunately EsbMetaData returned an unmodifiable list which Configuration.create nevertheless attempted to modify leading to a java.lang.UnsupportedOperationException. The code has now been changed and, as a result, users can now have two different deployment types on the same deployment.
A missing deployment descriptor file (deploy.xml) was causing deployments to fail. (A BPEL project must have a deployment descriptor file in order for the runtime to determine the process end-points.) This file has now been added to the software.
If the user entered an incorrect username or password at the BPEL Console log-in screen, no error message was displayed. This has now been changed so that the user is given feedback about supplying the wrong credentials.
Setting the key on process instances was causing instance variables to be misplaced. A code fix has now been applied so that variables are stored correctly.
The business_ruleservice_cep quick start's deployment descriptor's service element was missing a description attribute. This led to users encountering java.lang.IllegalStateExceptions. This has now been fixed so users will no longer encounter these exceptions.
The BPEL's engines termination handler (which controls forced termination of processes) was buggy and triggered java.lang.IllegalArgumentExceptions. The code has now been fixed so that the termination handler will work as expected.
Teiid Dynamic Portfolio example's readme file referred to wrong VDB name (weather) when it should have been dynamicportfolio. The readme file has now been amended to correct this mistake.
If the user ran ant runtest, a warning message would appear. This was due to a small coding error which has now been fixed. As a result, users will no longer see this error message.
The all, production, default server profiles are supported with EDS - but with the EMBEDDED server only. Do not try to install EDS into the standalone server as it is not a supported/certified configuration.
EDS procedures could not be resolved by the queryplanner if their models were marked as "not visible". This has now been fixed via a code change so procedures can now be marked as resolved even if their underlying models are invisible.
The file contained pre-set administrative roles. It should not have contained any roles when it was defined at install time. These roles have now been removed.
The build number was not being displayed in http://localhost:8080/jbossws/. A code fix has been applied so that users can now see which build they are using.
There were a number of broken links on this pace: http://localhost:8080/jbossws/. These have now been fixed.
The MVELMonitoringAction was storing the correct number of messages but each of them was just a duplicate of the very last message passed. This bug was caused by the reuse of the MonitoringPatternBean (which contains the message value) and which resulted in every enty in the list referring to the same instance. A code fix has been applied and, as a result, the messages are now stored correctly.
The jboss-as/samples/quickstarts/readme.txt file has been updated as its contents were out of date.
Users would sometimes encounter a PathNotFoundException when trying to check in a node. Updates to the Modeshape software have rectified this issue so users can now check in nodes without encountering any problems.
If the user tried to run the Salesforce connector, they would encounter a java.lang.NullPointerException. A code change has been applied to fix this issue so the Salesforce connector can now be run without the problem rearing.
Previously, there was no way to create an EDS web service connection from JBDS/Teiid Designer without a WSDL. This meant that a user could not develop and test a virtual database that invoked a non-SOAP HTTP service from the tooling without creating the ds.xml file manually and deploying it. Functionality has been enhanced so that users can now develop and test virtual databases more easily.
In the BPEL Editor's wizard tool, users could not create message correlation properties. This functionality has now been fixed.
The Smooks router was setting messages as non-persistent when, in fact, it should have been making them persistent. This was due to a bug in the router's code which has now been rectified As a result, messages are now set as persistent.
Users were unable to select the fault variable data type in faultHandler. To fix this problem, the type selection dialogue and properties sections have been refactored so that the filters are limited to only those types that are valid within the context of the selected variable or property.
OnMessage and OnAlarm had different context menus. This has been changed so that they both display the same menu, making for a more consistent user experience.
An error message appeared if the user clicked on a hyperlink before the JUDDI console had finished loading correctly. A code fix has been applied so that this message no longer appears and hyperlinks now work as expected.
The BPEL engine could not use the HP Systinet UDDI registry to register and locate processes. To fix this problem, an alternative JAX-WS transport has been added to the ESB codebase. As a result, users should now be able to use the HP Systinet Registry.
The Modeshape JBDC driver was reporting the wrong metadata for some of its columns: they were set as string, even when they were non-string types. A code fix has bbeen applied so that the correct metadata types are now set for these columns.
If an invalid filenamefilter was specified, a javax.jcr.PathNotFoundException was thrown, instead of a user-friendly exception explaining the configuration issue. A patch has been applied to Modeshape to rectify this issue.
If your JBoss BPM installation employs multiple business calendar property files and you had set a timer to repeat, the job executor would not know which business calendar properties file was in use when the timer was created. This update introduces a new column called CALENDARRESOURCE_ to the JBPM_JOB table that store the name of the business calendar properties resource used to create a timer. To avoid forcing unaffected customers to create the aforementioned column manually, this update is disabled by default. In order to enable it, replace the org/jbpm/job/Timer.hbm.xml mapping resource with org/jbpm/job/Timer.calendar.hbm.xml in the Hibernate configuration, after you have created the column.
An error message appeared in the log stating that BIRT failed to activate. Since BIRT is optional functionality that is disabled by default, this message was slightly misleading. It has been changed to more accurately state, "BIRT service has not been activated. Please check the DEBUG log for further details."
Resteasy plug-in information messages were incorrectly recorded in the log as errors. An upgrade to the software has fixed this issue and the messages are now classified correctly.
The BPEL Console was not providing users with feedback when authentication failed. It has now been enhanced to tell users this information.
The jboss-service.xml file was being parsed incorrectly. The parser was not ignoring white space. A code change has been applied and, as a result, this file is now parsed correctly.
The software was erratic in terms of support for transitions. It has been changed so that, if no condition is met, the default transition is taken. (The default transition is the first unconditional transition if there is one, or else the first conditional transition.) If only conditional ("guarded") transitions are available, and none of the conditions on the transitions evaluate to true, an exception will be thrown. Throwing an exception when none of the guarded transitions are viable informs the user that the process is incorrect.
If the user waited too long to log in at the Administration Console web page, an exception would occur. A time-out message is now displayed instead.
The jUDDI root_BusinessEntity was missing a number of BusinessServices which were exposed by the juddiv3.war, these being "valuesetcaching", "replication" and "valuesetvalidation". To fix this problem all of the exposed services are now registered in jUDDI and the unimplemeted services have been removed.
jUDDI Console queries were generating long log messages, filling the hard disk over time with useless requests. A size limitation has been added to the log messages and a generic "NumberFormatException in maxRows" message is now recorded, so all of the user input is no longer echoed.
No confirmation was required when the user deleted a user account from within the jUDDI Console. As a safeguard, a confirmation has now been added to protect against accidental erasure of accounts.
Whilst the servlet and console URLs exposed by SOA Server were password-protected, the URLs exposed by jUDDI v3.0 were not. When using the juddi-client-3.1.1 it is now possible to use WSTransport against a WebServices deployment which is protected by Basic Authentication.
Every time the form with publisher's details was submitted, the 'Max Service Per Business' value was overridden by the 'Max Bindings Per Service' value. A code fix has been applied so that this value is no longer over-ridden and thus now displays accurate data for the user.
Hovering the cursor over URLs in the jUDDI Console caused display boxes to change size. This was due to some stylesheet settings that turned fonts to bold when the user hovered the mouse over them, causing the text length and encapsulating box to change in shape. A change to the font setting in the stylesheet has fixed this so the text and box no longer change in size
When the user tried to use the JUDDI Console after the session had already expired, a Javascript alert was displayed. This alert contained the source code of the login page. A code fix has now been applied so that this alert dialogue box no longer appears if the session times out.
The JUDDI Console would misplace title attributes in the wrong area. This has been fixed so that the attributes are now displayed correctly.
The publisher portlet's action buttons have now been disabled for non-administrator users.
There was no easy way to log out of the JUDDI console and log back in. A logout link has now been added.
The EJBProcessor looked for remote EJBs at application startup. If the look-up failed, the EJBProcessor threw an exception, meaning that the application could not start. The code, simply did a look-up at the outset and reused the proxy to invoke methods on the target EJB. It has now been changed so that it can handle remoted EJBs. As a result, no exception is encountered and the application starts correctly.

4. Known Issues

The following issues are known to exist in this release of the JBoss Enterprise SOA Platform and will be fixed in a subsequent release.
Note that Ingres is not yet a supported or certified platform for SOA or EDS. A current list of the supported platforms can be found here:
JBoss Developer Studio version 4.1.1 is the companion tooling distribution to SOA and EDS versions 5.2. Please be sure to install this version of Developer Studio when using SOA or EDS 5.2. JBoss Developer Studio can be obtained from the Red Hat Customer Portal at Please download and install Developer Studio 4.1.1.
If you deploy a VDB containing a Data Role on a JBDS 4.1.0 VDB whilst you are connected to EDS 5.1, you will see an error message which states "Attribute 'allow-create-temporary-tables' enabled is not allowed to appear in element 'data-role" There was a change in the Teiid VDB's vdb.xml schema which added an option that makes it incompatible with the SOA 5.1 server. Therefore, you cannot deploy these files to that version of the SOA server.
If your server is working at high capacity, you may encounter 'AcquireInstanceLock' exceptions. These have no impact as those jobs which did not obtain the 'Instance Lock' are sent to the ODE_JOB table from where they will be retried until they process successfully.
The Drools runtime definition must reference the ${SOA-P 5.0} top-level directory, not the ${SOA-P 5.0}/jboss-as/server/default/deploy/jbrules.esb or the user will encounter a java.lang.NoClassDefFoundError when the project is run.
In order to use XA transactions with a PostgreSQL 8.4 backing store, you will need to change the default value of max_prepare_transactions in your postgresql.conf file. As of 8.4, the default setting for this property is 0. Please choose a number of prepared transactions equal to or greater the maximum number of connections specified in your postgresql.conf - so that there is a transaction available per connection.
The Dynapartner quick start fails to invoke dynamically-assigned endpoint references. Currently there is a bug in the BPEL engine where the EPR is essentially cached with the partner link, so any subsequent changes after the first invoke do not take effect As a workaround, users should set the UDDI lookup/registration properties to false. It will then work. If the workaround is not employed, the user will not be able to use the UDDI register to look up partner web-services from a BPEL process, but will still be able to call local/remote web-services by including the WSDL of the service in the Java archive deployed on the server. Also, If a user wants to reuse a BPEL process as a web-service he or she must manually register the end-point in the UDDI as the engine will not do it automatically.
There is a backwards compatibility issue as Smooks no longer contains org.milyn.smooks.edi.SmooksEDIParser class. If you are still using an old configuration, you must change it to use EDIReader ( or update the configuration to this: <edi:reader mappingModel="parse/edi-to-xml-order-mapping.xml" />
jUDDI 3.1 allows you to specify entity keys but this is not compatible with the version from 3.0. To make the formats compatible, define the following properties in deploy/riftsaw.sar/ bpelServiceKeyFormat businessKeyFormat bindingKeyFormat The Riftsaw business key in file deploy/jbossesb-registry.sar/juddi_custom_install_data/riftsaw_BusinessEntity.xml must be updated according to the businessKeyFormat property. The Riftsaw business key in file deploy/jbossesb-registry.sar/juddi_custom_install_data/riftsaw_BusinessEntity.xml must be updated according to the businessKeyFormat property.
When using a DB2 9.7 database to retrieve blobs/clobs, you may run into the issue where DB2 hasn't fully materialized the blobs/clobs in your query. This was not an issue in DB2 9.1. Therefore, to access blobs/clobs in a DB2 9.7 database using EDS you need to append the following to your connection url: :driverType=4;fullyMaterializeLobData=true;fullyMaterializeInputStreams=true;progressiveStreaming=2;progresssiveLocators=2;
If the user tried to expand a Modeshape sequencer by clicking on its arrow in the Administration Console, a null pointer exception will appear in the log.
jBPM may fail to start if MySQL is used as its backend database. This is due to a problem with the MySQL cluster configuration. To work around the problem, increase the value of the MaxNoOfAttributes property.
Teradata lobs can only be read from an embedded client using with the default option to use the calling thread and in single threaded mode (transactional or userRequestSourceConcurrency=1). Usage of Teradata lobs under any other configuration is unlikely to work.
Users may encounter warning messages if the set Rules project code compatibility to JBoss Rules 4.x. These are caused by examples that use pre-5.x API calls and are intended to discourage users from accessing the internal API. If, however, you do need to access the API, you can turn them off by going to Windows - Preferences - JBoss Rules and setting the set internal classes to accessible.
Be aware that if you install CXF into SOA-P, it replaces the Native WS in all server configurations. You cannot just change a single configuration since CXF and Native WS cannot coexist in shared libraries. Therefore you must decide whether the whole installation will use CXF or NativeWS. It is not possible to have both CXF and WS Native at the same time.
The SOA Platform Server will fail if there is a space character in directory tree string. This is caused by a WAR file supplied with the ESB. The WAR file contains an XML catalogue and it is the resolution of the entries in this catalogue that causes the issue.
You cannot deploy a single web service to two different URLs. When the WAR file is deployed, the service will be accessible via only one URL. This is different to the behaviour exhibited when the system is configured to use the native web service.
The quick starts include Hornet/Q queue deployment files (hornetq-jms.xml), although Hornet/Q is not yet supported. There is no functional impact from having the extraneous files present as the quick starts use whichever JMS is active (by default, this is JBoss Messaging.)
The JackrabbitXmlNodeTypeRegistrationTest fails on the Solaris 9 platform. This is caused by the presence of an invalid character in an XML file which results in the system being unable to parse it. This could be encountered whenever any XML file is loaded. To fix this issue, you must edit the file in question to remove any invalid characters. An easy way to verify that XML files are valid is to open them in your web browser. If there is a problem, the browser will identify it for you.
JBoss Rules does not support forward- or backward-compatability of any serialised formats. Versions of packages created in JBoss Rules 4.x are binary-incompatible with versions created in JBoss Rules 5.x For this reason the rebuild button was added to Rules. It is also why the client version must match the JBoss Rules version. To work around this problem, you must run with the same versions of the JARs on both the client and the server and, if you add news JARs to the server (regardless of the release) you must rebuild the packages.
Importing an Microsoft Excel spreadsheet into in a Knowledge Base will cause an exception to be thrown ( StringIndexOutOfBoundsException ) if the spreadsheet was created in Excel 95 or earlier. This is because of an issue in the JXL library which is used to handle these files. This can be worked around by opening and saving the spreadsheet in Microsoft Excel 97 or greater or with Calc. This will be fixed in a future release.
The user will encounter an org.jboss.messaging.util.ExceptionUtil if they use separate databases in a cluster. This is because the use of separate databases results in duplicated channel ids. Always configure JBoss Message to use a shared database if clustering. If you do so, you will not see this exception.
When the Web Service proxy is used to invoke any method it will return the response as provided by the target webservice. In some instances the target webservice may return a response which is not valid within the invoking context. The Web Service proxy does not sanitise these responses and will pass the response back to the caller.

5. New Features

The following are available in this release:
EDS now has the ability to constrain the allowed cipher suites negotiated during a SSL connection
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 pluggable password encryption/decryption mechanism for the ESB's FilePassword. This is similar to how the FilePassword mechanism works in the JaasSecurityDomain mbean, but you can uses your own pluggable password encryption mechanism. For instance, in the jbossesb-properties, you can specify property name="" value="testKeystorePassword" using your plugin implementation. This improves on the old implementation which was hard-coded and not pluggable.
The BPEL jbt.bpel.facet.core project facet id has been deprecated in favour of bpel.facet.core in the BPEL editor plug-in but backward compatibility has been retained. To facilitate this, support for the new facet id has been added to the plug-in and also to the SOA-P 5.2 (and beyond) run-times.
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.