06-29-04 12:29 AM
I did change the target namespaces to make them different, and it did not
seem to help. And, the other suggestion did not work either for me
(although I'm glad it did work for Mark).
In the end, I found if I seperated the schema by placing them in their own
assemblys, the problem went away. This is not an ideal solution because I
have more projects that I really need. but, it get me past this dilema for
now. For more info on this topic, see "schema resolution in pipeline
components" in the online help.
Good Luck!!
JimM
"Junaid" <junaid_ahsan@hotmail.com> wrote in message
news:44d1a7ca.0406280940.358c81e3@posting.google.com...
> Jim,
>
> Are you using target namespaces? If you are not that might be the
> issue - as dis/assemblers need that to match the message with a
> document specification.
>
> BTW, if you are successful in resolving document specification with
> mainpulating typenames without using namespaces do let me know how -
> as so far I have not been very successful with this.
>
> thanks,
>
> Junaid.
>
> Ram <Ram@discussions.microsoft.com> wrote in message
news:<3EF1F9E9-13D5-41D3-A130-E474EA4D7E1C@microsoft.com>...[vbcol=seagreen]
click on schema and select properties to change the Typename.[vbcol=seagreen]
in a project, but I keep getting the following error:[vbcol=seagreen]
the type: "xxxx". Either the schema is not deployed correctly or more than
one schema is deployed for the same message type.[vbcol=seagreen]
[ Post a follow-up to this message ]
|