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;
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.
To enable deployment to a standalone server, change the EDS build.xml by replacing:
<property name="jboss_home" value="../jboss-as/"/>
with:
<condition property="jboss_home" value="../jboss-esb">
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 OpenOffice.org 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.