Hi > I found more issues down to the path where we have both OSOA and OASIS SCA > XML processors against the same in-memory model (OASIS-based). > > 1) We have to remove the Document processors and Model Resolvers from the > assembly-xml-osoa.
+1 > > 2) The "write" of the model is based on the Java type of the model. We now > have two processors registered against the same java type, one from > assembly-xml-osoa and the other from assembly-xml. They compete for the same > model and produce different behaviors depending who overrides the other one. > I think we need to record the version of the spec for the composite that was used to populate the model and then use this to find the appropriate processor for writing. Having the spec version available will likely be useful later on in processing the model also. If no one objects I'll add a spec version field to the composite model object. Simon
