Won't Fix
Details
Priority
MajorAffects versions
Components
Assignee
UnassignedUnassignedReporter
Charles HedrickCharles Hedrick
Details
Details
Priority
Affects versions
Components
Assignee
Unassigned
UnassignedReporter
Charles Hedrick
Charles HedrickCreated June 5, 2010 at 6:11 AM
Updated August 14, 2017 at 2:02 PM
Resolved August 14, 2017 at 2:02 PM
The code in common SiteMerger gets the XML tag name in the import file, and looks it up using ComponentManager.get(serviceName). That means that the XML tag name is tied to the actual bean implementing the import. This is crazy. This is already out of date, so there's a list of old names to map to new names. And if there's ever a major redesign of Sakai, this is likely to be completely inappropriate.
You've got a function EntityManager.getEntityProducers() that will give you all of the entity producers. Why not just add a getTagNames() function to the API, and build a hash table of tag name to class? (I say getTagNames so that a class can handle more than one tag name, in case you need to change tag names or have one class handle multiple ones.)