[MAGNOLIA-1090] missing path attribute on workflow item produces stacktrace and incomplete rendering of inbox. Created: 27/Sep/06 Updated: 23/Jan/13 Resolved: 10/Oct/06 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.0 RC3 |
| Type: | Bug | Priority: | Major |
| Reporter: | Chris Miner | Assignee: | Philipp Bärfuss |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| 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 |
|
I removed the path attribute of a workflow item and found that this produced a stack trace when the inbox was accessed. |
| Comments |
| Comment by Chris Miner [ 27/Sep/06 ] |
|
The stacktrace is related to the possiblility of InboxListModelIterator.getValue(String, Object) returning something other than a StringAttribute. In that case the cast can fail. With no path at all you get an empty string. |
| Comment by Chris Miner [ 04/Oct/06 ] |
|
This bug is now found in the InboxValueProvider getValue(String, Object) method. |