[Home] [By Thread] [By Date] [Recent Entries]
>> > I'd prefer to have the Element contain a "userObject" >> > pointer to the business object. > >Such a delegation approach is necessary in any case, since >it's important to integrate into frameworks that already >define their own base class. Is it sufficient? Hmmm ... >almost certainly not, IMHO. Even so, it's on the roadmap. This is part of the capability being added to Coins release 2 (Early access now, general release end of this month). Coins will wrap user objects, with support for things like EventListener registration between user objects specified in the CSchema as a kind of refId attribute. What I'm trying to do with it is demonstrate the use of XML to compose an awt program from a mix of standard awt components and user application code. Bill xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|

Cart



