Bug 780162 (SOA-2538)

Summary: Admin console - usability issue with editing deployed VDB
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Len DiMaggio <ldimaggi>
Component: Tooling, EDSAssignee: Len DiMaggio <ldimaggi>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.1.0.ER3   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-2538
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-09 21:00:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
not-editable-1.png
none
non-editable-2.png none

Description Len DiMaggio 2010-11-03 14:53:18 UTC 
project_key: SOA

The EDS Admin guide correctly states that:

"...Only Modelss "connection-jndi-name" can be modified using this tool by clicking on the "configuration" tab, all other properties are read-only..."

The problem is that the other text boxes displayed for the VDBs' other properties allow the user to select/highlight/scroll through text - this gives the impression that the data is editable, when it is not.

See attached screenshots - can these fields be displayed in a greyed-out mode when they are not editable?
Comment 1 Ted Jones 2010-11-03 16:19:23 UTC 
This is the behavior that comes with the admin console GUI. From a plugin standpoint we can make the fields read-only (which they are) and this makes them non-editable and a light grey color, but (as noted in the description of this Jira) the user can still place their cursor in the field and move it around. This is confusing and a Jira should be logged against Embedded Jopr, if there isn't already one.
Comment 2 Len DiMaggio 2010-11-04 02:25:04 UTC 
Attachment: Added: not-editable-1.png
Attachment: Added: non-editable-2.png
Comment 3 Len DiMaggio 2010-11-04 02:30:21 UTC 
Link: Added: This issue is a dependency of EMBJOPR-351
Comment 4 Ian Springer 2010-11-04 13:58:27 UTC 
The current behavior was intentional. I made the text inputs for read-only props readonly [1] instead of disabled [2], so that the text would still be selectable, in case the user wants to copy and paste the property value.

[1] http://www.w3schools.com/tags/att_input_readonly.asp
[2] http://www.w3schools.com/tags/att_input_disabled.asp