[MAGNOLIA-6954] Optimise Jsoup usage in DefaultMessageBundlesLoader Created: 09/Feb/17  Updated: 23/Mar/17  Resolved: 09/Mar/17

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 5.4.12, 5.5.3

Type: Improvement Priority: Neutral
Reporter: Ilgun Ilgun Assignee: Hieu Nguyen Duc
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 2d 2.5h
Original Estimate: 3d

Issue Links:
Relates
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Sprint: Saigon 86
Story Points: 3

 Description   

Ideally, we should be parsing those input files once and just delegate to org.jsoup.safety.Cleaner for #isValid() and #clean().
Therefore we would have less overhead and potentially better performance (although it's not very observable)

Reconsider the usage of it in the legacy lookup.


Generated at Mon Feb 12 04:19:23 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.