[MAGNOLIA-1282] Modules : displayName is not set correctly Created: 19/Dec/06 Updated: 23/Jan/13 Resolved: 19/Dec/06 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 3.0.1 |
| Fix Version/s: | 3.0.2 |
| Type: | Bug | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| 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
|
||||||||
| Description |
|
Depending on the order in which Betwixt fills the ModuleDefinition bean, the displayName might or not be set properly. This is due to some fallback logic in the setName method, which should really be in the getDisplayName method instead. |
| Comments |
| Comment by Magnolia International [ 19/Dec/06 ] |
|
Actually, this is not related to the order in which Betwixt fills the ModuleDefinition bean - eventhough the setter should still be fixed - but simply to the fact that the betwixt config file does not match the dtd. Some module definition xml files are using <display-name> : those are set properly by betwixt, but are invalid against the dtd (which we don't check at the moment). Others use <displayName>, which is valid against the dtd but currently not set by betwixt. Will change the betwixt configuration and appropriate module definition xml files so that we use <displayName> everywhere. We should also validate against the module.dtd |
| Comment by Magnolia International [ 19/Dec/06 ] |
|
See |