ICEfaces
  1. ICEfaces
  2. ICE-9276

Add additional FileEntry properties for FacesMessage customisation

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 3.3
    • Fix Version/s: None
    • Component/s: ACE-Components
    • Labels:
      None
    • Environment:
      ALL

      Description

      These are the existing message bundle keys for FileEntry:

      org.icefaces.ace.component.fileEntry.UPLOADING
      org.icefaces.ace.component.fileEntry.SUCCESS
      org.icefaces.ace.component.fileEntry.INVALID
      org.icefaces.ace.component.fileEntry.MAX_TOTAL_SIZE_EXCEEDED
      org.icefaces.ace.component.fileEntry.MAX_FILE_SIZE_EXCEEDED
      org.icefaces.ace.component.fileEntry.MAX_FILE_COUNT_EXCEEDED
      org.icefaces.ace.component.fileEntry.REQUIRED
      org.icefaces.ace.component.fileEntry.UNKNOWN_SIZE
      org.icefaces.ace.component.fileEntry.UNSPECIFIED_NAME
      org.icefaces.ace.component.fileEntry.INVALID_CONTENT_TYPE
      org.icefaces.ace.component.fileEntry.PROBLEM_WITH_CALLBACK

      The existing FileEntry properties for overriding these are:

      String maxTotalSizeMessage
      String maxFileSizeMessage
      String maxFileCountMessage
      String requiredMessage

      Definitely we should add one for successMessage and arguments could be made for invalidMessage, unknownSizeMessage, unspecifiedNameMessage, invalidContentTypeMessage, problemWithCallbackMessage. Although we haven't yet added the feature for specifying invalid contentTypes.

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              Mark Collette
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: