What steps will reproduce the problem?
1. Use a wsdl file that uses varying prefixes for the
same namespaces
2. Generated code will not properly account for the
differences in namespaces during deserialization of
XML returned from the service
What is the expected output?
Type identification should be solely reliant on the
provided URI, not the prefix used
What do you see instead?
Type identification during deserialization currently relies
solely on the prefix currently being used. If this does not
match up with the prefix used in the wsdl file type
identification won't work (xsi:type tags).
Web services that are consistent with their prefix usage
will work as expected
Please use labels and text to provide additional
information.
Original issue reported on code.google.com by madcow...@gmail.com on 10 Sep 2008 at 4:30
Original issue reported on code.google.com by
madcow...@gmail.com
on 10 Sep 2008 at 4:30