Uploaded image for project: 'AdMaxLocal'
  1. AdMaxLocal
  2. AML-132

SGS: No error thrown in log when an invalid BA or BL is used

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.1.1
    • Fix Version/s: 1.1.1
    • Labels:
      None
    • Environment:

      SMB Server: optus-qa-smb1 (50.57.178.209)

      SMB Services Build: optus-ear-1.1.1-SNAPSHOT-p78-t20120215-144058-CI.ear

      Description

      Steps:

      1. Send a siteGen deploy request that has an invalid primary Business Area ID, say <primaryBusinessAreaID>1</primaryBusinessAreaID> or <primaryBusinessLocationID>1</primaryBusinessLocationID>

      2. Check the jboss server.log to see if the deployment throws any error.

      Expected:

      It would be nice to have a clear error thrown to end user saying that an invalid BA has been used in siteGen deploy.

      Actual:

      No error is thrown. Attached the generated logs.

        Attachments

        1. SGS_log_Invalid_BA.txt
          5 kB
          Gurpreet Singh
        2. SGS_log_Invalid_BL.txt
          5 kB
          Gurpreet Singh

          Activity

            People

            • Assignee:
              jason.stedman Jason Stedman (Inactive)
              Reporter:
              gurpreet.singh Gurpreet Singh
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: