Bug 824889

Summary: [eap6] outbound socket-bindings are not listed
Product: [Other] RHQ Project Reporter: Libor Zoubek <lzoubek>
Component: PluginsAssignee: Heiko W. Rupp <hrupp>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4CC: hrupp, theute
Target Milestone: ---   
Target Release: RHQ 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 825172 (view as bug list) Environment:
Last Closed: 2013-09-01 10:01:34 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 707223, 825172    

Description Libor Zoubek 2012-05-24 14:05:22 UTC
Description of problem: I am running EAP6 in standalone mode(full profile) and I cannot see 'Outbound remote' and 'Outbound local' socket bindings under 'standart-sockets' resource.


Version-Release number of selected component (if applicable):
JON ER3.1 EAP6.ER8
  
Actual results: only 'Inbound' socket bindings are listed/supported


Expected results:
mail-smtp (Outbound bindng) should be listed within all bindings, when adding a binding user should specify binding type. Also, other resources, their configuration refers to outbound bindings could be altered so UI provides radios/combos to pickup a binding. (Same way as it is in configuration of web connector and inbound bindings)

Comment 1 Heiko W. Rupp 2012-05-24 14:18:32 UTC
Workaround exists in that the user manually provides the name of the outbound binding in the text box.

Unfortunately we don't list them, so the user needs to find them e.g. via console

Comment 2 Heiko W. Rupp 2012-05-24 19:59:33 UTC
master 77d51c1

Comment 3 Heiko W. Rupp 2013-09-01 10:01:34 UTC
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.