[TILES-416] wildcard order of tile definitions is not preserved

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.2
• Fix Version/s: 2.1.3
• Component/s: tiles-core
• Flags: Patch
• Assignee: Antonio Petrelli
• Reporter: Lukasz Racon
• Created: 19/May/09 20:48
• Updated: 29/Oct/09 08:52
• Resolved: 15/Jun/09 21:13

Description

Tile definitions are stored in HashMap which does not preserve the order from the tiles definition XML.

If you define these two:
<definition name="test.def*.sub*" template="/test

{1}.jsp">
<definition name="test.def*" template="/test{1}

.jsp">

and try to resolve definition name like "test.defName.subLayered" you may get either.

Order that depends on tile name hashCode and hash table implementation does not sound like a good idea. When table reaches load threshold it may give you different result. For example adding 13th tile definition (Hash table has default capacity: 16 and .75 load factor) triggers resize function that may reorder tile definitions - tiles that worked before may suddenly stop working.

Same issue was reported here:
http://markmail.org/message/cgazkho4qndlgo6d