That doesn't seem sufficient to me. What's the package name? What
about classes that should represent multiple element types? What about
the different semantics associated with different namespaces? Suppose
you want the element and class names to be different, perhaps because
you and your users work with different natural languages? (And I'll
confess to having deferred the homework to finding out exactly how
XML names and Java names differ! I'd expect them not to be the same.)
The model I'm working with right now does include a mapping of name
to class, but it's not direct (e.g. can be many to one) and is aware
of namespaces. It can be statically configured (e.g. an XML element
containing mappings -- embedded, or in a separate document) as well
as algorithmically configured (i.e. a factory class).
- Dave