I am not sure that the 'default' config will ever be used in a production environemnt. I think of it as a config that users can startup, play with, to get comfortable with JBoss (and fall in love with it, maddly inlove such that they want to give all there money to us and tell everyone they know how much they love it and can't stand the thought of giving bea another dollar).
I do think that we need to provide a standard place for deployment files which require extra config before working. If the non-core bits are moved from jboss/lib to jboss/servers/<configName>/lib then this should do, so folks would know what they could safely remove and not mess up the core. --jason David Jencks wrote: >One of the things I really wanted to do with the sars was move these >special-purpose out of lib/ext and into individually deployable packages >that included all needed classes and configuration. Then you could easily >construct a desired configuration by dropping the appropriate (and clearly >named) sars into the deploy directory. I started trying to do this, >gradually. I'm not sure this is a shared vision since I think some of this >may have been undone by marc. Maybe we could talk about whether this is a >good idea and how best to do it. > >One problem tends to be that "default configuration" is not really suitable >for most production usage. If the sar ships with default config, you have >to open it up, change stuff, and redeploy. Maybe there is a way to set up >basic config that will always be needed, included in the sar, and "example >config, provided outside. Possibly the jmx persistence will provide a >better solution for this also, although I don't yet see how. > >thanks > >david jencks > > >On 2002.02.22 13:14:16 -0500 Scott M Stark wrote: > >>Ok, keep a lib and lib/ext. However, all that is in these directories >>is not necessarily common. Certainly they should not contain all >>of the stuff currently there. A large percentage of these so called >>common libs would be replaced in a different configuration. >> >>In lib: >>crimson.jar - replaceable by any other JAXP compliant parser >>jmxri.jar - replaceable by jbossmx, openJMX, tivoli's JMX >> >>In lib/ext: >>castor.jar - ??? >>jbossmq.jar - replaceable by another JMS provider >>jbossmqha.jar - replaceable by another JMS provider >>log4j.jar - replacable by different versions of log4j >>jbossmx.jar - Not even used yet? >>mail-plugin.jar - can be dropped or replaced by another >>javax.mail.Session >>factory >>hsqldb-plugin.jar - replacable by another DB >>... >> >>xxxxxxxxxxxxxxxxxxxxxxxx >>Scott Stark >>Chief Technology Officer >>JBoss Group, LLC >>xxxxxxxxxxxxxxxxxxxxxxxx >>----- Original Message ----- >>From: "Bill Burke" <[EMAIL PROTECTED]> >>To: "Scott M Stark" <[EMAIL PROTECTED]>; >><[EMAIL PROTECTED]> >>Sent: Friday, February 22, 2002 8:37 AM >>Subject: RE: [JBoss-dev] Configuration layout changes... >> >> >>>Don't move lib or lib/ext under the config directories if you're going >>> >>to >>do >> >>>this. We don't want multiple copies of jboss core libs hanging around >>> >>in >> >>>multiple places. You'll still need a lib directory under >>> >>config/default/lib >> >>>for config specific regular jar files. Or do all jars get placed under >>> >>the >> >>>deployer now? >>> >>>my 2cents >>> >>>Bill >>> >> >> >>_______________________________________________ >>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 > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
