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. 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 ? 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?? 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> 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. 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? 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
