Subject:Problem with build 377n & XSLT Mapper ?!? (didn't happen in 377m) Author:gavin clark Date:07 Oct 2005 05:00 AM
Hi,
using the latest version and I'm getting some very odd behaviour in XSLT mapper !.
When I run the scenario, each element is prefixed with an "a:" and also when I map an element in the source/target relationship it marks it as red ... and then the same elelment reappears at the bottom of the target document display.
This is causing a lot of problems as we're in the final testing cycle with our customer !.
Subject:Problem with build 377n & XSLT Mapper ?!? (didn't happen in 377m) Author:(Deleted User) Date:07 Oct 2005 12:26 PM
There is a bug in mapper tree.
This is what actually went wrong:
Starting from 377m mapper becomes namespace-aware.
If you will take a look at the following element:
<Invoice xmlns="schemas-bex-biz:Invoice-v3"> you
will see that default namespace is redefined. So,
when you map element from the source tree to the
target one mapper detects that namespace is different
and adds a prefix. It defines this prefix in:
the default prefix is redefined and there is no need to use "a:",
but this is not an issue. The issue is within target document
schema tree. This tree does not perform namespace lookup, so
for it default prefix and "a:" are different even if they are pointing to the same namespace. So, it shows all a: prefixed elements as not belonging to the target (in red) and all elements with default prefix
as target elements (this is why you are getting duplicates).
We will try to fix this issue in the next update.
Before this you can probably consider changing target document so
it will not redefine default namespace. If you could change
Subject:Problem with build 377n & XSLT Mapper ?!? (didn't happen in 377m) Author:(Deleted User) Date:12 Oct 2005 07:49 AM
No, only those that are using redefined default namespace. it's invoce and its children. Let me check where you can download earlier version,
I'll post its location here.