Hi,

I have a solution which includes two maps that have custom XSLT paths
defined, and each has two source schemas. In both maps the two source schema
s
have blank target namespaces (forced upon me by third parties).

Every time I open either of these maps, the Message Part Type of the second
source schema reverts to the same Type as the first source schema. This
message appears as a consequence "The signature of map <blah> has
changed....". To fix the problem, I have to reselect the second schema from
the dropdown list and the Message Part Type corrects itself. But this happen
s
every time I open the map! Also, the custom XSLT path does not persist, but
is that "by design"? The maps compile correctly and run correctly, but the
designer seems content on screwing them up every time I open them.

My solution has lots of complex maps, and only the custom XSLT maps with
multiple source schemas cause a problem.

What's happening with this strange behaviour?

Thanks!

[ Post a follow-up to this message ]