HI Experts,
Issue Resolved.
When i'm generating the XSD from the B2B cockpit, initially i gave the namespace under which i have to store in PI. But now when i'm generating the XSD i gave my Service interface namespace and stored in the different namespace which i mentioned above.
Thank you very much for your inputs.
Thanks,
Satish.
Hi Satish,
I believe it could not be due to the namespace prefix, just because it is irrelevant what is the prefix, important is the namespace. Prefix is just its shortcut...
So If I understand correctly, you have defined a Service Interface in a Software Component A and would like to use a external definition for this Service Interface from Software Component B... Perhaps just check if your dependency in ESR are maintain, like here for C4C Content...
Here you should be able to use in COD_ERP_INT_IC External Definition from COD_ERP_INT...
Best regards,
Milan
Hello Satish,
SAP note 2350224 SAP JVM 8.1 Patch Collection 23 (build 8.1.023), documents a change to how namespace values are handled. I suspect this is related to the issue you have mentioned here.
This change comes to fix this official JDK bug: https://bugs.openjdk.java.net/browse/JDK-8162598. After this change, the default namespace of XSL templates is handled correctly (previously it was not!). According to the w3.org documentation, an empty string cannot be used as a namespace name (see http://www.w3.org/TR/xml-names/#iri-use).
In this case, you may need to add xmlns="http://<your_namespace>" to the xsl's xsl:stylesheet tag, e.g. like this:
http://www.w3.org/1999/XSL/Transform" xmlns="http://
"
Regards
Mark
HI Experts,
After closely comparing i found one more thing. My service interface, Message mapping and Operation mapping resides under this namespace http://test.com, SWCV A and my external definition resides under this namespace http://Unilver.com/XI/ANSI_X12, SWCV B.
In my incoming payload i can see the namespace as http://test.com but in the message mapping default instance in the test tab namespace is http://Unilver.com/XI/ANSI_X12. Because of this reason mapping is failing not with the prefix.
1) Now why the incomoing payload not taking the External definition namespace instead it is taking Service interface namespace, but in the service interface i'm maintaining the external definition only with the namespace http://Unilver.com/XI/ANSI_X12.
2) If the point 1 is as per PI pipelines then i have to go to XSLT mapping or XMLAnnomizer bean to change the Service interface namespace to my external definition namespace .
Add comment