Skip to end of metadata
Go to start of metadata

Overriding a module definition will allow you to add functionality to the module and override existing functionality. You should always put your files last in the list properties to facilitate the cases where you want to override functionality. While the documentation below assumes that you are overriding the module bean for a delivered module, a very similar process would apply when adding a module. You would just have a heck of a lot more information to change after copying in a template module definition(wink)

  1. Add your override Spring file for the module.
  2. Copy the original module definition into your file. It will have a id like "xxxModule" and a class of org.kuali.core.KualiModule. See the chartModule bean in work/src/org/kuali/module/chart/OJB-repository-chart.xml for an example.
  3. Make any necessary changes.
    • Change the module user classes
    • Change authorizer classes or package prefixes
    • Add data dictionary packages
    • Add OJB repository files
    • Add DWR files
    • Add batch jobs
      For example, here we have added to dataDictionaryPackages, databaseRepositoryFilePaths, and scriptConfigurationFilePaths.
  4. Don't forget to include your new Spring file by overriding the spring.source.files build property.
Unable to render {include} The included page could not be found.
  • No labels