Hi Geeks Maybe it is a better solution to have the minimal configuration specified in the free JBoss documenation because what is the minimal configuration. If you don't need JMS then you can get ride of it but when you deploy a MDB then you need it. I would suggest we go with the everything and discuss what you can take out in the docu.
Have fun - Andy ----- Original Message ----- From: "Andrew Scherpbier" <[EMAIL PROTECTED]> To: "Jason Dillon" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, April 09, 2002 6:39 PM Subject: Re: [JBoss-dev] Demo > I see your point about a "minimal" configuration. > > But what about the idea of a directory that has all the deployable > stuff. This could be a good solution to the problem of people asking > (or having to search for) database *-service.xml files. And as I said > earlier, it would allow people to pick the web container they want (if any). > > By building a completely self-contained package that requires minimal > external stuff to be installed, the user's experience will be that much > better! ;-) > > --Andrew > > Jason Dillon wrote: > > > Sure, though then perhaps an additional "minimal" configuration is in > > order, so that the "default" brings up most of the needed > > functionality. Or perhaps not... this is hard, because the minimum > > required is on that there be a jboss-service.xml, you don't need to > > configure any other beans... but this configuration is not very useful. > > > > I would support a minimal configuration, though I am not sure what > > functionality that would contain. I would also support documenting > > this somewhere, as minimal to you might not be minimal to me and so on. > > > > I expect 70% of the users who download this release to uppack it, > > startup with the defaults, copy there .ear or .war and then load a > > webpage in there broweser for confirmation that it all worked. > > > > I understand that you want to be clear about what is requried and what > > is optional, but perhaps there is a better way to get this information > > across than with a seperate configuration? > > > > --jason > > > > > > Andrew Scherpbier wrote: > > > >> I have a suggestion on a related subject... > >> From my current point of view (as a user of jboss 3) I would actually > >> prefer a clear description of whatall goes into the deploy directory > >> and why, and let me be the judge what gets deployed. This would mean > >> creating the simplest deploy directory that has at least the ability > >> to deploy a simple (no war) ear file that contains EJBs. > >> In a separate directory, put all the crap that *can* be put into the > >> deploy directory (and these need to be clearly described since the > >> names may refer to things the user doesn't know about (yet)). The > >> motivation for this is that as a deployer of JBoss, I want to make > >> sure I only include the stuff that is actually used/required to > >> deploy my user's applications. > >> So, in other words, instead of making an example deploy directories > >> from which a user might not know what to delete, provide the minimal > >> config plus a clear description on what can be deployed. > >> > >> This might also be a nice way to include both Jetty and Catalina in > >> the binary distribution. Let the user pick what they want. > >> > >> Am I making any sense to anyone? > >> > >> Jason Dillon wrote: > >> > >>> I would prefer to keep any additional configurations that ship with > >>> the release to a minimum. I think that three configs: "default", > >>> "advanced" and "example" will cover what we need and won't add much > >>> extra confusion. I expect that clustering would go into the > >>> "advanced" configuration. > >>> > >>> --jason > >>> > >>> > >>> Peter Fagerlund wrote: > >>> > >>>> on 11-04-2 01.21, Jason Dillon at [EMAIL PROTECTED] wrote: > >>>> > >>>>> Do you mean a demo or example configuration for the server? I think > >>>>> that a demo module under jboss-all is not appropriate, but a demo or > >>>>> example configuration under server/ is certainly do able. There was > >>>>> talk awhile ago about how to best organize this. I have not > >>>>> implemented > >>>>> anything since there was not a final decision. > >>>>> > >>>>> I suggest we add a "advanced" and "example" config directory under > >>>>> server, probably copying "default" for a base. > >>>>> > >>>> > >>>> exactly ++ also maybe a folder for cluster and the like called > >>>> extended ? > >>>> ... The deployer would need to be aware and ant triggable ...Yes - > >>>> We talked > >>>> about it some while ago and the concencus was - cool ;-) if that is > >>>> not > >>>> final . then . Ahhh ... > >>>> > >>>> /peter_f > >>>> > >>>>> --jason > >>>>> > >>>>> > >>>>> Peter Fagerlund wrote: > >>>>> > >>>>>> Are We ready to make a Demo folder in jboss-all/ that BM would > >>>>>> copy into > >>>>>> output/*/* where I could with an ant build.xml file build and > >>>>>> copy to deploy > >>>>>> ... and once in deployed in deploy as a webapp I could edit some > >>>>>> source - > >>>>>> save - *bong* - cool ... > >>>>>> > >>>>>> /peter_f > >>>>>> > >>>>>> > >>>>>> _______________________________________________ > >>>>>> 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 > >> > >> > >> > >> > > > > > > -- > Andrew Scherpbier, CTO ([EMAIL PROTECTED]) > BlackBall Music (http://www.blackballmusic.com/) > > > > > _______________________________________________ > 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
