On 2002.03.01 15:51:35 -0500 Steve Loughran wrote: > > ----- Original Message ----- > From: "David Jencks" <[EMAIL PROTECTED]> > To: "Ant Developers List" <[EMAIL PROTECTED]> > Sent: Friday, March 01, 2002 11:58 > Subject: Re: Order of attributes versus elements > > > > On 2002.03.01 13:29:34 -0500 Steve Loughran wrote: > > > > > > ----- Original Message ----- > > > From: "David Jencks" <[EMAIL PROTECTED]> > > > To: "Ant Developers List" <[EMAIL PROTECTED]> > > > Sent: Friday, March 01, 2002 05:34 > > > Subject: Re: Order of attributes versus elements > > > > > > > > > > Just to be gratuitous, I'll repeat my assertion that a lot of > aspects > > > of > > > > ant might be simpler if it was built using jmx. > > > > > > what, like having to write an interface called ExecTaskMBean for > every > > > task > > > instead of using some kind of declarative metadata to describe what > > > methods > > > exported? JMX is like EJB1.0 in that respect. > > > > use model mbeans, not standard ones. See the xdoclet OpenJmx > descriptor > > generators and the (just starting) jboss mx xml descriptor generator. > If > > for some reason you like Standard MBeans, use xdoclet to generate the > > interface for you. > > I should look at this
I think it's really cool. I didn't really understand model mbeans until I read about them in Juha Lindfor's new jmx book. > > > Plus the whole JMX registry > > > singleton model is messy; makes writing unit tests that much harder > > > > What do you mean by the singleton model? > > the way you have to register beans with the central place to make them > locatable, if all your server go through the same system to find stuff > then > you need to clean it out between unit tests, and it doesnt seem that easy > to > clean up unless you know what you added. > > But I welcome being proved wrong, if it simplifies my future work Maybe you are lacking a reasonable way of deploying mbeans... the mlet pseudo-xml notation sucks, and doing it in code is also kind of a non starter. I'm used to the jboss 3 model, which lets you deploy xml configuration chunks of any size at any time, and provides pretty good lifecycle and dependency management. Tests I write generally involve deploying an xml document with the configuration for the mbeans I'm working with, testing them, and finally undeploying the document. david jencks > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
