Menu
▾
▴
#194 NameSpace issue in XML mapper
Build 5.0.1.34:
I have created input xml file with different Namespaces for Parent and child but same prefix.
Created XML Mapper BizComp and mapped source and target elements.
When executed the BizView following result is displayed:
<Document>
<Element>
<Amt>77</Amt>
<Curd xmlns:p_1="http://services.soa.synovus.com/CDIR">%xa-input::/p_1:CurrentTermAmt/p_1:CurCd%</Curd>
</Element>
</Document>
Second element Curd value which have different Namespace is not substituted.
Note: Same test is executed correctly in 4.5.
And also when we map source element which have different namespace to the target element, intialy it is not showing mapped element in Target. But if we select Source element again and try to drag n drop, it is showing mapping.
Please find the attached test case.
Logged In: YES
user_id=1930993
Originator: NO
The wizard needs to resolve this type of namespace collision at design time (by renaming prefixes as necessary), so that different components of a path will never use the same prefix, if those components point to different URIs.