Hi Jeff,

This organization doesn't quite make sense to me.

I can see something like


>App Server
info
java system info
server logs
shutdown
thread pools
web server
ejb server
jms server
DB info
DB Manager

>Resources
Jar aliases
Respository
JMS Resources (why not under applications??)
Database pools (again, why not under applications?)

>Applications
Deploy New
Plan Creator
Plugins
System Modules
Application Ears
Web App Wars
Ejb Jars
J2CA Connectors
App Clients

>Security
Security Realms
Keystores
Certificate Authrotiry
Users and Groups (this is not useful for real apps since it only looks at the default properties file security realm which hopefully no one will ever use in production)

>Monitoring
JMX Viewer
JNDI Viewere
Classloader viewer
Dependency Viewer
Monitoring
LDAP Viewer (We don't install ldap by default, and this is a pretty weak app compared to e.g. ApacheDS Studio)

I'm not sure about
Apache HTTP since these are instructions that IIUC don't do anything in the actual geronimo server. I really don't know where to put them.

I've tried to put stuff in better categories (e.g. j2ca connectors are applications) and to put the most important/ most likely to be used choices first.

Since there is some question (at least from me) about a good order I'm not sure if this should go in 2.2. If you like what I suggest and no one else objects I guess I'm OK with it but I'd also be OK with just rearranging stuff in 3.0.

thanks
david jencks

On Nov 19, 2009, at 8:31 PM, chi runhua wrote:

I'm also attaching the snapshot of updated navigation layout for your reference.


Jeff C

On Fri, Nov 20, 2009 at 12:25 PM, chi runhua <[email protected]> wrote:
Hi devs,

With the help of Shawn, we realized it's pretty easy to re- categorize the items in navigation pane because of flexible architecture of Geronimo plugin system. Just wonder if we could include the updates to the coming G2.2 release as a transitional stage of Console improvement task in G3.0. Here is how I did it.

Locate all the AdminConsoleExtensionGBean in plan.xml of each portlet and change the pageTitle attribute. For example,
      Update
<gbean name="JMSServerManager" class="org.apache.geronimo.pluto.AdminConsoleExtensionGBean">
           <attribute name="pageTitle">Server/JMS Server</attribute>
           ...
      To
<gbean name="JMSServerManager" class="org.apache.geronimo.pluto.AdminConsoleExtensionGBean"> <attribute name="pageTitle">Application Server/JMS Server</attribute>
           ...

The new category is nearly identical with the proposal in https://issues.apache.org/jira/browse/GERONIMO-4950 . I've built the server assembly locally and looks everything just works fine.

If you think it's acceptable, I'll open a new JIRA and submit the patches for 2.2 branch&trunk later.

Any comments?


Jeff C

<NavigationItem_regroup.png>

Reply via email to