Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <3745494.1182657025886.JavaMail.jira@brutus>
Date: Sat, 23 Jun 2007 20:50:25 -0700 (PDT)
From: "David Jencks (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Closed: (GERONIMO-3071) Impossible to tell what is actually
 started in the app client
In-Reply-To: <28048011.1175927312964.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/GERONIMO-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jencks closed GERONIMO-3071.
----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.0-M5)
                   2.0-M7

Server startup done in rev 550164. I guess we could think about doing something similar for deployments.... maybe another issue.

> Impossible to tell what is actually started in the app client
> -------------------------------------------------------------
>
>                 Key: GERONIMO-3071
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3071
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: application client
>    Affects Versions: 2.0-M5
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 2.0-M7
>
>
> We have a nifty monitor interface for the ConfigurationManagers so they can tell what they're up to.  We should use it to log what modules the app client is starting.  We should also do this for the server.... might be a separate issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.