Hello. I have a few WSDL documents that are a part of the same logical service. Some of them use datatypes that are defined by a standards body and I have the schemas (xsd files) that define those types.
The problem is that some of the WSDL files are obtained through some .NET interface after that thing "incorporates" the aforementioned standard datatypes while other WSDLs use: <xs:import namespace="http://www.std.org/namespaces/foo"; schemaLocation="foo2.4.xsd"/> That is, they import it from a local file that is located in the same place as the WSDL file. The problem is that when I run wsdl2java on these WSDL files, I get two different generated classes for some of those "standard datatypes". One is the thing that was generated from the local WSDL file that we obtained from the organization that defines these datatypes. This is the one we want. The other, however, is generated from that .NET WSDL that actually has those datatypes embedded instead of using an <xs:import namespace="..." schemaLocation="foo2.4.xsd"/> statement. Since this is .NET that's responsible for this we get some differences in cases and that results in two different classes being generated for the same datatype that only have changes in letter cases but are otherwise exactly the same. Most importantly, the namespace is the same! So, to summarize: My question is whether it's at all possible to tell wsdl2java to use a specific schema file for a particular namespace instead of using the definition within the WSDL file that is being processed. That WSDL file does contain the definition of the types for a particular namespace but I would like to override that and instead use the definition that is in a seperate schema file (the one that comes directly from the organization that defined the data structure). I hope I'm making myself understood, If not, please don't hesitate to fire back some questions. It's really desirable for us that the same class versions be used for these datatypes instead of having to convert between those two different versions that are currently being generated. Kind regards, Stefan Freyr.
pgptkl6k9lvod.pgp
Description: PGP signature
