Uploaded image for project: 'Metadata Aggregator'
  1. Metadata Aggregator
  2. MDA-178

Add a bean definition resource

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.9.2
    • Fix Version/s: 0.10.0
    • Component/s: None
    • Labels:
      None
    • Operating System:
      Multiple

      Description

      One thing that I have found it necessary to build for every significant application in which I have used the MDA is a bean catalogue. By this I mean a beans.xml file that defines abstract beans for each bean class I use from the MDA, named after that class but including lazy instantiation and defining common items such as the initialize and destroy method names. This simplifies actual bean declarations, which are made from the parent bean rather than specifying a class.

      See for example: https://github.com/ukf/ukf-meta/blob/master/mdx/common-beans.xml

      I think this is enough of a common pattern to provide as part of the distribution, invoked through an import of classpath:net/shibboleth/metadata/beans.xml or the like.

      It makes sense to include a fixed prefix (suggestion: mda.) in each name, so that we end up with, for example, mda.DOMResourceSourceStage.

      It doesn't seem to be necessary to include all of the package hierarchy in these abstract bean names, although it might make sense to include some grouping for function. This would be the same kind of choice as we have made in IdP bean configuration files (where the prefix is shibboleth..

        Attachments

          Activity

            People

            Assignee:
            ian@iay.org.uk Ian Young
            Reporter:
            ian@iay.org.uk Ian Young
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 3 hours, 58 minutes
                3h 58m