Namespace support: naming collisions / redeclared types in different namespaces about gowsdl HOT 1 OPEN

Originally posted by @ieure in #218 (comment)

For #223, the issue is 100% gowsdl. It should probably put each ns' schema into its own subpackage based on its ns name, so you have svcX.DuplicateComplexType and svc1.DuplicateComplexType and the correct imports get added as needed.

I agree that this would be the correct approach if it can be made to work properly. There are a number reasons why I didn't try this yet:

1. The vast majority of type names do not collide. At least for those that don't, it is more cumbersome to have them in separate packages.
2. This would break backwards compatibility of gowsdl, since all definitions from separate XML namespaces would end up in new separate packages. This is relevant for scenarios where XML namespaces were used but no name collisions occurred.
3. I know for instance that dotnet-svcutil for C# does not create C# namespaces for this case. I just resolves the naming collisions by adding numbers (1, 2, 3, ...) to those type names that would otherwise create collisions with existing names in other XML namespaces. It leaves the non-colliding type names alone at global scope.
4. Personal reason: my limited experience with Go does not (yet) allow me to anticipate other problems that this approach might cause.

from gowsdl.