Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 9.2.0, 10.0.0
    • Fix Version/s: Backlog
    • Component/s: Camel Editor
    • Labels:
      None
    • Steps to Reproduce:
      Hide
      • add a global bean (go through the whole wizard and click Finish)
      • select the created global bean and click on "Edit"
      • click on "Add"
      • provide values for the fields and click "Ok"
      • Click Cancel
        --> if you go to source file, the provided values are stored although cancel was clicked
      Show
      add a global bean (go through the whole wizard and click Finish) select the created global bean and click on "Edit" click on "Add" provide values for the fields and click "Ok" Click Cancel --> if you go to source file, the provided values are stored although cancel was clicked

      Description

      Brian comment:
      "That's an interesting bug you've discovered with not being able to cancel the wizard and not effect changes to the model after doing changes in the wizard. It seems to be a flaw in the Global Element framework at the moment because the SAP wizard has the same problem.

      When we pass the XML element to the wizard, we're essentially giving it free reign to edit the in-memory model with no way to return to the initial state. I'm not quite sure how to remedy that at this point."

      Update: Not an issue on SAP, must have been fixed sometime in last 6 months. And PR fixes issue with Bean wizard.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                aurelien.pupier Aurélien Pupier
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: