RE: [xml-dev] contradictory loader ordering in 3.5

Richard Unger wrote:

> I could do that, but I'd have to make xml.core.XMLDataObject not final :)

There are good reasons to keep it final. You can see that it's
getting more and more lightweight in every release moving its
functionality into various supports. Finally it should disappear
at all (see FSExtension proposal). 

I can suggest copy pasting it if you really need its hardwired node
and cookies plugging mechanism. It's not designed for subclassing.

Look XSLDataObject, EntityDataObject and SchemaObject for examples
(well missing the synchronizer capabilities). Let me know what 
functionality you need to factor out and I'll do it for the next
release more likely that unfinalizing it :-).

  Cc.