Date of First Response: 2009-12-18 12:25:25
project_key: SOA

A few screenshots will be attached.

Issues:
1)  There are a variety of fonts in use in the console
2)   The SOA Platform font choice is particularly awkward (is it Comic Sans?)
3)  "JUDDI" should be "jUDDI" (http://ws.apache.org/juddi/) - in this case, we can just call it "Registry"
4) "JBossWs" should be "JBossWS"  (http://labs.jboss.com/jbossws/) - in this case, we can just call it "Web Services" or "WS"
5) The use of DIVs and Javascript for the individual consoles make it difficult to find the direct URLs to the console - it is confusing.  

Look at the JBossWs console as an example (screenshots will be uploaded).
The end-user first opens their browser and types in "http://localhost:8080"
Then the select JBossWs link, the url changes to "http://localhost:8080/#" this means I am not sure where I navigated to, but the fact that I need to login each time to each of the menu-items does tell me that I went some place else.
The user then has to click on "View a list of deployed services" and then the actual WS endpoint.

What I wanted (as the user) was the URL to the actual WSDL for my WS endpoint, so I can feed that WSDL back into Visual Studio or soapUI, in order to get the WSDL URL, I need to copy & paste it from the body of the WSDL (near th body) OR I need to right-click and choose Open Link in New Tab.

Bottom line, I prefer the SOA-P 4.3 way of handling this navigation.  The DIV which acts like an IFrame hides too many of the important details like the actual URL associated with each individual web app/console.   The colors & fonts do not match up well so it is a bit disjointed, obviously different consoles.