On 2001.12.06 12:46:21 -0500 Luke Taylor wrote: > Bill Burke wrote: > > > Guys, > > > > You all may or may not agree, but the current structure of mbean xml > > files is really confusing. > > > Ah. I'm glad someone else has some reservations. I assumed I was just > lagging behind (probably true anyway) and that everyone else knew > exactly what was going on from all the discussions on sars and services > so it's good to hear a mildly dissenting voice with some clout.
On the other hand, I think quite a few people have said it was confusing at first and useful when they got used to it. > > Could somone possibly supply a v. brief summary of the current situation > and what the final plan is? Some things it would be useful to know: > > 1. I take it jboss-service.xml is loaded first - would it work if I put > other (independent) services in here, even though it says not to ? The one in conf/default is. > > 2. Is the boot-server configuration only used for booting over the > network - can we try this out just now, and how do you decide what > configuration it obtains/supplies?? I have no idea what this is for. > > 3. Why does the jetty mbean in the jboss-service.xml (in boot-server) > refer to two files which don't exist (at least not in the current build): > > "Configuration">../conf/boot-server/jetty.xml</attribute> > "WebDefault">../conf/boot-server/webdefault.xml</attribute> I think this is an obsolete antique. > > 4. Do all my other services go in the deploy directory rather than > conf/blah? This seems to make it a bit harder to set up several > different static configurations (as you would do previously by just > creating new dirs in jboss/conf). I guess the hot-deploy of services > makes this less of an issue. Yes. The current situation is way less than ideal. I want a deployment script functionality and pretty much deprecate autodeploy. If you want several configurations, you could have several conf dirs, and for each a separate deploy dir with the stuff to autodeploy. > > 5. Should they be sars, or plain xml files, or does it matter. Are the > sars only necessary if I want to supply additonal jar files without > putting them in lib/ext? Doesn't matter. I'd use a sar for a package that doesn't need it's mbeans reconfigured frequently and you't like to keep everything together, and a service.xml for things under development. > > I'll have a go at redoing the simple mbean lab we did in London to see > if I can clear things up, but any information on the basic setup these > days would be very useful. > > thanks, > > Luke. > > > -- > Luke Taylor. Monkey Machine Ltd. > PGP Key ID: 0x57E9523C http://www.mkeym.com > > > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
