[news.eclipse.tools.emf] Re: Is there a way to extend EFactories?

[Ed Merks <Ed.Merks@xxxxxxxxx>]

Paul,

For writing you could specialize XMLSaveImpl.shouldSaveFeature to omit 
things.   Although I'm not sure I understand why you'd ever need to read 
a v2 thing and write out a v1 thing...  Perhaps the problem is simpler 
than you imagine?


Paul Fullbright wrote:
> Ed,
>
> > > > It's nice that the schema has a version attribute, but that doesn't 
> > > > help you distinguish which version any particular instance will be 
> > > > using.
> > >
> > > It does help actually.  We use a custom content describer that 
> > > introspects the root element, namespace, and version,
> > So the document has a version?  The schema version attribute doesn't 
> > help...
>
> Yes it does.  My example does not, however.
>
> > > Talk to Sun.  :)  Though all the schema changes are not 
> > > incompatible.  Anything valid under v1 will also be valid under v2 
> > > (if my example didn't have this, that's my fault.)
> > So can't you just use the new model for reading old instances then?
>
> For reading, we could.  For writing, not so much.
>
> Thanks,
> Paul