Bug 361687

Description Rob Cernich 2011-10-21 12:02:16 EDT

Build Identifier: 

Please see forum post for additional details: http://www.eclipse.org/forums/index.php/t/245319/

Simply put, allow developers to define the XML element name on the model class representing the element.  This saves the developer from having to define a mapping in the containing class, moving that concern to the actual class managing the details of the element.  In other words, the contained elements provided their own names.

This becomes very useful when an element type may be extended (e.g. abstract XML types), especially when the specialized types are contributed dynamically (i.e. not known at the time the Sapphire model is created).

A side benefit is that it saves the developer from having to provide a mappings in the containing class.

Also refer to bug #360371 which allows developers to provide an alternate default naming.  It would be useful, in conjunction with this if the default name were generated using the name provided on the extended element, in the event no mapping is provided on the containing class.  Such a strategy would also provide backward compatibility for existing models. 

Reproducible: Always