Embedded Jopr
  1. Embedded Jopr
  2. EMBJOPR-350

Unable to Unset configuration values for managed resources

    Details

    • Type: Bug Bug
    • Status: Closed Closed (View Workflow)
    • Priority: Blocker Blocker
    • Resolution: Done
    • Affects Version/s: 1.3.4
    • Fix Version/s: 1.3.4
    • Component/s: Web App/Integration
    • Labels:
      None
    • Environment:
      JBoss EAP 5.1.0 admin-console (Embeeded JOPR 1.3.4.SP1)
    • Steps to Reproduce:
      Hide

      JBOSS_HOME="/opt/jboss/eap/jboss-eap-5.1.0/jboss-as"
      JBOSS_CONF=00362683
      rm -rf "$

      {JBOSS_HOME}/server/${JBOSS_CONF}/"
      cp -a "${JBOSS_HOME}

      /server/default/" "$

      {JBOSS_HOME}/server/${JBOSS_CONF}"
      cd "${JBOSS_HOME}

      /bin" && ./run.sh -c $

      {JBOSS_CONF}

      -b 0.0.0.0

      1. Via admin-console, change "DefaultDS" property "Check Valid Connection SQL" to:
      2. SELECT * FROM "INFORMATION_SCHEMA"."SYSTEM_SESSIONS";
      3. Click "Save"
      4. Verify configuration change exists on the DefaultDS Configuration tab in admin-console
      5. Via admin-console, change "DefaultDS" property "Check Valid Connection SQL" back to Unset:
      6. Check "Unset" column next to property
      7. Click "Save"
      8. Verify configuration change exists on the DefaultDS Configuration tab in admin-console
      9. Here is where the bug seems to be as the Unset check is not retained
      Show
      JBOSS_HOME="/opt/jboss/eap/jboss-eap-5.1.0/jboss-as" JBOSS_CONF=00362683 rm -rf "$ {JBOSS_HOME}/server/${JBOSS_CONF}/" cp -a "${JBOSS_HOME} /server/default/" "$ {JBOSS_HOME}/server/${JBOSS_CONF}" cd "${JBOSS_HOME} /bin" && ./run.sh -c $ {JBOSS_CONF} -b 0.0.0.0 Via admin-console, change "DefaultDS" property "Check Valid Connection SQL" to: SELECT * FROM "INFORMATION_SCHEMA"."SYSTEM_SESSIONS"; Click "Save" Verify configuration change exists on the DefaultDS Configuration tab in admin-console Via admin-console, change "DefaultDS" property "Check Valid Connection SQL" back to Unset: Check "Unset" column next to property Click "Save" Verify configuration change exists on the DefaultDS Configuration tab in admin-console Here is where the bug seems to be as the Unset check is not retained
    • Similar Issues:
      Show 10 results 

      Description

      Configuration values can not be unset. For example, setting a datasource's "Check Valid Connection SQL" to a string, saving the configuration and then reverting back to the default by checking the "Unset" check-box next to the property, the string is retained after save and the Unset has no affect.

      This appears to be an issue with the UI not updating the Configuration object for the resource. In order for the org.jboss.on.embedded.ui.configuration.resource.ResourceConfigurationUIBean.updateConfiguration() method to actually push the configuration change into ProfileService as being "Unset" the value of the unset input field must be <null>. In the current case, it retains the old value and has no indication that it is "Unset".

      This appears to be the same (or similar) to JBNADM-2643 (https://jira.jboss.org/browse/JBNADM-2643).

        Issue Links

          Activity

          Hide
          Ian Springer
          added a comment -

          This is partially fixed (as fixed as I think is possible without changes on the JBAS side) in RHQ master. The fix was in the as5 plugin - see https://bugzilla.redhat.com/show_bug.cgi?id=694660 for details.

          Show
          Ian Springer
          added a comment - This is partially fixed (as fixed as I think is possible without changes on the JBAS side) in RHQ master. The fix was in the as5 plugin - see https://bugzilla.redhat.com/show_bug.cgi?id=694660 for details.
          Hide
          Larry O'Leary
          added a comment -

          This was resolved as per https://issues.jboss.org/browse/JBPAPP-5285?focusedCommentId=12619790&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12619790

          Ian Springer added a comment - 09/Aug/11 5:18 PM
          This is fixed in EmbJopr 1.3.4.SP5, which will be used for the EAP 5.1.2 admin-console.

          Show
          Larry O'Leary
          added a comment - This was resolved as per https://issues.jboss.org/browse/JBPAPP-5285?focusedCommentId=12619790&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12619790 Ian Springer added a comment - 09/Aug/11 5:18 PM This is fixed in EmbJopr 1.3.4.SP5, which will be used for the EAP 5.1.2 admin-console.
          Hide
          Larry O'Leary
          added a comment -

          This was verified as part of RHQ upstream https://bugzilla.redhat.com/show_bug.cgi?id=694660 and EAP downstream https://issues.jboss.org/browse/JBPAPP-5285 and is in Embedded JOPR 1.3.4.SP5

          Show
          Larry O'Leary
          added a comment - This was verified as part of RHQ upstream https://bugzilla.redhat.com/show_bug.cgi?id=694660 and EAP downstream https://issues.jboss.org/browse/JBPAPP-5285 and is in Embedded JOPR 1.3.4.SP5
          Hide
          RH Bugzilla Integration
          added a comment -

          Heiko W. Rupp <hrupp@redhat.com> made a comment on bug 694660

          Bulk closing of old issues that are in VERIFIED state.

          Show
          RH Bugzilla Integration
          added a comment - Heiko W. Rupp <hrupp@redhat.com> made a comment on bug 694660 Bulk closing of old issues that are in VERIFIED state.
          Hide
          RH Bugzilla Integration
          added a comment -

          Heiko W. Rupp <hrupp@redhat.com> changed the Status of bug 694660 from VERIFIED to CLOSED

          Show
          RH Bugzilla Integration
          added a comment - Heiko W. Rupp <hrupp@redhat.com> changed the Status of bug 694660 from VERIFIED to CLOSED

            People

            • Assignee:
              Ian Springer
              Reporter:
              Larry O'Leary
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: