Description of problem: See https://issues.jboss.org/browse/RIFTSAW-470 Version-Release number of selected component (if applicable): 2.3.2.Final
The solution to this problem is to convert those Native SQL into HQL, which is in the bpaf-explore project (a subproject that is consumed by the bpm-console and riftsaw). It has been fixed into the RiftSaw 2.3.2 version.
GSS considers this a high priority, please.
Fix exists in Riftsaw 2.3.4.Final which SOA-P 5.3.0 is using.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: When using Riftsaw, problems would arise when attempting to access http://servername:8080/bpel-console/. An exception would be thrown which read "Failed to execute query". This was solved by converting those Native SQL into HQL, which is in the bpaf-explore project (a subproject that is consumed by the bpm-console and Riftsaw). It has been fixed in Riftsaw 2.3.2.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -When using Riftsaw, problems would arise when attempting to access http://servername:8080/bpel-console/. An exception would be thrown which read "Failed to execute query". This was solved by converting those Native SQL into HQL, which is in the bpaf-explore project (a subproject that is consumed by the bpm-console and Riftsaw). It has been fixed in Riftsaw 2.3.2.+Problems would arise when attempting to access the BPEL Console at http://servername:8080/bpel-console/ if Oracle 11G was the database. An exception would be thrown which read "Failed to execute query". This was solved by converting native SQL commands into HQL. It has been fixed in Riftsaw 2.3.2.
Verified in SOA-P 5.3.0.ER3
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.