yes, this is a major bug in xml schema/wsdl. utilizing the xml namespace prefixes inside of attribute values was a giant mistake (since the prefix values themselves are not significant, only placeholders for the actual namespaces). unfortunately, i don't know of any good solution to the problem (i've had to implement virtually the same sort of idea: merging multiple user defined schemas into one schema/wsdl). i do know that xerces has an xml schema model api, but i don't know if it has support for merging together multiple schemas and generating the resulting output.
↧