[VELOCITY-21] Why is Context orthogonal to the Collections API

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.1
• Fix Version/s: 1.5
• Component/s: Build
• Environment: Operating System: other; Platform: All
• Bugzilla Id: 4321
• Assignee: Unassigned
• Reporter: Dale King
• Created: 21/Oct/01 23:06
• Updated: 11/Feb/11 11:23
• Resolved: 13/Sep/05 12:40

Description

I have a set of mappings that I loaded into a java.util.Properties object that
I need to use in my template rendering. For some reason you have this Context
interface which is little more than a renamed java.util.Map. Why do you have
your own separate implementations for what should just be standard collections
classes? In order to make those properties available, I end up having to create
a context and copy the settings from the Properties object one, by, one. Why
not just use Map instead of Context?