[CONTEDIT-63] Get rid of content editor specific JCRNodeAdapter extensions Created: 20/Mar/17 Updated: 27/Mar/17 Resolved: 21/Mar/17 |
|
| Status: | Closed |
| Project: | Content Editor |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Aleksandr Pchelintcev | Assignee: | Aleksandr Pchelintcev |
| Resolution: | Fixed | 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)
|
||||||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||||||
| Epic Link: | Initial Article editor | ||||||||||||||||
| Sprint: | Basel 88 | ||||||||||||||||
| Story Points: | 3 | ||||||||||||||||
| Description |
|
There're are two extensions of JCR Node apaters atm in the content editor module: one for the JcrNodeAdapter itself, the other - for its "new" variation. The wrappers exist for one purpose: auto-generate the queried Vaadin item property if the corresponding property exists in JCR (or just create it for the new node adapter). This behaviour seems to be conflicting with other node adapter related features and at least for the case of JcrNodeAdapter - duplicate the logic that is already there! We should remove those wrappers and probably swallow the bullet and explicitly add the properties to the items when they're missing (luckily we can add such logic to the block model implementation). |