Hi, Eike,

I'd like to take a moment to express my appreciation for the
introduction of the CDOTextResource in the Kepler release of CDO. It
is as manna from Heaven.

In one day I was able to port the Property Sheet customization models
of Papyrus into a CDO repository. These comprise a few EMF models
(normally stored as XMI in the workspace metadata area) and a very
large number of XWT UI definition files (XML text). I can efficiently
toss these into the repository via CDOTextResources and load them

* via a custom URIHandler into XMI resources as expected by Papyrus
for editing the
customization model in an EMF-style editor

* via a custom URLStreamHandler (as URLs) into the XWT UI rendering engine

With a repository running on the local host on an SSD, it's as smooth as silk!

I encourage everyone to investigate what they can do with
CDOTextResource (and, I suppose, CDOBinaryResource). Have a look at
the r10523 revision of the cdo_kepler branch in the Papyrus SVN if you
want to see how they work for me.

Thanks,

Christian