Uploaded image for project: 'Fuse Tools'
  1. Fuse Tools
  2. FUSETOOLS-188

show the actual validation error message when 1 error on a Properties view rather than "1 error detected"

    Details

    • Type: Enhancement
    • Status: Closed
    • Priority: Trivial
    • Resolution: Out of Date
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Camel Editor
    • Labels:
      None

      Description

      when editing the Properties fields on a node (e.g. typing a non-numeric into a number field like closeCorrelationKeyOnCompletion or completionSize on Aggregate - the error message on the title section of the Properties view shows "1 error detected" rather than showing the actual error.

      It would be nicer to just show the one error message there

        Gliffy Diagrams

          Activity

          Hide
          jastrachan James Strachan added a comment - - edited

          did some investigation. Seems that MessageManager.ControlDecorator.createPrefix() ensures that the prefix is never null but always "" if you install a IMessagePrefixProvider which returns null (or set the IMessagePrefixProvider to null).

          Then MessageManager.update(ArrayList) only ever shows 1 error when the prefix is null (which it can never be) so not sure if we can fix this one

          Particularly as I see no way to switch the MessageManager implementation; the update* methods are all private and there's no way to look at the MessageManager and find out what the current Messages are to then interact with the prefix or explicitly set the Form text based on the number of messages available!

          Bizarre!

          Show
          jastrachan James Strachan added a comment - - edited did some investigation. Seems that MessageManager.ControlDecorator.createPrefix() ensures that the prefix is never null but always "" if you install a IMessagePrefixProvider which returns null (or set the IMessagePrefixProvider to null). Then MessageManager.update(ArrayList) only ever shows 1 error when the prefix is null (which it can never be) so not sure if we can fix this one Particularly as I see no way to switch the MessageManager implementation; the update* methods are all private and there's no way to look at the MessageManager and find out what the current Messages are to then interact with the prefix or explicitly set the Form text based on the number of messages available! Bizarre!
          Hide
          lhein Lars Heinemann added a comment -

          Closing old issues raised for IDE 1.x and 2.x which where not updated for almost 1.5 years. Please reopen and update the issue if needed.

          Show
          lhein Lars Heinemann added a comment - Closing old issues raised for IDE 1.x and 2.x which where not updated for almost 1.5 years. Please reopen and update the issue if needed.

            People

            • Assignee:
              lhein Lars Heinemann
              Reporter:
              jastrachan James Strachan
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: