[MAGNOLIA-1389] PropertyInitializer should be able to use unqualified (without domain) server name Created: 18/Feb/07 Updated: 18/Feb/07 Resolved: 18/Feb/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 3.0.1 |
| Fix Version/s: | 3.1 M1 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Fabrizio Giustina | Assignee: | Fabrizio Giustina |
| 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)
|
| Description |
|
When propertyIntializer select a configuration file using the server name, it's not clear when you should use a fully qualified server name (server.something.com) or simply the server name. It's not clear which of them InetAddress.getLocalHost().getHostName() will return and so it would be better to always been able to use the "simple" name. |
| Comments |
| Comment by Fabrizio Giustina [ 18/Feb/07 ] |
|
Committed to trunk: PropertyInitializer will still use also a full server name, but it will output a deprecation warning with the "correct" server name you should use |