[MAGNOLIA-7434] Improve AbstractI18nContentSupport#hasProperty performance Created: 24/Dec/18 Updated: 31/Aug/21 |
|
| Status: | Open |
| Project: | Magnolia |
| Component/s: | i18n |
| Affects Version/s: | 5.7.1 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Viet Nguyen | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| 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)
|
||||
| Description |
|
info.magnolia.cms.i18n.AbstractI18nContentSupport#hasProperty checks the presence of the property by calling getProperty(javax.jcr.Node, java.lang.String) that throws an exception if the property does not exist. Exceptions are expensive (especially when having deep stack traces) in term of performance and the method hasProperty is called a lot. A new i18n supported 'hasProperty' implementation which consider to performance optimization is expected. |