Lets not talk about what names you want to use, it is plain silly and pointless.
I imagine that if we do anything along these lines, we will provide one or two seperate configuration directories under server/, then either provide a toplevel examples/ or something similar under docs/. But before anything is done, I think we need to understand what the purpose of these new configs & examples are for, who is the target audience and how much of this will be covered by the documentation. Otherwise, you are just spinning your wheels. --jason Andrew Scherpbier wrote: > Peter Fagerlund wrote: > >> on 10-04-2 18.50, Andrew Scherpbier at [EMAIL PROTECTED] wrote: >> >>> How about "deployables" in the root of the distribution tree. >>> >> >> close but ... >> > but what? > > Maybe "available-services" or "possible-services" > >> >> >>> Also, to follow up on Peter's message in a different thread about using >>> a default.war to document things... I really like that idea. It can >>> be extended to dynamically show what services can be deployed by >>> looking >>> in the deployables directory and parsing the *-service.xml files for >>> information. If those files contain the documentation for the service >>> they provide, then there is only one place to update if things change. >>> (Would adding a <description> element to the *-service.xml files break >>> anything?) >>> The cool part of this is that the documentation could automatically >>> show >>> the dependecies as well. >>> >>> At another level, this whole interface could be extended to be a web >>> based configuration thingy which can create configurations with the >>> services you want. Maybe this should be part of the new JMX web >>> interface. >>> >> >> fucking beautiful >> > At yet another level (higher baby, go higher!) it might be much easier > to not rely on the autodeployer at all for this stuff. > Instead, use the web interface to create a meta deployment descriptor > that tells a new type of deployer what to deploy and in what order. > That way, all possible service, sar, and jar files can be put in one > place and left there. > The only problem with this approach that I can see is that some of the > *-service.xml files need customization (the database ones come to > mind). Any bright ideas on how to deal with that? > > Don't get me wrong, I absolutely love the autodeployer for > development, but from a user point of view, it can be quite > confusing. Providing a clean, web-based configuration interface will > make the barrier to entry for jboss deployers much lower. > This idea might actually work really well in a clustered environment > as well. > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
