Bug 990879 - Administration Console contains community branding
Summary: Administration Console contains community branding
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console
Version: 6.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ER2
: EAP 6.2.0
Assignee: Harald Pehl
QA Contact: Jakub Cechacek
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-01 07:07 UTC by Nikoleta Hlavickova
Modified: 2015-02-01 23:00 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
In JBoss EAP 6.1.1 the web management console displayed a favicon of AS7, not the Red Hat logo. This has now been resolved and the correct favicon now appears when in the web management console.
Clone Of:
Environment:
Last Closed: 2013-12-15 16:20:27 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
favicon.ico (97.72 KB, image/png)
2013-08-01 07:59 UTC, Nikoleta Hlavickova 		no flags Details
View All

Description Nikoleta Hlavickova 2013-08-01 07:07:12 UTC 
Description of problem:
There is AS7 icon in the header of Administration Console

How reproducible:
always

Steps to Reproduce:
1. start EAP 6.1.1 ER4
2. go to localhost:8080
3. click 'Administration Console'

Actual results:
AS7 icon

Expected results:
EAP6 icon
Comment 1 Heiko Braun 2013-08-01 07:50:18 UTC 
what "icon"?
Comment 2 Nikoleta Hlavickova 2013-08-01 07:59:11 UTC 
Created attachment 781467 [details]
favicon.ico

favicon.ico
Comment 3 Nikoleta Hlavickova 2013-08-01 10:43:51 UTC 
Regression against EAP 6.1.0 GA.
Comment 4 Aleksandar Kostadinov 2013-08-08 19:13:41 UTC 
This is a regression in 6.1.1
The problem was initially fixed with bug 899708

The issue is easy to fix and low risk so I'm proposing it to 6.1.1
Comment 6 Harald Pehl 2013-11-21 20:27:53 UTC 
Fixed for EAP 6.2
Comment 7 Nikoleta Hlavickova 2013-11-28 09:28:08 UTC 
AS7 favicon no longer present. Verified for EAP 6.2.0 CR3.
Note You need to log in before you can comment on or make changes to this bug.