Wrong namespace after import type from WSDL

Topics: Service Factory Modeling Edition Forum
Apr 24, 2008 at 1:12 PM

I'm not quite sure if it is a bug or intended behavior but if I use the XSD Type Picker to pick an element from a schema to fill the Element property of a XSD Message in the Service Contract Designer then the namespace of the Service contract is used and NOT the namespace of the element defined in the schema. OK - I can manually override the namespace but that is rather confusing because it can be easily forgotten. If I'm using a contract first approach then I will most probably end up with two different WSDL schema definitions - the original end the new one.


Apr 25, 2008 at 9:09 PM
You are right. In that case, the ns of the schema will override the element ns. I agree that this might be a bit confusing and the element property value should be disabled for this scenario. Nevertheless you should not end up with two different scenarios because the ns in the attributes types are the same as your schema definition so if your get a schema back from the generated types they should have the same ns.