[
https://issues.apache.org/jira/browse/CAMEL-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401303#comment-13401303
]
Claus Ibsen commented on CAMEL-5398:
------------------------------------
Frankly the compiler should IMHO be able to optimize this code itself, as if
the input to the replace methods is a fixed string, then its not changed at
runtime. And thus the compiler could take advantage of that.
Could you maybe do a test to see if you can measure and speed difference?
> Optimize String.replaceAll() to cache Patterns where suitable
> -------------------------------------------------------------
>
> Key: CAMEL-5398
> URL: https://issues.apache.org/jira/browse/CAMEL-5398
> Project: Camel
> Issue Type: Improvement
> Reporter: Henryk Konsek
> Assignee: Henryk Konsek
> Fix For: 2.11
>
>
> Inspired by issue [1] regarding performance of JMS headers, I performed a
> little search in IDE and found out that there's pretty much not optimized
> String.replaceAll() calls.
> I think it will be good to search the code base for such calls again and
> replace them with references to the static pre-compiled
> java.util.regex.Patterns. Of course if such action makes sense (like in
> StringHelper#removeQuotes()).
> [1] https://issues.apache.org/jira/browse/CAMEL-5396
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
