What is on deploy/ should really only be used for development and adding
dynamically say a datasource.

PERIOD.

Putting all the deployment in there and removing the service.xml from conf
is a bad idea.
Do you hear me... a *bad* idea.

The service.xml from conf is the STATIC configuration, and it should REALLY
BE THE WAY WE SHIP OUR STUFF.

In clear you develop your solutions with the sar trick, you deploy new stuff
eventually but when it comes down to locking your servers for production or
shipping a product with JBoss YOU PUT OUT A SERVICE.XML IN THE CONFIGURATION
DIRECTORY and the files in lib/ext.

moving this around won't bring ANYTHING and will confuse the hell out of
people.

because we can then change the configuration in one file.  I don't buy the
"I remove a file and I removed the stuff", because I can just as well remove
the xml entry and I removed the service and since the SAR makes the xml
unreachable its a pain. End of case.

This is a busy-work proposal, I read it twice and I don't understand what it
bring to the table, while I see pain, as far as I am concerned it goes to
/dev/null.

You are turning what is a trick in development (hotcycling your services)
and what is a nice way to extend services in your servers with datasources
and new services, into a silly standard.  Bottom line you can't work on the
XML, there are 24 configuration files (one per service) and the whole thing
is silly.

-1 all the way, just forget this.

|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of David
|Jencks
|Sent: Friday, February 22, 2002 10:53 AM
|To: [EMAIL PROTECTED]
|Subject: Re: [JBoss-dev] Configuration layout changes...
|
|
|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

Reply via email to