Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.20.0
    • Component/s: camel-core
    • Labels:
      None
    • Estimated Complexity:
      Novice

      Description

      Please heck Pattern.compile usage across Camel source code - also not direct usage.

      For example:
      Whenever one of these methods are used from String class a Pattern.compile() is utilized:

      • matches
      • replaceFirst
      • replaceAll
      • replace
      • split: has an optimization and for certain characters it doesn’t use Pattern.compile.

      For example:
      GenericFileConsumer.isMatched calls name.matches(endpoint.getExclude())
      GenericFileEndpoint could contain also excludePattern as well.

      Possible solution:
      Walk through the code and replace usages of these methods with static Pattern variables.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                davsclaus Claus Ibsen
                Reporter:
                matihost Mateusz Nowakowski
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: