| Summary: | QE - Review SOA Platform 4.3.CP03 Release Notes | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | David Le Sage <dlesage> |
| Component: | Documentation | Assignee: | David Le Sage <dlesage> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.3 CP04 GA | ||
| Target Milestone: | --- | ||
| Target Release: | 4.3 CP04 GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-2032 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-05-18 04:29:03 UTC | Type: | Task |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
David Le Sage
2010-04-07 06:10:31 UTC
Need to rename all the docs from "CP03" to CP04".... Comments on doc here: http://downtown.englab.bne.redhat.com/drafts/JBoss_Enterprise_SOA_Platform/4.3.CP04/SOA_Release_Notes/ 3.1.4. JBoss Rules SOA-1914 https://jira.jboss.org/jira/browse/JBRULES-2421 If the user was running JBoss Rules 4.0.7 on an IBM virtual machine with JIT enabled, an .RuntimeDroolsExceptions would occur. This was because of a problem with regard to the way in which XXXX instanceof Object expressions were handled. The code in the org.drools.base.ValueType class which handles these expressions has been modified. As a result, JBoss Rules can now be run on IBM virtual machines with JIT enabled, without it causing exceptions. *** Comment: Note that SOA Platform 4.3 CP04 is not certified with the IBM JVM. ------------------------------ https://jira.jboss.org/jira/browse/SOA-1072 The example.base.build.xml used by jBPM examples has now been removed. It has previously caused some problems but is now no longer needed as examples are now being built with Maven rather than Ant. POM files have now been provided to test and run the examples. *** Comment: This bug is still open in CP04 - we need to list it as an unresolved issue, ------------------------------ https://jira.jboss.org/jira/browse/SOA-1463 A java.lang.Exception exception would occur if the user tried to run start, stop, create or destroy deployment operations from within the ESB Statistics level. In order to mitigate this problem, these operations are no longer available at this level. *** Comment: This bug is still open in CP04 - we need to list it as an unresolved issue, ------------------------------ https://jira.jboss.org/jira/browse/SOA-1998 *** Comment: See the JIRA - the description of this issue is changing. ------------------------------ Known Issues in This Release 4.1.1. JBoss Business Process Manager SOA-1948 https://jira.jboss.org/jira/browse/JBPM-2791 If there is a variable mapping between the Enterprise Service Bus and the Business Process Manager and the mapped value happens to be an empty string, then the result will be null. Also, if an object is persisted in an Oracle database with a field set to be an empty sting, the field value will also be null. Currently, there is no work-around for this problem. 4.1.2. JBoss Enterprise Application Platform SOA-1519 https://jira.jboss.org/jira/browse/JBPAPP-2893 There are problems with crash recovery when inflowing transactions are associated with multiple resource managers. As a consequence, a single XAResource can not be returned to drive the recovery for a given Xid. There is currently no work-around solution for this problem. *** Comment: Have we used this phrase in the past: "There is currently no work-around solution for this problem." ------------------------------ SOA-1529 https://jira.jboss.org/jira/browse/JBESB-3197 Currently, there is no service invoker load-balancing policy that prefers local end-point references. This would be of use if users do not want requests to be balanced between different instances in the clutter, as the latter makes debugging harder in the event of a failure. There is no work-around for this lack of functionality. *** This phrase "There is no work-around for this lack of functionality" sounds overly negative - why not simply say that the functionality is not supported by the Platform. David - some edits to make Last changes for release made. |