Trying to merge a type definition from multiple (potentially conflicting) XSD parts can cause lots of problems. A type should have a single corresponding XSD type that defines it. The extensible namespaces feature is really intended to allow one to "extend the namespace" by adding new types, not to "extend the definitions of existing types" in a namespace.
Frank. "ext2" <[email protected]> wrote on 09/20/2010 02:57:10 AM: > [image removed] > > SDO ExtensiableNamespaces cannot extend? > > ext2 > > to: > > user > > 09/20/2010 03:01 AM > > Please respond to user > > Hi: > We can create namespace extensible HelperContext or un-extensiable > HelperContext. > But while using namespace extensible HelperContext to load types from two > xsds( they both has same target namespace , but different schema > definition). > Types loaded from the second xsd will replace the types loaded from the > first xsd; > > Why not extending the types? > > Thanks any suggestion. > > >
