Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-8737

Stunner - Process with empty Class Name Import doesn't build

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 7.26.0.Final
    • Designer
    • NEW
    • NEW
    • Hide
      1. Create empty project with simple process: Start->End
      2. Add empty Default Import
      3. Save dialogue, Save process, build & deploy project
      Actual Result

      Build failed. In Alerts panel you will see an error:

      [KBase: defaultKieBase]: unable to parse xml : Exception class org.xml.sax.SAXParseException : <import> requires a 'name' attribute
      Expected Result

      Empty Import should be automatically removed when user saves/closes Imports dialogue.

      Show
      Create empty project with simple process: Start->End Add empty Default Import Save dialogue, Save process, build & deploy project Actual Result Build failed. In Alerts panel you will see an error: [KBase: defaultKieBase]: unable to parse xml : Exception class org.xml.sax.SAXParseException : <import> requires a 'name' attribute Expected Result Empty Import should be automatically removed when user saves/closes Imports dialogue.
    • 2019 Week 41-43 (from Okt 7), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 40-42 (from Sep 28), 2020 Week 43-45 (from Okt 19), 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21), 2021 Week 04-06 (from Jan 25), 2021 Week 07-09 (from Feb 15), 2021 Week 10-12 (from Mar 8)

      It is possible to save empty Class Name Import. Process with empty Class Name Import doesn't build with not clear message:

      [KBase: defaultKieBase]: unable to parse xml : Exception class org.xml.sax.SAXParseException : requires a 'name' attribute

      As part of this issue, another related issue can be fixed:

      • It is possible to set the same import twice (doesn't cause any build/runtime issues)

      If it is not rational it can be moved to separate task.

              josephblt Wagner Lemos (Inactive)
              kgaevski@redhat.com Kirill Gaevskii
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: