3 Replies Latest reply on Jan 25, 2011 3:23 AM by jaikiran

    Grand Unified Tweak Documentation?

    nickarls

      If I want to disable schema validation for a TLD I just edit the server/default/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml and set the useSchemaValidation attribute of the TldParsingDeployer to false.

       

      The server structure is full of these tunings that can be made. But are all those tweaks documented anywhere in some centralized location? You can stumble on stuff that are already there and you just set some true value to false but when you need to know what attributes to add you're out of luck...

        • 1. Grand Unified Tweak Documentation?
          jaikiran

          Nicklas Karlsson wrote:

           

          But are all those tweaks documented anywhere in some centralized location?

          Unfortunately, no. Maybe we should start a wiki article and keep adding to it.

          • 2. Grand Unified Tweak Documentation?
            nickarls

            The problem is that (if I understand correctly) almost any internal file can have it's attributes set through XML files even if it makes sense or not.

             

            Perhaps it would be an idea that for AS 7, the module leads (or people who Know Stuff) would add an annotation for fields that are candidates for configuration and then the documentation would be auto-generated. Something like

             

            @Configurable(description="TLD's getting you down? Cut some corners by settings this to false and you can skip validation")

            public void setUseSchemaValidation(boolean useSchemaValidation)

            {

               getHelper().setUseSchemaValidation(useSchemaValidation);

            }

             

            You could then generate a nice list with bean - property - description. With another annotation for the file location within the AS, you could even generate links to the correct file. Perhaps.

            • 3. Grand Unified Tweak Documentation?
              jaikiran

              Nicklas Karlsson wrote:

               

              Perhaps it would be an idea that for AS 7, the module leads (or people who Know Stuff) would add an annotation for fields that are candidates for configuration and then the documentation would be auto-generated.

              For AS7, the configurations (meant to be done by users) has been minimized and the goals are to make sure that some random internal AS specific configurations don't end up in these files. Here's one such thread which explains the goals for AS7 http://community.jboss.org/message/574143#574143 with regard to this topic.