[MAGNOLIA-6187] I18nizer can't work with already proxied objects Created: 29/Apr/15 Updated: 11/May/15 Resolved: 29/Apr/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | configuration, i18n |
| Affects Version/s: | None |
| Fix Version/s: | 5.4 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Description |
|
With the current implementation of ProxytoysI18nizer, one can't i18n-decorate an object that's already been otherwise proxied. This is a problem with e.g the new configuration mechanism, which also relies on proxies, e.g to implement NamedDefintion. |
| Comments |
| Comment by Magnolia International [ 30/Apr/15 ] |
|
Done on feature/ |