Uploaded image for project: 'Red Hat Decision Manager'
  1. Red Hat Decision Manager
  2. RHDM-860

Employee rostering unable to deploy due to unresolvable placeholder in orm.xml

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Blocker
    • 7.3.0.GA
    • 7.3.0.GA
    • OptaPlanner
    • None
    • CR1
    • CR2
    • Hide

      1. get optaweb-employee-rostering project
      2. mvn clean install -Dproductized -DskipTests
      3. in the ee subsystem of Wildfly's standalone.xml, configure:
      <spec-descriptor-property-replacement>true</spec-descriptor-property-replacement>
      4. deploy the employee-rostering WAR
      5. see a server log for error message

      Alternatively, try to

      Show
      1. get optaweb-employee-rostering project 2. mvn clean install -Dproductized -DskipTests 3. in the ee subsystem of Wildfly's standalone.xml, configure: <spec-descriptor-property-replacement>true</spec-descriptor-property-replacement> 4. deploy the employee-rostering WAR 5. see a server log for error message Alternatively, try to

    Description

      Employee Rostering cannot be deployed with the productized profile. As the persistence-related parameter need to be provided at runtime, wildfly is able to take placeholders in some configuration files (e.g. persistence.xml). For more details see RHDM-745.

      However, after configuring the property replacement (see steps to reproduce), the deployment fails as one of the placeholders is in orm.xml, where Wildfly does not do the replacement.

      Attachments

        1. stacktrace
          3 kB
          Radovan Synek

        Issue Links

          duplicates

          Bug - A problem that impairs or prevents the functions of the product. RHDM-840 OptaWeb Employee Rostering on postgrsql openshift image does not deploy

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is incorporated by

          Bug - A problem that impairs or prevents the functions of the product. PLANNER-1438 Fix tests that are broken due to resteasy upgrade

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              rsynek@redhat.com Radovan Synek
              rsynek@redhat.com Radovan Synek
              Radovan Synek Radovan Synek
              Radovan Synek Radovan Synek
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: