Bug 779459 (SOA-1844)

Summary: Gateway listener's traits not displayed in admin console
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Jaroslaw Kijanowski <kijanowski>
Component: Monitoring and ManagementAssignee: Kevin Conner <kevin.conner>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.0.0 ER7   
Target Milestone: ---   
Target Release: FUTURE   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1844
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-08 20:13:18 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
count5.png
none
count6.png none

Description Jaroslaw Kijanowski 2010-01-18 09:09:55 UTC 
Date of First Response: 2010-01-18 09:15:03
project_key: SOA

Following traits are present for esb aware listeners but not for gateways:

MEP
Service Category
Service Description
Service Name
Start Date


Besides that I could imagine that it might be helpful when names of the associated queues would be displayed as well - in form of URLs pointing to the corresponding resources.
Comment 1 Kevin Conner 2010-01-18 14:15:03 UTC 
These traits are specific to the listeners, do we really want them duplicated in the gateways?
Comment 2 Jaroslaw Kijanowski 2010-01-19 09:37:51 UTC 
Aren't these traits specific to a service? Maybe the service level would be a better place?

Moreover, in the jopr console, it looks fine to have not these traits displayed for the gateway, however in the JON console "-- nothing found --" is displayed (screen attached).

What about the queue names, would this make sense?
Comment 3 Jaroslaw Kijanowski 2010-01-19 09:38:27 UTC 
Attachment: Added: count5.png
Attachment: Added: count6.png
Comment 4 Anne-Louise Tangring 2010-09-21 19:11:38 UTC 
In SOA 5.1.0 triage, we decided that Kevin will close this issue.