> in order of simplicity there is > less simple : all in sars, PACKAGED SARS (with no classes in > there either ! X-() > medium: all in separate mybean-service.xml it can be good to have > the separate files (without the silly packaging) so that the > autodeployer can pick up the fact that you have changed one mbean > and only one > simplest: what I had in the first release of it, meaning one > jboss-service.xml file (equivalent of the jboss.jcml) and one > example sar and one example myservice-service.xml but for god's > sake don't let the sar be the norm, it becomes impossible. > > David bottom line: I think the work is really good (I really do) > but let it up to us to determine what makes sense admin wise, > bill you can bring all the sars back under one roof, following > the above 2 guidelines. So the infrastructure stays as it WILL BE
still want me to do this? _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
