I'm a fan of not only richness, but also simpleness. Let me refine my proposal a little bit not to break the simpleness of the Programming Model.
We can still return normal type for get/set( "implementation") for users don't care substitution element instance and keep the simple PM. At the same time, we can make getSequence( "implementation") to return a Sequence for users to set/get substitution element instance. The new proposal won't change the spec a lot except for the new feature/support appending. On 6/21/06, Yang ZHONG <[EMAIL PROTECTED]> wrote:
Sequence is the only public API today to SET substitution element instance and GET the substitution element instance. I am proposing mapping substituted property to Sequence, e.g. "implementation" property returns Sequence INSTEAD OF a normal type. If we can do that, SDO users are enabled to set and get substitution element instance which can't be done today. After we do that, we can hide/discard "implementationGroup" or just delegate "implementation" to "implementationGroup". I guess the proposal needs to change the spec, unfortunately. -- Sincerely Yang ZHONG
-- Sincerely Yang ZHONG
