Google's summer of code project - Improve the JMX support within Apache Tomcat

[Мартин Бенков <ma...@gmail.com>]

Hello,

I'm a student in the university of Sofia and I'm willing to attend Google's
summer of code this year. The project I'm interested in is - *Improve the
JMX support within Apache Tomcat*. Is this project with high priority or
should I choose a more important one.

Now I have about 3 years experience with Java and year and a half
professional experience with J2EE(I've worked in Sap Labs Bulgaria in the
team responsible for the JMS implementation). During this time I've looked
at several mbeans and I'm familiar with the main idea of the JMX.

Currently I don't know what the state of the project is but as far as the
description of the task informs me the main goal is to enlist all attributes
in the JMX infrastructure document them and choose which of them should be
read only.

My proposal is something like - first get on board with the community, then
explore the current state of the JMX integration in the Tomcat(see best
practices to add attributes in the JMX), discuss which are the read only
properties and imlement them.

I'm looking forward to hearing from you.

Regards,
Martin Benkov

Re: Google's summer of code project - Improve the JMX support within Apache Tomcat

[Mark Thomas <ma...@apache.org>]

Mark Thomas wrote:
> Мартин Бенков wrote:
>> Hello,
> 
> Martin,
> 
> Welcome to the Tomcat community.
> 
>> I'm a student in the university of Sofia and I'm willing to attend Google's
>> summer of code this year. The project I'm interested in is - *Improve the
>> JMX support within Apache Tomcat*. Is this project with high priority or
>> should I choose a more important one.
> 
> The JMX project stands as much chance as any other. If we do need to apply
> limits then it will be on the basis of the quality of the applications.
> 
>> Now I have about 3 years experience with Java and year and a half
>> professional experience with J2EE(I've worked in Sap Labs Bulgaria in the
>> team responsible for the JMS implementation). During this time I've looked
>> at several mbeans and I'm familiar with the main idea of the JMX.
>>
>> Currently I don't know what the state of the project is but as far as the
>> description of the task informs me the main goal is to enlist all attributes
>> in the JMX infrastructure document them and choose which of them should be
>> read only.
>>
>> My proposal is something like - first get on board with the community, then
>> explore the current state of the JMX integration in the Tomcat(see best
>> practices to add attributes in the JMX), discuss which are the read only
>> properties and imlement them.
> 
> Great. Building Tomcat locally is probably a good place to start. You should be
> using the one in http://svn.eu.apache.org/repos/asf/tomcat/trunk
> 
> Once you have Tomcat building, I suggest you pick a current bug and try and fix
> it. This will help you to get familiar with the code base. The effort won't be
> wasted. The JMX project will require changes all over the codebase so the more
> familiar you are the better. And you will have fixed a Tomcat bug which is
> always a good thing :)
> 
> If you need help with any of this or a suggestion as to which bug might be a
> good one to start with, just e-mail the dev list.

One more thing: Make sure you get your application in to GSOC as soon as
possible - even if it is just a draft - as Google are trying to judge numbers.

Mark

> 
>> I'm looking forward to hearing from you.
>>
>> Regards,
>> Martin Benkov
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org

Re: Google's summer of code project - Improve the JMX support within Apache Tomcat

[Mark Thomas <ma...@apache.org>]

Мартин Бенков wrote:
> Hello,

Martin,

Welcome to the Tomcat community.

> I'm a student in the university of Sofia and I'm willing to attend Google's
> summer of code this year. The project I'm interested in is - *Improve the
> JMX support within Apache Tomcat*. Is this project with high priority or
> should I choose a more important one.

The JMX project stands as much chance as any other. If we do need to apply
limits then it will be on the basis of the quality of the applications.

> Now I have about 3 years experience with Java and year and a half
> professional experience with J2EE(I've worked in Sap Labs Bulgaria in the
> team responsible for the JMS implementation). During this time I've looked
> at several mbeans and I'm familiar with the main idea of the JMX.
> 
> Currently I don't know what the state of the project is but as far as the
> description of the task informs me the main goal is to enlist all attributes
> in the JMX infrastructure document them and choose which of them should be
> read only.
> 
> My proposal is something like - first get on board with the community, then
> explore the current state of the JMX integration in the Tomcat(see best
> practices to add attributes in the JMX), discuss which are the read only
> properties and imlement them.

Great. Building Tomcat locally is probably a good place to start. You should be
using the one in http://svn.eu.apache.org/repos/asf/tomcat/trunk

Once you have Tomcat building, I suggest you pick a current bug and try and fix
it. This will help you to get familiar with the code base. The effort won't be
wasted. The JMX project will require changes all over the codebase so the more
familiar you are the better. And you will have fixed a Tomcat bug which is
always a good thing :)

If you need help with any of this or a suggestion as to which bug might be a
good one to start with, just e-mail the dev list.

> I'm looking forward to hearing from you.
> 
> Regards,
> Martin Benkov
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org