XMLWordPrintable

      The dependency needs to optional so provisioning a layer with batch does not automatically pull in legacy security.

      This is not just about making the module dependency optional, this is about understanding why it is not optional and identifying the steps required to make it optional.

      This needs to consider:

      • Default Configuration
      • User Defined Configuration

      Both of these can have different consequences depending on of they are used for:

      • Resource defined services
      • DeploymentUnitProcessor processing

            darran.lofthouse@redhat.com Darran Lofthouse
            darran.lofthouse@redhat.com Darran Lofthouse
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: