For what its worth I think the jar dependency tracking stuff is the only stuff in need of a rethink, the mbean-ref and classpath syntax I am quite happy with.
I certainly don't think we need a return to the "depends" tag. BTW, I have also noticed a bug in the mbean-ref stuff, it would be nice if someone could find and fix it in their journeys. If you have an mbean with a number of mbean refs in it and hot undeploy and hot redeploy the mbean while the server is running, something in the dependency tracking seems to go haywire because when you shut the server down your mbean is then undeployed once for each mbean ref it contains i.e. it is undeployed multiple times. If you haven't hot undeployed and redeployed then this doesn't happen. David > he he... > > in fact 2 problems one real one fake > > the fake: 'depends' removal i have been working on my > codebase for the past > 3weeks and the code was update by david j last week :) I was > missing it but > I did update the server deployer hence panic...my bad > > the real: the classpath explicit thingy, I think the davidM idea of > wildcards is important and I really can't fathom why we are > tracking *jars* > ... weird. please explain I might be missing it > the real2: the over the board service.xml I think we got that covered. > > marcf > > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.303 / Virus Database: 164 - Release Date: 11/24/2001 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
