+++ This bug was initially created as a clone of Bug #710230 +++

Created attachment 502598 [details]
Screen shot of admin-console showing confusion when invoking the Test Connection operation on a datasource

In some cases, the result of invoking an operation can be confused with the result of the actual operation. 

For example:

For a datasource resource, you can invoke the "Test Connection" operation. Once the operation has been submitted, the "Operation History" will indicate "Successful". This "Successful" message can easily be interrupted as the connection to the datasource was successful when in reality, the actual test of the datasource connection returned failed. 

This is confusing to operational admins looking at this UI to test a connection. In fact, this would mislead them to look at the wrong section and proceed thinking the connection has been obtained when it's not, and could possibly cause serious production ramifications. The UI should be re-worked and be more intuitive and clear.

--- Additional comment from ian.springer on 2011-07-27 14:36:02 EDT ---

The fix for this should be to improve the description of the 'testConnection' operation in the as5 plugin descriptor as follows:

    <operation name="testConnection" displayName="Test Connection" description="Test if a connection can be obtained - returns true if a connection was obtained, or false if not; NOTE: this operation will always return a status of Successful - the results of the operation must be inspected to see whether or not a connection was obtained">

--- Additional comment from ian.springer on 2011-07-28 12:59:14 EDT ---

Fixed in AdminConsole_EAP_5_1 branch - commit f1bb1cc.

This is not possible to verify directly - QE should just do an overall smoke test of the admin-console and make sure all the basics still work.

--- Additional comment from ian.springer on 2011-07-29 15:06:36 EDT ---

Fixed in master - commit 5f9ddb7.