The utiltity of the config/xxx directory has diminished, but it still gives configuration files and the core services definition. It still has utility as a namespace for alternate versions of:
auth.conf jndi.properties log4j.xml server.policy standardjaws.xml standardjboss.xml standardjbosscmp.xml I would agree that all of the stuff in deploy now are really services that are part of the default configuration and could just as easily be picked up and monitored from config/default/deploy. If you move deploy, why not move everything under conf except bin and client so that you can have multiple JBoss servers running on the same box with different configs. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Jason Dillon" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, February 21, 2002 7:10 PM Subject: [JBoss-dev] Configuration layout changes... > I think we need to change how we organize configuration & deployment > files before we finalize this release. Most configuration is now done > through the deploy/ directory, which is great, but what is point of > named configurations (default/*) anymore? > > I would hope that users would leave jboss-service.xml alone and add > there stuff to user-service.xml, or provide similair deployables for > there bits. So if we think of jboss-service.xml as containing the basic > core components and not really changing per install, then changing the > config name only lets users vary logging config and other config which > might be pulled from there as a resource... which are slimming down as > we convert them to use the xml xnippet facility. > > So what good does config name do us right now? Not a whole lot... > > So how do we re-organize our layout to make better use of this? > > To start we could place a deploy/ under each config, where users would > deploy there files. The problem then is where do the core server > components go? This takes us back to the deploy/lib stuff. > > To complicate things a little further, I don't think that it is super > easy to configure another deployable directory as it used to be with > AutoDeployer. This ins't a big deal for now, as I expect that we will > split that functionalty off into a deployment scanner bean, which can do > whatever it feels like. > > Until then, I think we may need to have a deploy dir under lib/ which > contains the core server deployables... or we can simply force users to > duplicate that stuff across there configs. This would be the simple > choice, and will allow the most control on a per config basis on what to > load. > > Short term, I think we should setup the enviroment like so: > > jboss-* > conf/ > default/ > deploy/ > jboss-service.xml > log4j.xml > ... > > This will make better use of the configuration name each server runs > under. We can leave putting the common stuff in a shared config later. > > Comments? > > --jason > > > _______________________________________________ > 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
