Re: Re: xmi.extension

Hi,
you could certainly write your own XMIReader/XMIWriter implementation
(either from scratch or by extending/delegating to the existing one) to
be able to handle either xmi.extensions or import/export from/to the
additional file. But to take full advantage of MDR you should rather
model the extension in MOF and cluster the UML metamodel into your
extension model. This way the XMI generated from your metamodel will
need no <xmi.extensions> tags and you can still export fully
UML-compliant XMI by exporting just the instances of UML packages (not
your extensions).
It should be quite easy to provide a simple hook into XMIReader and
XMIWriter to allow plugging xmi.extension handlers, however we had no
plans for doing it, since nobody requested it.
Regards,
Martin

On Thu, 2004-05-06 at 22:38, [email protected] wrote:
> Hi Martin,
> 
> Can't I tune the MDR load/save mechanism for parsing/generating myself the <xmi.extension> portions of my xmi files????
> If not are you meaning that MDR won't handle this xmi feature at all???
> 
> The perfect situation for me would be :
> 
> - storing extension to METAMODEL in a sepparate file to the UML metamodel
> 
> - storing these extension data in the same file as the model (with xmi.extension tag) 
> 
> Is this possible with MDR????
> 
> Regards,
> 
> -------------------------------------------------------------
> NetCourrier, votre bureau virtuel sur Internet : Mail, Agenda, Clubs, Toolbar...
> Web/Wap : www.netcourrier.com
> Téléphone/Fax : 08 92 69 00 21 (0,34 € TTC/min)
> Minitel: 3615 NETCOURRIER (0,16 € TTC/min)
>