You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Viet Hung Nguyen (JIRA)" <ji...@apache.org> on 2008/01/19 17:40:34 UTC
[jira] Created: (GERONIMO-3766) monitoring agent should be
separated into mejb, jmx, and jar utility classes
monitoring agent should be separated into mejb, jmx, and jar utility classes
----------------------------------------------------------------------------
Key: GERONIMO-3766
URL: https://issues.apache.org/jira/browse/GERONIMO-3766
Project: Geronimo
Issue Type: Sub-task
Security Level: public (Regular issues)
Components: monitoring
Environment: windows
Reporter: Viet Hung Nguyen
Assignee: Viet Hung Nguyen
Fix For: 2.1
in order to modularize the monitoring agent, I suggest the following breakdown:
agent-ejb <----which will contain anything MEJB related, so that only this will pull in OpenEJB
agent-jmx <----which will have the code for JMX connections
agent-jar <-----which will have the utility classes/functions that are used by both agent-ejb and agent-jmx
So, when packaging these JARs into an EAR,
agent-ejb + agent-jar will make up the agent MEJB plugin
agent-jmx + agent-jar will make up the agent JMX plugin
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3766) monitoring agent should be
separated into mejb, jmx, and jar utility classes
Posted by "Erik B. Craig (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erik B. Craig reassigned GERONIMO-3766:
---------------------------------------
Assignee: Erik B. Craig (was: Viet Hung Nguyen)
> monitoring agent should be separated into mejb, jmx, and jar utility classes
> ----------------------------------------------------------------------------
>
> Key: GERONIMO-3766
> URL: https://issues.apache.org/jira/browse/GERONIMO-3766
> Project: Geronimo
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: monitoring
> Environment: windows
> Reporter: Viet Hung Nguyen
> Assignee: Erik B. Craig
> Fix For: 2.1
>
> Attachments: geronimo-3766.patch
>
>
> in order to modularize the monitoring agent, I suggest the following breakdown:
> agent-ejb <----which will contain anything MEJB related, so that only this will pull in OpenEJB
> agent-jmx <----which will have the code for JMX connections
> agent-jar <-----which will have the utility classes/functions that are used by both agent-ejb and agent-jmx
> So, when packaging these JARs into an EAR,
> agent-ejb + agent-jar will make up the agent MEJB plugin
> agent-jmx + agent-jar will make up the agent JMX plugin
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3766) monitoring agent should be
separated into mejb, jmx, and jar utility classes
Posted by "Viet Hung Nguyen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Viet Hung Nguyen resolved GERONIMO-3766.
----------------------------------------
Resolution: Fixed
> monitoring agent should be separated into mejb, jmx, and jar utility classes
> ----------------------------------------------------------------------------
>
> Key: GERONIMO-3766
> URL: https://issues.apache.org/jira/browse/GERONIMO-3766
> Project: Geronimo
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: monitoring
> Environment: windows
> Reporter: Viet Hung Nguyen
> Assignee: Viet Hung Nguyen
> Fix For: 2.1
>
> Attachments: geronimo-3766.patch
>
>
> in order to modularize the monitoring agent, I suggest the following breakdown:
> agent-ejb <----which will contain anything MEJB related, so that only this will pull in OpenEJB
> agent-jmx <----which will have the code for JMX connections
> agent-jar <-----which will have the utility classes/functions that are used by both agent-ejb and agent-jmx
> So, when packaging these JARs into an EAR,
> agent-ejb + agent-jar will make up the agent MEJB plugin
> agent-jmx + agent-jar will make up the agent JMX plugin
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3766) monitoring agent should be
separated into mejb, jmx, and jar utility classes
Posted by "Erik B. Craig (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erik B. Craig reassigned GERONIMO-3766:
---------------------------------------
Assignee: Viet Hung Nguyen (was: Erik B. Craig)
Patch Committed revision 613704.
Sorry it took me a while, had to get my windows machine going, was having problems with your patch on linux.
Thanks viet
> monitoring agent should be separated into mejb, jmx, and jar utility classes
> ----------------------------------------------------------------------------
>
> Key: GERONIMO-3766
> URL: https://issues.apache.org/jira/browse/GERONIMO-3766
> Project: Geronimo
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: monitoring
> Environment: windows
> Reporter: Viet Hung Nguyen
> Assignee: Viet Hung Nguyen
> Fix For: 2.1
>
> Attachments: geronimo-3766.patch
>
>
> in order to modularize the monitoring agent, I suggest the following breakdown:
> agent-ejb <----which will contain anything MEJB related, so that only this will pull in OpenEJB
> agent-jmx <----which will have the code for JMX connections
> agent-jar <-----which will have the utility classes/functions that are used by both agent-ejb and agent-jmx
> So, when packaging these JARs into an EAR,
> agent-ejb + agent-jar will make up the agent MEJB plugin
> agent-jmx + agent-jar will make up the agent JMX plugin
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3766) monitoring agent should be
separated into mejb, jmx, and jar utility classes
Posted by "Viet Hung Nguyen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Viet Hung Nguyen updated GERONIMO-3766:
---------------------------------------
Attachment: geronimo-3766.patch
this patch needs the following commands to be executed with it:
svn delete applications/monitoring/agent-ejb/src/main/java/org/apache/geronimo/monitoring/MBeanHelper.java
svn delete applications/monitoring/agent-ejb/src/main/java/org/apache/geronimo/monitoring/snapshot/SnapshotConfigXMLBuilder.java
svn delete applications/monitoring/agent-ejb/src/main/java/org/apache/geronimo/monitoring/snapshot/SnapshotDBHelper.java
svn add applications/monitoring/agent-jar
> monitoring agent should be separated into mejb, jmx, and jar utility classes
> ----------------------------------------------------------------------------
>
> Key: GERONIMO-3766
> URL: https://issues.apache.org/jira/browse/GERONIMO-3766
> Project: Geronimo
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: monitoring
> Environment: windows
> Reporter: Viet Hung Nguyen
> Assignee: Viet Hung Nguyen
> Fix For: 2.1
>
> Attachments: geronimo-3766.patch
>
>
> in order to modularize the monitoring agent, I suggest the following breakdown:
> agent-ejb <----which will contain anything MEJB related, so that only this will pull in OpenEJB
> agent-jmx <----which will have the code for JMX connections
> agent-jar <-----which will have the utility classes/functions that are used by both agent-ejb and agent-jmx
> So, when packaging these JARs into an EAR,
> agent-ejb + agent-jar will make up the agent MEJB plugin
> agent-jmx + agent-jar will make up the agent JMX plugin
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.