tag:blogger.com,1999:blog-198418411689889330.post2610675625210535863..comments2024-03-14T02:51:06.486-07:00Comments on SOA , Oracle Fusion Middleware , Weblogic, Java and Cloud..: Dealing with Multiple Sources in XSLT in SOA 11gSridharhttp://www.blogger.com/profile/01939149207884236898noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-198418411689889330.post-21628131599299904392019-04-25T01:17:22.158-07:002019-04-25T01:17:22.158-07:00Oracle apps and Fusion Self Paced Training Videos ...Oracle apps and Fusion Self Paced Training Videos by Industry Experts. Please visit <a href="https://oracleappsfusion.teachable.com/" rel="nofollow">https://oracleappsfusion.teachable.com</a>rajeevhttps://www.blogger.com/profile/01710655696788199203noreply@blogger.comtag:blogger.com,1999:blog-198418411689889330.post-36008972467467804202018-03-27T05:47:17.205-07:002018-03-27T05:47:17.205-07:00Thank you, really usefulThank you, really usefulRakeshhttps://www.blogger.com/profile/01761926476625166505noreply@blogger.comtag:blogger.com,1999:blog-198418411689889330.post-28498911823488053082016-06-06T07:18:23.267-07:002016-06-06T07:18:23.267-07:00Hello Sridhar, I have a similar requirement in my ...Hello Sridhar, I have a similar requirement in my xslt. I have been able to add multiple sources to the xslt. While I'm building the my SOA Composite, am getting the below exception.<br /><br />Error(199): Namespace prefix "" qualifying "inputVariable.payload" cannot be resolved.<br /><br />Below is my analysis so far with this issue<br />---------------------------------------------<br />1) Am facing this compilation issue when I build the SOA Composite in the version 11.1.1.7.0. Composite compiles properly in 11.1.1.6.0<br />2) The compiler is able to identify the first source properly but it is not recognizing the second , third etc properly and it complains in all the places about namespace not resolved.<br /><br />Note : Our build server uses the SOA 11.1.1.7.0 libraries to build the composites. But the project compiles properly on the 11.1.1.6.0 jdeveloper properly.<br /><br />Can you please shade some light on this?<br /><br />Regards<br />AshokAshokhttps://www.blogger.com/profile/06809022145953123106noreply@blogger.comtag:blogger.com,1999:blog-198418411689889330.post-63606843262585105502015-12-17T04:25:03.469-08:002015-12-17T04:25:03.469-08:00Useful information, thank you.
I am wondering wh...Useful information, thank you. <br /><br />I am wondering whether it is possible to pass parameters into a transform in a routing rule in Mediator in Soa SUite 11g, or can it only be done within Bpel?<br /><br />thanks<br />Lisa<br />Lisahttps://www.blogger.com/profile/08491361207907482981noreply@blogger.comtag:blogger.com,1999:blog-198418411689889330.post-47360373592781963802013-11-07T00:26:35.870-08:002013-11-07T00:26:35.870-08:00based on the above lines, i have a requirement whe...based on the above lines, i have a requirement where 1 source contains employee records and other source contains employee and dependent records. They will be joined based on the SSN no. I need to generate target with employee and multiple dependents. Currently with above approach, the target file is only has Employee and 1 dependent. It is not generating for other dependents<br />Ex: Source 1 record: ESSN, DOB, DTHIRE etc<br /> Source 2 record: ESSN, DOB, MEDSTATUS, ACTDTAT etc<br /> DSSN, DOB, ESSN, NEWSTAT, BUILDSTAT etc<br /> DSSN1, DOB1, ESSN, NEWSTAT1, BUILDSTAT1 etc<br /><br />the target should contain:<br /> Layout1: ESSN, DOB, MEDSTATUS, ACTDTAT etc<br /> Layout2: DSSN, DOB, ESSN, NEWSTAT, BUILDSTAT etc<br /> DSSN1, DOB1, ESSN, NEWSTAT1, BUILDSTAT1 etcAnonymousnoreply@blogger.com