[
https://issues.jboss.org/browse/AS7-2262?page=com.atlassian.jira.plugin.s...
]
Darran Lofthouse commented on AS7-2262:
---------------------------------------
This is a deliberate design choice.
In stand alone mode the admin console and the JBoss Web container are running the same
process so a link across is possible (Personally I think even that is bad)
In admin mode there is now no direct relationship between the JBoss Web containers and the
process running the admin console, we can't even reliably a - detect if the user
accessing JBoss Web can connect to the admin console or b - identify the address they
should use.
Once users have moved to domain mode from standalone mode they should have enought
understanding of the topology of their own set up to connect directly themselves.
Link to Console missing from Welcome page
-----------------------------------------
Key: AS7-2262
URL:
https://issues.jboss.org/browse/AS7-2262
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.Alpha1
Reporter: Chuck Mosher
Assignee: Darran Lofthouse
Labels: eap6-ux
Attachments: ConsoleWithLinkScreenshot.png, ConsoleWithoutLinkScreenshot.png
If I start up the app server(s) using "bin/domain.sh", I can open up the
starting page @ localhost:8080/ but there is no link to open the console; only to examine
the documentation. The link to the Console is there when running standalone.sh. See
attached screenshots.
Options are: leave the link in there, but when clicked it will result in an error
message instructing the user they need to pick which instance they want to examine. Or,
point it to localhost:9990/.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira