openjmx-devel Mailing List for OpenJMX (Page 4)

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Carlos Quiroz wrote:

>>Carlos Quiroz wrote:
>>
>[...]
> 
>Perhaps a better documentation of this would be good, but I'm ok with the 
>feature
>
I am working on it :-)

Jerome.

>Carlos Quiroz wrote:
>
>>On Sunday 03 February 2002 20:43, J=E9r=F4me BERNARD wrote:
>>
>>>What bug do you have?
>>>
>>>I think there a no changes planned in XDoclet. We will just add an exa=
mple
>>>and that's it.
>>>So if there is still something wrong, let me know and I will fix it AS=
AP.
>>>
>>Again with the extend=3D"XXX" which is expanded on the MBeanDescription=
 class=20
>>to extends XXXMBeanDescription
>>
>>Now thinking a second time about it is maybe be design, is it? But assu=
mes=20
>>that your extended interface also has a Description class
>>
>Yes. This is a design reason. I supposed that the class which would be=20
>extended would be a MBeanDescription class too. This is also because I=20
>found it easier to have only one extends attribute on the jmx:mbean tag=20
>rather than having two (one for the interface and one for the=20
>description) because I think that most of the cases will have a=20
>description extending another one.
>
>What would you prefer/propose to do?
Hi I think is Ok. From the design point of view it sounds very reasonable=
=2E=20
Perhaps a better documentation of this would be good, but I'm ok with the=
=20
feature

>
>Jerome.
>
>
>
>
>_______________________________________________
>Openjmx-devel mailing list
>Ope...@li...
>https://lists.sourceforge.net/lists/listinfo/openjmx-devel
>

Carlos Quiroz wrote:

>On Sunday 03 February 2002 20:43, J=E9r=F4me BERNARD wrote:
>
>>What bug do you have?
>>
>>I think there a no changes planned in XDoclet. We will just add an exam=
ple
>>and that's it.
>>So if there is still something wrong, let me know and I will fix it ASA=
P.
>>
>Again with the extend=3D"XXX" which is expanded on the MBeanDescription =
class=20
>to extends XXXMBeanDescription
>
>Now thinking a second time about it is maybe be design, is it? But assum=
es=20
>that your extended interface also has a Description class
>
Yes. This is a design reason. I supposed that the class which would be=20
extended would be a MBeanDescription class too. This is also because I=20
found it easier to have only one extends attribute on the jmx:mbean tag=20
rather than having two (one for the interface and one for the=20
description) because I think that most of the cases will have a=20
description extending another one.

What would you prefer/propose to do?

Jerome.

On Sunday 03 February 2002 20:43, J=E9r=F4me BERNARD wrote:
> What bug do you have?
>
> I think there a no changes planned in XDoclet. We will just add an exam=
ple
> and that's it.
> So if there is still something wrong, let me know and I will fix it ASA=
P.
Again with the extend=3D"XXX" which is expanded on the MBeanDescription c=
lass=20
to extends XXXMBeanDescription

Now thinking a second time about it is maybe be design, is it? But assume=
s=20
that your extended interface also has a Description class

Regards

>
> Regards,
> Jerome.
>
> ----- Original Message -----
> From: "Carlos Quiroz" <car...@we...>
> To: <ope...@li...>
> Sent: Sunday, February 03, 2002 7:11 PM
> Subject: Re: [Openjmx-devel] [Fwd: JMX work, and CustomerBMPBean]
>
> > On Friday 01 February 2002 17:06, J=E9r=F4me BERNARD wrote:
> > Hi J=E9r=F4me
> >
> > I still have a bug with this but now it extends the
> > MBeanClass+MBeanDescriptionAdapter
> >
> > Regards
> >
> > P.S. I will wait for this to release
>
> _______________________________________________
> Openjmx-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openjmx-devel

What bug do you have?

I think there a no changes planned in XDoclet. We will just add an example
and that's it.
So if there is still something wrong, let me know and I will fix it ASAP.

Regards,
Jerome.

----- Original Message -----
From: "Carlos Quiroz" <car...@we...>
To: <ope...@li...>
Sent: Sunday, February 03, 2002 7:11 PM
Subject: Re: [Openjmx-devel] [Fwd: JMX work, and CustomerBMPBean]

> On Friday 01 February 2002 17:06, Jérôme BERNARD wrote:
> Hi Jérôme
>
> I still have a bug with this but now it extends the
> MBeanClass+MBeanDescriptionAdapter
>
> Regards
>
> P.S. I will wait for this to release

On Friday 01 February 2002 17:06, J=E9r=F4me BERNARD wrote:
Hi J=E9r=F4me=20

I still have a bug with this but now it extends the=20
MBeanClass+MBeanDescriptionAdapter

Regards

P.S. I will wait for this to release

> Carlos Quiroz wrote:
> >>Now question is where? and should I do it?
> >>Where to put the license of XDoclet too?
> >
> >I'd put the license at src/etc and the lib at lib/
>
> Ok. I am going to do it right now.
>
> >I found a bug....
> >When the jmx:mbean extends=3D"XXx" is set the YYYMBeanDescription clas=
s
> > doesn't extends MBeanDescriptionAdapter, instead doesn't extends anyt=
hing
>
> This is why I suggested you to update your XDoclet CVS tree. I told it
> to Dmitri yesterday and it is fixed since a few hours now.
>
> I faced the same problem you have just after Dmitri commited 'cause I
> use the "extends" feature everywhere :-)
>
> Jerome.
>
>
> _______________________________________________
> Openjmx-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openjmx-devel

On Friday 01 February 2002 19:55, Bordet, Simone wrote:
> Hi,
>
> > I can do it in my own let say on Sunday
>
> Ok.
> I was suggested to put news not only in SF, but also in freshmeat and
> slashdot. I don't know these sites, anyone has experience ? They're good ?
No idea, but I can take a look

>
> > > Last major thing to be done is the sendPastNotification in
> >
> > the Timer, and a
> >
> > > small thing in the MLet about dynamic libraries, then we're
> >
> > complete.
> > Are you going to implement this for beta2 or it will be for RC/final?
>
> Not beta 2, for sure. You can take a look at them if you want and have
> time, anybody can.
not me, I have to work this weekend but take a couple of hours for 
this :-(

>
> Ah, remember also to update the change notes tracker, I guess after beta 2
> we can go for a RC, so that we can keep track of changes between betas and
> RCs.
Yeah, the changes will be included in the README and I'll add a 1.b2 release

>
> Simon
>
> _______________________________________________
> Openjmx-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openjmx-devel

Hi,

> I can do it in my own let say on Sunday

Ok.
I was suggested to put news not only in SF, but also in freshmeat and =
slashdot. I don't know these sites, anyone has experience ? They're good =
?

> > Last major thing to be done is the sendPastNotification in=20
> the Timer, and a
> > small thing in the MLet about dynamic libraries, then we're=20
> complete.
> Are you going to implement this for beta2 or it will be for RC/final?

Not beta 2, for sure. You can take a look at them if you want and have =
time, anybody can.

Ah, remember also to update the change notes tracker, I guess after beta =
2 we can go for a RC, so that we can keep track of changes between betas =
and RCs.

Simon

On Friday 01 February 2002 17:58, Bordet, Simone wrote:
> Hi,
>
> > what about a beta2 release this weekend?
>
> It will be fine also for me, but I will not be present this weekend and
> next week.
I can do it in my own let say on Sunday

>
> Last major thing to be done is the sendPastNotification in the Timer, and a
> small thing in the MLet about dynamic libraries, then we're complete.
Are you going to implement this for beta2 or it will be for RC/final?

>
> Simon
>
> _______________________________________________
> Openjmx-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openjmx-devel

Hi,

> what about a beta2 release this weekend?

It will be fine also for me, but I will not be present this weekend and =
next week.

Last major thing to be done is the sendPastNotification in the Timer, =
and a small thing in the MLet about dynamic libraries, then we're =
complete.

Simon

Well fine for me. I guess the documentation has to be updated a bit and 
I won't be free for working on it this week-end but if I am lucky I will 
be able to finish it today. Anyway, I suppose that with the example, 
some developers in need of this feature will be able to figure out how 
to use it :-)

Jerome.

Carlos Quiroz wrote:

>>Carlos Quiroz wrote:
>>
>>>Ant.jar is in the build dir
>>>
>>Ok. Thank you. I have commited the example and the required changes now.
>>
>I noticed and thanks a lot
>
>what about a beta2 release this weekend?
>

>Carlos Quiroz wrote:
>
>>Ant.jar is in the build dir
>>
>Ok. Thank you. I have commited the example and the required changes now.
I noticed and thanks a lot

what about a beta2 release this weekend?

>
>Jerome.
>
>
>_______________________________________________
>Openjmx-devel mailing list
>Ope...@li...
>https://lists.sourceforge.net/lists/listinfo/openjmx-devel
>

Carlos Quiroz wrote:

>Ant.jar is in the build dir
>
Ok. Thank you. I have commited the example and the required changes now.

Jerome.

> -----Original Message-----
> From: J=E9r=F4me BERNARD [mailto:jer...@xt...]
> Sent: 01 February 2002 17:22
> To: ope...@li...
> Subject: Re: [Openjmx-devel] [Fwd: JMX work, and CustomerBMPBean]
>=20
> Carlos Quiroz wrote:
>=20
> >
> >
> >>Ok. I am facing a classic "chicken and the egg" problem :-)
> >>I have updated the example and am ready to commit BUT it will break
> >>examples compilation since we need XDoclet to go through the MBean
> >>implementation file in order to generate at least the interface. So
I
> >>have to add in CVS the xdoclet.jar file.
> >>
> >Yes I noticed the problem. Perhaps you could add a test via setting
an
> >available property which is true if the XXXMBean.java file is
available,
> and
> >only then it will invoke the xdoclet task.
> >
> XDoclet requires ant.jar to be in the classpath or somewhere else (but
> then precised in the build.xml file) and I am wondering what I should
> do. Should I check if there is an ant.jar file in the lib directory?
Or
> should I add ant.jar in CVS in the lib directory?
Ant.jar is in the build dir

>=20
> Jerome.
>=20
>=20
> _______________________________________________
> Openjmx-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openjmx-devel

Carlos Quiroz wrote:

>	
>
>>Ok. I am facing a classic "chicken and the egg" problem :-)
>>I have updated the example and am ready to commit BUT it will break 
>>examples compilation since we need XDoclet to go through the MBean 
>>implementation file in order to generate at least the interface. So I 
>>have to add in CVS the xdoclet.jar file.
>>
>Yes I noticed the problem. Perhaps you could add a test via setting an 
>available property which is true if the XXXMBean.java file is available, and 
>only then it will invoke the xdoclet task. 
>
XDoclet requires ant.jar to be in the classpath or somewhere else (but 
then precised in the build.xml file) and I am wondering what I should 
do. Should I check if there is an ant.jar file in the lib directory? Or 
should I add ant.jar in CVS in the lib directory?

Jerome.

>Carlos Quiroz wrote:
>
>>=09
>>
>>>Now question is where? and should I do it?
>>>Where to put the license of XDoclet too?
>>>
>>I'd put the license at src/etc and the lib at lib/
>>
>Ok. I am going to do it right now.
ok

>
>>I found a bug....
>>When the jmx:mbean extends=3D"XXx" is set the YYYMBeanDescription class=
=20
doesn't=20
>>extends MBeanDescriptionAdapter, instead doesn't extends anything
>>
>This is why I suggested you to update your XDoclet CVS tree. I told it=20
>to Dmitri yesterday and it is fixed since a few hours now.
>
>I faced the same problem you have just after Dmitri commited 'cause I=20
>use the "extends" feature everywhere :-)
Ok. I updated yesterday night or this morning but there were some bugs wi=
th=20
the serialveruid tags. Now it seems ok

>
>Jerome.
>
>
>_______________________________________________
>Openjmx-devel mailing list
>Ope...@li...
>https://lists.sourceforge.net/lists/listinfo/openjmx-devel
>

Carlos Quiroz wrote:

>	
>
>>Now question is where? and should I do it?
>>Where to put the license of XDoclet too?
>>
>I'd put the license at src/etc and the lib at lib/
>
Ok. I am going to do it right now.

>I found a bug....
>When the jmx:mbean extends="XXx" is set the YYYMBeanDescription class doesn't 
>extends MBeanDescriptionAdapter, instead doesn't extends anything
>
This is why I suggested you to update your XDoclet CVS tree. I told it 
to Dmitri yesterday and it is fixed since a few hours now.

I faced the same problem you have just after Dmitri commited 'cause I 
use the "extends" feature everywhere :-)

Jerome.

=09>Carlos Quiroz wrote:
>
>>>>
>>>>If possible include a minimal build.xml for it
>>>>
>>>Sure. I will copy the build.xml file from another example and update i=
t=20
>>>in order to use the jmxdoclet ant task.
>>>BTW we are supposed to add xdoclet.jar in CVS and to ship it with the=20
>>>distribution...
>>>
>>I think that's what we agreed before (don't forget the license), let us=
 know=20
>>when it's stable enough and then we should put it in the lib dir and mo=
dify=20
>>the distribution task to include it possible for beta2
>>
>Ok. I am facing a classic "chicken and the egg" problem :-)
>I have updated the example and am ready to commit BUT it will break=20
>examples compilation since we need XDoclet to go through the MBean=20
>implementation file in order to generate at least the interface. So I=20
>have to add in CVS the xdoclet.jar file.
Yes I noticed the problem. Perhaps you could add a test via setting an=20
available property which is true if the XXXMBean.java file is available, =
and=20
only then it will invoke the xdoclet task.=20

>
>Now question is where? and should I do it?
>Where to put the license of XDoclet too?
I'd put the license at src/etc and the lib at lib/

I found a bug....
When the jmx:mbean extends=3D"XXx" is set the YYYMBeanDescription class d=
oesn't=20
extends MBeanDescriptionAdapter, instead doesn't extends anything

Carlos Quiroz wrote:

>>>
>>>If possible include a minimal build.xml for it
>>>
>>Sure. I will copy the build.xml file from another example and update it 
>>in order to use the jmxdoclet ant task.
>>BTW we are supposed to add xdoclet.jar in CVS and to ship it with the 
>>distribution...
>>
>I think that's what we agreed before (don't forget the license), let us know 
>when it's stable enough and then we should put it in the lib dir and modify 
>the distribution task to include it possible for beta2
>
Ok. I am facing a classic "chicken and the egg" problem :-)
I have updated the example and am ready to commit BUT it will break 
examples compilation since we need XDoclet to go through the MBean 
implementation file in order to generate at least the interface. So I 
have to add in CVS the xdoclet.jar file.

Now question is where? and should I do it?
Where to put the license of XDoclet too?

Jerome.

<snip>
>>>I should add the example I wrote in CVS. I will complete it and add=20
>>>operations and constructors with more than one parameter too. What is=20
>>>the best place for adding it?
>>>
>>It should go to examples/tools/xdoclet
>>
>Ok.
>
>>
>>
>>If possible include a minimal build.xml for it
>>
>Sure. I will copy the build.xml file from another example and update it=20
>in order to use the jmxdoclet ant task.
>BTW we are supposed to add xdoclet.jar in CVS and to ship it with the=20
>distribution...
I think that's what we agreed before (don't forget the license), let us k=
now=20
when it's stable enough and then we should put it in the lib dir and modi=
fy=20
the distribution task to include it possible for beta2

>
>
>Jerome.
>
>
>
>
>_______________________________________________
>Openjmx-devel mailing list
>Ope...@li...
>https://lists.sourceforge.net/lists/listinfo/openjmx-devel
>

Carlos Quiroz wrote:

>>Carlos Quiroz wrote:
>>
>>>>PS: I will make my best to complete the documentation about XDoclet. 
>>>>There is a lot of things missing in it.
>>>>
>>>It would be nice to include an example like
>>>
>>>/**
>>>*
>>>* @jmx:mbean-operation description="...."
>>>*/
>>>public void operation(String name, String name2)
>>>
>>>and so on.
>>>
>>I should add the example I wrote in CVS. I will complete it and add 
>>operations and constructors with more than one parameter too. What is 
>>the best place for adding it?
>>
>It should go to examples/tools/xdoclet
>
Ok.

>
>
>If possible include a minimal build.xml for it
>
Sure. I will copy the build.xml file from another example and update it 
in order to use the jmxdoclet ant task.
BTW we are supposed to add xdoclet.jar in CVS and to ship it with the 
distribution...

Jerome.

>Carlos Quiroz wrote:
>
>>>PS: I will make my best to complete the documentation about XDoclet.=20
>>>There is a lot of things missing in it.
>>>
>>It would be nice to include an example like
>>
>>/**
>> *
>> * @jmx:mbean-operation description=3D"...."
>> */
>>public void operation(String name, String name2)
>>
>>and so on.
>>
>I should add the example I wrote in CVS. I will complete it and add=20
>operations and constructors with more than one parameter too. What is=20
>the best place for adding it?
It should go to examples/tools/xdoclet

If possible include a minimal build.xml for it

>
>Jerome.
>
>
>_______________________________________________
>Openjmx-devel mailing list
>Ope...@li...
>https://lists.sourceforge.net/lists/listinfo/openjmx-devel
>

Carlos Quiroz wrote:

>>PS: I will make my best to complete the documentation about XDoclet. 
>>There is a lot of things missing in it.
>>
>It would be nice to include an example like
>
>/**
> *
> * @jmx:mbean-operation description="...."
> */
>public void operation(String name, String name2)
>
>and so on.
>
I should add the example I wrote in CVS. I will complete it and add 
operations and constructors with more than one parameter too. What is 
the best place for adding it?

Jerome.

>Yup.
>
>I really ease JMX development. I was so much bored having to keep=20
>updating my MBean interfaces & descriptions that I thought about this=20
>feature.
Yes it really does. It is quite boring to write so many times the same st=
uff=20
:-)

>
>As I said, I might add a mlet template (for generating mlet tags) with=20
>merges (so that one file might contain more than one mlet tag).=20
>Depending on what you do for "mbean initialization", a template would be=
=20
>quite good too (for specifing in the implementation file the default val=
ue).
Yes, but that's a bit on the waiting. I guess it won't make it before bet=
a2

>
>Dmitri commited a few hours ago (around 4 to 8 hours ago) some few=20
>fixes, so check if you have the latest version. Ara (the other=20
>administrator of XDoclet) told me that the "approximate" (we all know=20
>what a plan mean on an open-source project :-)) new release of XDoclet=20
>is for 2 or 3 weeks.
I got it from an update yesterday but is working quite fine. I'll also=20
contribute an expanded syntax highlight file for my editor jEdit

>
>Have fun "templating" :-)
>
>Jerome.
>
>PS: I will make my best to complete the documentation about XDoclet.=20
>There is a lot of things missing in it.
It would be nice to include an example like

/**
 *
 * @jmx:mbean-operation description=3D"...."
 */
public void operation(String name, String name2)

and so on.

>
>
>Carlos Quiroz wrote:
>
>>Hi J=E9r=F4me=20
>>
>>This is really, really good. I had never used xdoclet before and I'm ve=
ry=20
>>impressed. I think I'll move all my MBeans to use xdoclet
>>
>>Regards
>>
>>
>>>-------- Original Message --------
>>>Subject: JMX work, and CustomerBMPBean
>>>Date: Fri, 1 Feb 2002 00:59:15 +1100
>>>
From: "Dmitri Colebatch" <di...@oz...>
>>
>>>To: <xdo...@li...>
>>>CC: J=E9r=F4me BERNARD <jer...@xt...>
>>>
>>>
>>>
>>>
>>>hey all,
>>>
>>>
>>>
>>>firstly - I've just checked in Jerome Bernard's JMX work from the=20
>>>OpenJMX project, and put the first beta of openjmx in the lib director=
y=20
>>>to enable the openjmx specific stuff to compile.  the tags are:
>>>
>>>
>>>
>>>class level:
>>>
>>> jmx:mbean extends=3D"" description=3D""
>>>
>>>
>>>
>>>method level:
>>>
>>> jmx:managed-constructor description=3D""
>>>
>>> jmx:managed-constructor-parameter postition=3D"" name=3D"" descriptio=
n=3D""
>>>
>>>
>>>
>>> jmx:managed-attribute description=3D""
>>>
>>>
>>>
>>> jmx:managed-operation description=3D""
>>>
>>> jmx:managed-operation-parameter postition=3D"" name=3D"" description=3D=
""
>>>
>>>
>>>
>>>ok - its only a first cut, I changed a few things, so it will probably=
=20
>>>need a little more work (tomorrow night) after Jerome has a look at my=
=20
>>>changes.  but it should work, hav ea look at the samples.
>>>
>>>
>>>
>>>secondly - CustomerBMPBean seems to be breaking, something to do with=20
>>>the dataobject.  Anyone else seeing this?  I had a super quick look, b=
ut=20
>>>couldn't spot the cause.  could someone give me a sanity check?
>>>
>>>
>>>
>>>cheers
>>>
>>>dim
>>>
>
>
>
>_______________________________________________
>Openjmx-devel mailing list
>Ope...@li...
>https://lists.sourceforge.net/lists/listinfo/openjmx-devel
>

Yup.

I really ease JMX development. I was so much bored having to keep=20
updating my MBean interfaces & descriptions that I thought about this=20
feature.

As I said, I might add a mlet template (for generating mlet tags) with=20
merges (so that one file might contain more than one mlet tag).=20
Depending on what you do for "mbean initialization", a template would be =

quite good too (for specifing in the implementation file the default valu=
e).

Dmitri commited a few hours ago (around 4 to 8 hours ago) some few=20
fixes, so check if you have the latest version. Ara (the other=20
administrator of XDoclet) told me that the "approximate" (we all know=20
what a plan mean on an open-source project :-)) new release of XDoclet=20
is for 2 or 3 weeks.

Have fun "templating" :-)

Jerome.

PS: I will make my best to complete the documentation about XDoclet.=20
There is a lot of things missing in it.

Carlos Quiroz wrote:

>Hi J=E9r=F4me=20
>
>This is really, really good. I had never used xdoclet before and I'm ver=
y=20
>impressed. I think I'll move all my MBeans to use xdoclet
>
>Regards
>
>
>>-------- Original Message --------
>>Subject: JMX work, and CustomerBMPBean
>>Date: Fri, 1 Feb 2002 00:59:15 +1100
>>
>From: "Dmitri Colebatch" <di...@oz...>
>
>>To: <xdo...@li...>
>>CC: J=E9r=F4me BERNARD <jer...@xt...>
>>
>>
>>
>>
>>hey all,
>>
>>
>>
>>firstly - I've just checked in Jerome Bernard's JMX work from the=20
>>OpenJMX project, and put the first beta of openjmx in the lib directory=
=20
>>to enable the openjmx specific stuff to compile.  the tags are:
>>
>>
>>
>>class level:
>>
>> jmx:mbean extends=3D"" description=3D""
>>
>>
>>
>>method level:
>>
>> jmx:managed-constructor description=3D""
>>
>> jmx:managed-constructor-parameter postition=3D"" name=3D"" description=
=3D""
>>
>>
>>
>> jmx:managed-attribute description=3D""
>>
>>
>>
>> jmx:managed-operation description=3D""
>>
>> jmx:managed-operation-parameter postition=3D"" name=3D"" description=3D=
""
>>
>>
>>
>>ok - its only a first cut, I changed a few things, so it will probably =

>>need a little more work (tomorrow night) after Jerome has a look at my =

>>changes.  but it should work, hav ea look at the samples.
>>
>>
>>
>>secondly - CustomerBMPBean seems to be breaking, something to do with=20
>>the dataobject.  Anyone else seeing this?  I had a super quick look, bu=
t=20
>>couldn't spot the cause.  could someone give me a sanity check?
>>
>>
>>
>>cheers
>>
>>dim
>>

2001	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov (277)	Dec (103)
2002	Jan (320)	Feb (100)	Mar (1)	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2009	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec (1)

openjmx-devel Mailing List for OpenJMX (Page 4)

openjmx-devel — OpenJMX Developers list