Bug 798677
| Summary: | Operations are not immediately visible to the user and message is misleading (Usability) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Pavel Kralik <pkralik> | ||||||
| Component: | JON | Assignee: | tcunning | ||||||
| Status: | CLOSED NOTABUG | QA Contact: | |||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 5.2.0 GA | CC: | ldimaggi, mharvey, mvecera, soa-p-jira, vhalbert | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | i386 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-03-14 13:50:00 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 735475 | ||||||||
| Attachments: |
|
||||||||
|
Description
Pavel Kralik
2012-02-29 14:53:44 UTC
Marking this as urgent as this is a regression. The exception is in upper right corner as a white triangle next to availability icon in the the SOA-P server resource. I have not been able to reproduce this. I've tested with just the SOA plugin pack, and everything works fine there. If I install the EDS plugin pack instead, the Java Naming Provider is set to the following in Connection Settings : jnp://jboss:service=Naming Port:***CHANGE_ME*** If I change that to jnp://127.0.0.1:1099, everything seems to work fine. (10:58:09 AM) mazz: that ***CHANGE_ME*** is an indication that the port could not be auto-discovered (10:58:37 AM) mazz: rather than leave it null or empty, its set to that to indicate auto-discovery of the port failed and the user needs to manually set it Given this works fine with the SOA plugin pack, are the EDS plugins changing how the jnp URL is being discovered, and for some reason that is not working? Setting this to urgent since its blocking the JON3.0.1 release. This looks similar to an old JOPR bug: https://issues.jboss.org/browse/JOPR-322 Created attachment 569707 [details]
Annotated screenshot of the Operations tab for a VDB
The operations tab has changed from the 2.4.x version of JON where the tab showed all the available operations upon initial display. The 3.0.x version shows a blank screen with the text, "No items to show". The user may interpret this to mean the selected object has no available operations. (That's what happened to me.)
Actually, the user must click the New button (located way down at the bottom, where it may be overlooked). A drop-down of available operations is then presented to the user.
As a suggestion, perhaps change the text to read "To schedule an operation, click the New button below". Making the color of the New button stand out more might also help--it sort of fades into the background as is.
Created attachment 569986 [details]
The Operation tab exception
The bug is a yellow triangle in the right upper corner of the page.
Usability issue - will be covered in the docs - from Deon:
I updated three places in the docs, just to try to hit places people might look if they encountered that Operations tab question. This is all basically the same text.
* FAQ: http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Operations_Network/300/html/Frequently_Asked_Questions/index.html#id3333992
* "About" operations: http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Operations_Network/3.0/html/Setting_up_Monitoring_Alerts_and_Operations/Operations.html#op-scheds (looks like this is missing an image; I'll check and get that fixed)
* Scheduling operations (procedure): http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Operations_Network/3.0/html/Setting_up_Monitoring_Alerts_and_Operations/OperationProc.html#Creating-New-Operations
|