[MGNLDAM-370] DAM Dialog saves ID (UUID) with the prefix jcr: e.g. jcr:cafebabe instead of cafebabe Created: 14/Jan/14 Updated: 19/May/14 Resolved: 16/Jan/14 |
|
| Status: | Closed |
| Project: | Magnolia DAM Module |
| Component/s: | None |
| Affects Version/s: | 1.2.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical |
| Reporter: | Tom Wespi | Assignee: | Jan Haderka |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | maintenance, quickwin | ||
| 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
|
| Release notes required: |
Yes
|
| Date of First Response: |
| Description |
|
This leads to a lot of NPE in any getById functions. reproduce:
|
| Comments |
| Comment by Magnolia International [ 16/Jan/14 ] |
|
How is this "specified" when we don't describe which dialog were talking about, why it's a problem (jcr: is the dam provider prefix in this case), what NPEs are thrown where/why (a session.getNodeById doesn't throw an npe, if client code doesn't check for returned nodes and ignores InvalidUuidEx that's another issue...), and what we plan to do about it. |
| Comment by Jan Haderka [ 16/Jan/14 ] |
|
This is actually by design. |