XSD Syndication Problem..

Hi All,
I want to transfer data from mdm through syndicator.
I created the follwing xsd file in xi.(message mapping)
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http:
mycompany.com\mdm" targetNamespace="http:
mycompany.com\mdm">
            <xsd:element name="MT_Customer" type="DT_Customer" />
            <xsd:complexType name="DT_Customer">
                        <xsd:annotation>
                                    <xsd:appinfo source="http://sap.com/xi/TextID">
                                    495dde70551e11db9e560011433286d8
                                    </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:sequence>
                                    <xsd:element name="Customer_Data">
                                                <xsd:annotation>
                                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                                            13886a30550b11dbcb99cf9a0abc902e
                                                            </xsd:appinfo>
                                                </xsd:annotation>
                                                <xsd:complexType>
                                                            <xsd:sequence>
                                                                        <xsd:element name="Customer" type="xsd:string">
                                                                                <xsd:annotation>
                                                                                <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                                13886a31550b11dba3f2cf9a0abc902e
                                                                                </xsd:appinfo>
                                                                                </xsd:annotation>
                                                                        </xsd:element>
                                                                        <xsd:element name="Title" type="xsd:string">
                                                                                <xsd:annotation>
                                                                                <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                                13886a32550b11dbcc76cf9a0abc902e
                                                                                </xsd:appinfo>
                                                                                </xsd:annotation>
                                                                        </xsd:element>
                                                                        <xsd:element name="Name1" type="xsd:string">
                                                                                <xsd:annotation>
                                                                                <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                                13886a33550b11db9c96cf9a0abc902e
                                                                                </xsd:appinfo>
                                                                                </xsd:annotation>
                                                                        </xsd:element>
                                                                        <xsd:element name="Name2" type="xsd:string">
                                                                                <xsd:annotation>
                                                                                <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                                13886a34550b11dbbbc7cf9a0abc902e
                                                                                </xsd:appinfo>
                                                                                </xsd:annotation>
                                                                        </xsd:element>
                                                                        <xsd:element name="Name3" type="xsd:string">
                                                                                <xsd:annotation>
                                                                                <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                                13886a35550b11db8470cf9a0abc902e
                                                                                </xsd:appinfo>
                                                                                </xsd:annotation>
                                                                        </xsd:element>
                                                                        <xsd:element name="Name4" type="xsd:string">
                                                                                <xsd:annotation>
                                                                                <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                                13886a36550b11dbb3bfcf9a0abc902e
                                                                                </xsd:appinfo>
                                                                                </xsd:annotation>
                                                                        </xsd:element>
                                                                        <xsd:element name="Searchterm1" type="xsd:string">
                                                                                <xsd:annotation>
                                                                                <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                                13886a37550b11dbae35cf9a0abc902e
                                                                                </xsd:appinfo>
                                                                                </xsd:annotation>
                                                                        </xsd:element>
                                                                        <xsd:element name="Searchterm2" type="xsd:string">
                                                                                <xsd:annotation>
                                                                                <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                                13886a38550b11dbb7c9cf9a0abc902e
                                                                                </xsd:appinfo>
                                                                                </xsd:annotation>
                                                                        </xsd:element>
                                                                        <xsd:element name="City_Post_Code" type="xsd:string">
                                                                                <xsd:annotation>
                                                                                <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                                13886a39550b11dba621cf9a0abc902e
                                                                                </xsd:appinfo>
                                                                                </xsd:annotation>
                                                                        </xsd:element>
                                                                        <xsd:element name="City" type="xsd:string">
                                                                                <xsd:annotation>
                                                                                <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                                13886a3a550b11db9287cf9a0abc902e
                                                                                </xsd:appinfo>
                                                                                </xsd:annotation>
                                                                        </xsd:element>
                                                                        <xsd:element name="Country" type="xsd:string">
                                                                                <xsd:annotation>
                                                                                <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                                13886a3b550b11dbb137cf9a0abc902e
                                                                                </xsd:appinfo>
                                                                                </xsd:annotation>
                                                                        </xsd:element>
                                                                        <xsd:element name="Region" type="xsd:string">
                                                                                <xsd:annotation>
                                                                                <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                                13886a3c550b11dbcc68cf9a0abc902e
                                                                                </xsd:appinfo>
                                                                                </xsd:annotation>
                                                                        </xsd:element>
                                                                        <xsd:element name="Noof_Employees" type="xsd:string">
                                                                                <xsd:annotation>
                                                                                <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                                13886a3d550b11db8a29cf9a0abc902e
                                                                                </xsd:appinfo>
                                                                                </xsd:annotation>
                                                                        </xsd:element>
                                                                        <xsd:element name="Annual_Sales" type="xsd:string">
                                                                                <xsd:annotation>
                                                                                <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                                13886a3e550b11dbbe2bcf9a0abc902e
                                                                                </xsd:appinfo>
                                                                                </xsd:annotation>
                                                                        </xsd:element>
                                                                        <xsd:element name="Currency_Of_Sales" type="xsd:string">
                                                                                <xsd:annotation>
                                                                                <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                                13886a3f550b11dbb901cf9a0abc902e
                                                                                </xsd:appinfo>
                                                                                </xsd:annotation>
                                                                        </xsd:element>
                                                                        <xsd:element name="Pobox" type="xsd:string">
                                                                                <xsd:annotation>
                                                                                <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                                13886a40550b11db97aecf9a0abc902e
                                                                                </xsd:appinfo>
                                                                                </xsd:annotation>
                                                                        </xsd:element>
                                                                        <xsd:element name="Language" type="xsd:string">
                                                                                <xsd:annotation>
                                                                                <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                                13886a41550b11dba4becf9a0abc902e
                                                                                </xsd:appinfo>
                                                                                </xsd:annotation>
                                                                        </xsd:element>
                                                                        <xsd:element name="Salesdata" type="xsd:string">
                                                                                <xsd:annotation>
                                                                                <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                                13886a42550b11dbae61cf9a0abc902e
                                                                                </xsd:appinfo>
                                                                                </xsd:annotation>
                                                                        </xsd:element>
                                                                        <xsd:element name="Bank_Details" type="xsd:string">
                                                                                <xsd:annotation>
                                                                                <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                                1f101890551e11dbc760cf9a0abc902e
                                                                                </xsd:appinfo>
                                                                                </xsd:annotation>
                                                                        </xsd:element>
                                                            </xsd:sequence>
                                                </xsd:complexType>
                                    </xsd:element>
                        </xsd:sequence>
            </xsd:complexType>
</xsd:schema>
And add xml shema entry in mdm console for the above schema.
When I try to set destination properties in syndicator...
I selected XMLSchema as type,client system,schema name. but,I am not able to select any <b>root</b> for it and I am not able to go proceed in syndication.
Is there any problem in the above xsd file ?
Please help me.

Hello Rama:
It happends because on your XSD you didn't define a data root tag:
<b><xsd:element name="dataroot">
</b>
I here paste an example of this. Please note how Office Access wrapped it all on the dataroot tag:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:od="urn:schemas-microsoft-com:officedata">
<xsd:element name="dataroot">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="SP1PERS" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="generated" type="xsd:dateTime"/>
</xsd:complexType>
</xsd:element>
<xsd:element name="SP1PERS">
<xsd:annotation>
<xsd:appinfo>
<od:index index-name="PrimaryKey" index-key="SPBPERS_PIDM " primary="yes" unique="yes" clustered="no"/>
<od:index index-name="STVNATN_CODE" index-key="STVNATN_CODE " primary="no" unique="no" clustered="no"/>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="SPBPERS_PIDM" minOccurs="0" od:jetType="text" od:sqlSType="nvarchar">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SP1PERS_HEIGHT_x0020_" minOccurs="0" od:jetType="text" od:sqlSType="nvarchar">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SP1PERS_FECHA_MATRIMONIO" minOccurs="0" od:jetType="text" od:sqlSType="nvarchar">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ST4TTRA_TITULO_TRATO" minOccurs="0" od:jetType="text" od:sqlSType="nvarchar">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STVNATN_CODE" minOccurs="0" od:jetType="text" od:sqlSType="nvarchar">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="GTVZIPC_CODE_LUGAR_NACIMIENTO" minOccurs="0" od:jetType="text" od:sqlSType="nvarchar">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="GTVZIPC_CODE_LUGAR_PROCEDENCIA" minOccurs="0" od:jetType="text" od:sqlSType="nvarchar">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SP1PERS_CURP" minOccurs="0" od:jetType="text" od:sqlSType="nvarchar">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SP1PERS_ACTIVITY_DATE" minOccurs="0" od:jetType="text" od:sqlSType="nvarchar">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SP1PERS_USER_x0020_" minOccurs="0" od:jetType="text" od:sqlSType="nvarchar">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Field11" minOccurs="0" od:jetType="text" od:sqlSType="nvarchar">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
I hope that helps
Regards
Alejandro

Similar Messages

  • XSD Resolution problem - Unable to load Translation schemas

    Hi,
    I've run into a very strange kind of problem (not to say some are less strange then others). Let me explain the context of the situation.
    I've got a BPEL process calling two plsql packages on ORA database, one Java web service running on the same weblogic server and couple of other services (eg. notification services, jdbc select/insert, etc.). There is no problem with the last listed, but definitely something wrong with the web service and the plsql callouts.
    When I deploy the BPEL process and execute it, the first two instances always fail. The same happens when I restart the server, the errors are repeated after a certain period as well (for example over night). The process always fails EXACTLY TWICE, before running normally. Every other instance executed after the two initial failures runs WITHOUT the following error.
    I mentioned there are two plsql callouts in the process, earlier the first instance failed on the second one and the second instance failed on the first. Now, it mostly fails on the second callout. I've made no significant changes in the code. Perhaps the strangest thing about this is that it fails when invoking the plsql package but the error concerns xsd definitions of the web service that plays no role at this stage.
    All my services are correctly deployed, I deleted all interface definitions from MDS repository and redeployed SOA bundle again before installing each service.
    I think it has something to do with generated xsd definitions by the java web service (it's the http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 and http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 from following stack trace), but I can't figure out what exactly is wrong with them.
    Anybody come accross a similar error? Thanks for tips, I've run out of ideas.      
    Error Message: {http://schemas.oracle.com/bpel/extension}bindingFault
    Fault ID     default/S50001KontrolaSouboruBS!1.0*soa_be986963-f9d9-412d-b692-43804a35b3ee/KontrolaSouboru/830023-BpInv18-BpSeq8.12-2
    Fault Time     14-Feb-2012 11:11:16
    Non Recoverable System Fault :
    <bpelFault><faultType>0</faultType><bindingFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'LogFile' failed due to: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "Could not instantiate InteractionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec due to: XSD Resolution problem. XSD Resolution problem. Unable to load Translation schemas from for http://xmlns.oracle.com/pcbpel/adapter/db/TST_IP/LOG_FILE/LOG_FILE/ due to: Different schema default values detected between: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 and oramds:/apps/LCRInterface/DataObjects/Common/V1/Common.xsd elementFormDefault values are differentDifferent schema default values detected between: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 and http://localhost:8001/soa-infra/services/default/S50035NotifikaceChybyBS/apps/LCRInterface/DataObjects/Common/V1/Common.xsd elementFormDefault values are differentDifferent schema default values detected between: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 and oramds:/apps/LCRInterface/DataObjects/Common/V1/DataTypes.xsd elementFormDefault values are differentDifferent schema default values detected between: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 and http://localhost:8001/soa-infra/services/default/S50035NotifikaceChybyBS/apps/LCRInterface/DataObjects/Common/V1/DataTypes.xsd elementFormDefault values are differentGlobal element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListByMaskRespDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 7] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 82] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:7] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:82] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 9] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 36] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:9] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:36] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}SaveFileDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 19] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 21] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:19] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:21] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListRespDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 11] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 51] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:11] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:51] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListByMaskDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 5] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 66] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:5] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:66] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetTextFileDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 13] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 112] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:13] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:112] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetTextFileRespDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 15] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 127] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:15] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:127] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}RenameFileDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 17] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 97] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:17] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:97] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListRespDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 115] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 52] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:117] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:54] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}RenameFileDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 175] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 98] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:177] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:100] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetTextFileRespDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 153] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 128] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:155] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:130] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListByMaskRespDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 64] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 83] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:66] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:85] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}SaveFileDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 93] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 22] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:95] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:24] Please make sure all used XML schemas are imported/included correctly. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary></part><part name="detail"><detail>Different schema default values detected between: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 and oramds:/apps/LCRInterface/DataObjects/Common/V1/Common.xsd elementFormDefault values are differentDifferent schema default values detected between: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 and http://localhost:8001/soa-infra/services/default/S50035NotifikaceChybyBS/apps/LCRInterface/DataObjects/Common/V1/Common.xsd elementFormDefault values are differentDifferent schema default values detected between: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 and oramds:/apps/LCRInterface/DataObjects/Common/V1/DataTypes.xsd elementFormDefault values are differentDifferent schema default values detected between: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 and http://localhost:8001/soa-infra/services/default/S50035NotifikaceChybyBS/apps/LCRInterface/DataObjects/Common/V1/DataTypes.xsd elementFormDefault values are differentGlobal element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListByMaskRespDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 7] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 82] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:7] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:82] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 9] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 36] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:9] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:36] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}SaveFileDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 19] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 21] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:19] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:21] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListRespDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 11] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 51] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:11] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:51] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListByMaskDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 5] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 66] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:5] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:66] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetTextFileDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 13] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 112] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:13] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:112] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetTextFileRespDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 15] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 127] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:15] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:127] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}RenameFileDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 17] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 97] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:17] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:97] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListRespDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 115] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 52] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:117] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:54] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}RenameFileDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 175] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 98] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:177] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:100] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetTextFileRespDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 153] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 128] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:155] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:130] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListByMaskRespDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 64] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 83] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:66] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:85] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}SaveFileDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 93] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 22] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:95] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:24] </detail></part><part name="code"><code>null</code></part></bindingFault></bpelFault>

    I had similar issue, when i deployed composite using Jdeveloper. The problem was with my adf-config.xml pointing to dev server and all my references in my composite.xml referring to test server.
    I changed property of 'oracle.mds.persistence.stores.db.DBMetadataStore' in adf-config.xml to test server. After adf-config.xml change in Jdev my compilation went smooth.
    Note: If above changes doesn't work, try restarting JDeveloper, sometimes the changes in adf-config.xml is not getting effect immediately.
    Regards,
    Ziaur Rahuman S
    Edited by: Ziaur Rahuman on Feb 13, 2013 10:58 PM

  • DB Adapter JCA-12563, XSD Resolution problem

    Hi,
    I am using Oracle SOA Suit, 11.1.1.4 and I am getting error in my db adapter.
    Below is the SOA adapter logs.
    This is intermittent issue, and occurs If i test the process for some time. After reeploying the service, same does not happen for some time but reoccurs after some good amount of testing.
    Can anybody help me with this issue?
    [2011-07-23T14:48:31.398+01:00] [managed1_metbsoa2] [ERROR] [] [oracle.soa.adapter] [tid: orabpel.engine.pool-5.thread-26] [userId: <anonymous>] [ecid: 16acbfc99351d211:2a7cdad1:13156bb951c:-8000-0000000000118eab,0:1:100392924] [APP: soa-infra] JCABinding=> NotificationService:DBA_GetConfigurationDetail [ DBA_GetConfigurationDetail_ptt::DBA_GetConfigurationDetailSelect(DBA_GetConfigurationDetailSelect_inputParameters,TConfigurationCollection) ] Could not invoke operation 'DBA_GetConfigurationDetailSelect' against the 'Database Adapter' due to: [[
    BINDING.JCA-12563
    Exception occured when binding was invoked.
    Exception occured during invocation of JCA binding: "Could not instantiate InteractionSpec oracle.tip.adapter.db.DBReadInteractionSpec due to: XSD Resolution problem.
    XSD Resolution problem.
    Unable to load Translation schemas from for http://xmlns.oracle.com/pcbpel/adapter/db/top/DBA_GetConfigurationDetail due to:
    Please make sure all used XML schemas are imported/included correctly.
    The invoked JCA adapter raised a resource exception.
    Please examine the above error message carefully to determine a resolution.

    I am also observing the similar issue , when db adapter is called getting the error
    Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'ObjectVersionNumber' failed due to: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "Could not instantiate InteractionSpec oracle.tip.adapter.db.DBPureSQLInteractionSpec due to: XSD Resolution problem. XSD Resolution problem. Unable to load Translation schemas from for http://xmlns.oracle.com/pcbpel/adapter/db/ObjectVersionNumber due to: Global element declaration/definition of name '{http://xmlns.oracle.com/apps/cac/soaprovider/plsql/jtf_tasks_pub/create_task/}InputParameters' are duplicated at the following locations: oramds:/apps/crm/services/IntegratedSoaGateway/APPS_ISG_CREATE_TASK_JTF_TASKS_PUB-24CREATE_TASK.xsd [line#: 3] http://civiceb.mfltest.co.uk/webservices/SOAProvider/plsql/jtf_tasks_pub/APPS_ISG_CREATE_TASK_JTF_TASKS_PUB-24CREATE_TASK.xsd [line#: 1] There are at least two of them looking different: oramds:/apps/crm/services/IntegratedSoaGateway/APPS_ISG_CREATE_TASK_JTF_TASKS_PUB-24CREATE_TASK.xsd [difference starting at line#:79] http://civiceb.mfltest.co.uk/webservices/SOAProvider/plsql/jtf_tasks_pub/APPS_ISG_CREATE_TASK_JTF_TASKS_PUB-24CREATE_TASK.xsd [difference starting at line#:1] Please make sure all used XML schemas are imported/included correctly. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
    There is a retry logic in a composite and after 2 or 3 retries this error does not comes, Its an intermittent issue.
    Is anyone able to find the resolution for this issue?.

  • OpenTrans 2.1 .xsd import problem into PI 7.1

    Hello,
    While trying to import the latest version 2.1 of openTrans .xsd Files (I downloaded "openTRANS_2.1_german_all-in-one_package.zip") into PI 7.1 we fail. Error message while loading the file "opentrans_2_1.xsd" is:
    Unable to convert imported document to WSDL
    Reason:
    Unable to recognize document as valid XSDCheck selected category
    OpenTrans 1.0 we have already in use since several time, however there is a need for the latest version now.
    Has anybody managed to get openTrans 2.1 to work with PI 7.1? And if so - how?
    Thanks!
    Andreas

    Hello Andreas
    This error can occur if there is an element tag with the name XML, e.g.: <xsd:element name="xml">.  If the element name is something other than xml, e.g. <xsd:element name="test">, then the import should be ok.
    SAP does not allow the element name in an XSD to start with the prefix -   xml                                                                               
    This conforms to the xml schema standards set by W3C  i.e.  http://www.w3schools.com/xml/xml_elements.asp
    -> XML Naming Rules section.
    Also, check note #1255351 External Defintion - XSD Checks Problem
    Regards
    Mark

  • XSD Location Problem.

    Hi Gurus,
    After starting the node in a cluster environemnt, often receiving "Unable to load Translation schemas from for http://xmlns.oracle.com/BRM/schemas/BusinessOpcodes due to: XSD Location problem.
    XSD Loading problem."
    This is mainly observed in BRM schemas, has anyone exprienced this? what shall be the workaround/solution other than restarting the container/application?
    We are using SOA 10.1.3.4 MLR 8 and Oracle AIA 2.4.
    Please help.

    The BRM schemas are present in the AIA Components which will be referred by the load balancer url in a clustered environment. However, if in any of the nodes, the url for AIA Components has the local node url instead of load balancer url, this issue occurs.
    Identify the node which is giving the issue (shutting down one node at a time and retrying the operation which gives the error). In the node which has the issue, try doing a search on AIA components to find out if there is any reference using local node url instead of load balancer.
    If you find any, replace with the load balancer url. I had faced a similar issue and I was able to resolve it as I have mentioned above.
    Cheers,
    - AR

  • XSD Loading problem

    I got this error from bpel console .. Can any one please update on this.. Why this this error should occur?.
    <messages><input><InvokePlanningOrderRoadshowProducerInputVariable><part name="PlanningOrderRequest" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><PlanningOrderRequest xmlns:ns0="http://xmlns.hdnl.com/EnterpriseObject/Core/PlanningOrder" xmlns="http://xmlns.hdnl.com/EnterpriseObject/Core/PlanningOrder">
    <ns0:PlanningOrderHeader>
    <ns0:OrderId>10215568</ns0:OrderId>
    <ns0:BookingId/>
    <ns0:OrderType>Standard</ns0:OrderType>
    <ns0:CustomerName>MRS JUNE OCKWELL</ns0:CustomerName>
    <ns0:ClientAccountId>EMP</ns0:ClientAccountId>
    <ns0:ClientPreAdviceNumber/>
    <ns0:Title/>
    <ns0:ClientOrderNumber>W3221000-36</ns0:ClientOrderNumber>
    <ns0:Latitude>53.526969</ns0:Latitude>
    <ns0:Longitude>-2.657221</ns0:Longitude>
    <ns0:Street/>
    <ns0:HouseNumber>8 Bentinck Street</ns0:HouseNumber>
    <ns0:Postcode>WN3 6RB</ns0:Postcode>
    <ns0:Town>WIGAN</ns0:Town>
    <ns0:Status/>
    <ns0:PhoneCallRequired>Y</ns0:PhoneCallRequired>
    <ns0:Phone1>01942202596</ns0:Phone1>
    <ns0:Phone2>07584651731</ns0:Phone2>
    <ns0:SlotPeriodStart/>
    <ns0:SlotPeriodEnd/>
    <ns0:SlotLength/>
    <ns0:StopDuration/>
    <ns0:PlanningOrderLines>
    <ns0:PlanningOrderLine>
    <ns0:OrderLineId>443405</ns0:OrderLineId>
    <ns0:OrderId>10215568</ns0:OrderId>
    <ns0:ItemNumber>EMP-TC750</ns0:ItemNumber>
    <ns0:ItemDescription>RICHMOND KING BED</ns0:ItemDescription>
    <ns0:NoOfPieces>03</ns0:NoOfPieces>
    <ns0:ServiceString>01000</ns0:ServiceString>
    <ns0:ShipsetId>01</ns0:ShipsetId>
    <ns0:ClientUPI>009707300553D094</ns0:ClientUPI>
    <ns0:OrderLineType>Delivery</ns0:OrderLineType>
    <ns0:OrderLineNumber>01</ns0:OrderLineNumber>
    <ns0:SpecialInstruction>IF NOT IN GO TO NUMBER 6 FOR KEY</ns0:SpecialInstruction>
    <ns0:DeliveryVolume/>
    <ns0:DeliveryWeight/>
    <ns0:CollectionWeight/>
    <ns0:CollectionVolume/>
    <ns0:Status>LOADED</ns0:Status>
    </ns0:PlanningOrderLine>
    </ns0:PlanningOrderLines>
    </ns0:PlanningOrderHeader>
    </PlanningOrderRequest>
    </part></InvokePlanningOrderRoadshowProducerInputVariable></input><fault><bindingFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>file:/SOA2M01/app/oracle/product/10.1.3/bpel/domains/operations/tmp/.bpel_PlanningOrder_1.0_06bcbd311b9a0d44d808edcbcee42770.tmp/PlanningOrderRoadShowProducer.wsdl [ Produce_Message_ptt::Produce_Message(PlanningOrderRequest) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Could not instantiate InteractionSpec oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec due to: XSD Loading problem.
    Unable to load Translation schemas from for http://xmlns.hdnl.com/EnterpriseObject/Core/PlanningOrder due to: XSD Location problem.
    No XSD (XML Schema) found for target namespace http://xmlns.hdnl.com/EnterpriseObject/Core/PlanningOrder and input element PlanningOrderRequest
    Please make sure the WSDL message points to a valid type.
    Please make sure all used XML schemas are imported/included correctly.
    ; nested exception is:
    ORABPEL-12537
    XSD Loading problem.
    Unable to load Translation schemas from for http://xmlns.hdnl.com/EnterpriseObject/Core/PlanningOrder due to: XSD Location problem.
    No XSD (XML Schema) found for target namespace http://xmlns.hdnl.com/EnterpriseObject/Core/PlanningOrder and input element PlanningOrderRequest
    Please make sure the WSDL message points to a valid type.
    Please make sure all used XML schemas are imported/included correctly.
    ; nested exception is:
    org.collaxa.thirdparty.apache.wsif.WSIFException: Could not instantiate InteractionSpec oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec due to: XSD Loading problem.
    Unable to load Translation schemas from for http://xmlns.hdnl.com/EnterpriseObject/Core/PlanningOrder due to: XSD Location problem.
    No XSD (XML Schema) found for target namespace http://xmlns.hdnl.com/EnterpriseObject/Core/PlanningOrder and input element PlanningOrderRequest
    Please make sure the WSDL message points to a valid type.
    Please make sure all used XML schemas are imported/included correctly.
    ; nested exception is:
    ORABPEL-12537
    XSD Loading problem.
    Unable to load Translation schemas from for http://xmlns.hdnl.com/EnterpriseObject/Core/PlanningOrder due to: XSD Location problem.
    No XSD (XML Schema) found for target namespace http://xmlns.hdnl.com/EnterpriseObject/Core/PlanningOrder and input element PlanningOrderRequest
    Please make sure the WSDL message points to a valid type.
    Please make sure all used XML schemas are imported/included correctly.
    </summary>
    </part><part name="detail"><detail>org.collaxa.thirdparty.apache.wsif.WSIFException: Could not instantiate InteractionSpec oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec due to: XSD Loading problem.
    Unable to load Translation schemas from for http://xmlns.hdnl.com/EnterpriseObject/Core/PlanningOrder due to: XSD Location problem.
    No XSD (XML Schema) found for target namespace http://xmlns.hdnl.com/EnterpriseObject/Core/PlanningOrder and input element PlanningOrderRequest
    Please make sure the WSDL message points to a valid type.
    Please make sure all used XML schemas are imported/included correctly.
    ; nested exception is:
    ORABPEL-12537
    XSD Loading problem.
    Unable to load Translation schemas from for http://xmlns.hdnl.com/EnterpriseObject/Core/PlanningOrder due to: XSD Location problem.
    No XSD (XML Schema) found for target namespace http://xmlns.hdnl.com/EnterpriseObject/Core/PlanningOrder and input element PlanningOrderRequest
    Please make sure the WSDL message points to a valid type.
    Please make sure all used XML schemas are imported/included correctly.
    </detail>
    </part></bindingFault></fault></messages>

    You remove xmlns:ns0 attribute from PlanningOrderRequest and the prefix ns0: from xsd tags. When you declare xmlns:ns0 means it is looking for that ns0 namespace in the project directory or oracle server global directory.

  • JAXB,xsd,xml problems

    Hello all!
    I am using JAXB to create xsd files and xml(by marshalling) from my Java beans.
    My problems is a bit complicated to explain so I'll do my best.
    My beans look like this:
    @XmlRootElement(name = "MerchantDetailsRequest")
    @XmlType(name = "MerchantDetailsRequest")
    public class MerchantDetailsRequest {
        private String merchantName;
        private Long merchantNumber;
        private Long merchantIdentifier;
        private Long status;
        private Long citySymbol;
        @XmlElement(required = false)
        public String getMerchantName() {
            return merchantName;
    // More getters and setters, equals & hashcode
    }The xsd schema I create looks like this:
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <xs:schema version="1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema">
      <xs:element name="MerchantDetailsRequest" type="MerchantDetailsRequest"/>
      <xs:element name="MerchantDetailsResponse" type="MerchantDetailsResponse"/>
      <xs:complexType name="MerchantDetailsRequest">
        <xs:sequence>
          <xs:element name="citySymbol" type="xs:long" minOccurs="0"/>
          <xs:element name="merchantIdentifier" type="xs:long" minOccurs="0"/>
          <xs:element name="merchantName" type="xs:string" minOccurs="0"/>
          <xs:element name="merchantNumber" type="xs:long" minOccurs="0"/>
        </xs:sequence>
      </xs:complexType>
      <xs:complexType name="MerchantDetailsResponse">
        <xs:sequence>
          <xs:element name="address" type="xs:string"/>
          <xs:element name="openDate" type="xs:dateTime"/>
        </xs:sequence>
      </xs:complexType>
    </xs:schema>Pay attention to the:
    <xs:element name="MerchantDetailsResponse" type="MerchantDetailsResponse"/>appearing twice(once for each element), these are required by our 3rd party(some other guys).
    The xml that is created by marshalling looks like this:
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <MerchantDetailsRequest>
        <citySymbol>4</citySymbol>
        <merchantIdentifier>9090</merchantIdentifier>
        <merchantName>Marco Van Basten</merchantName>
        <merchantNumber>9</merchantNumber>
    </MerchantDetailsRequest>
    Now, here comes the problem:
    I got a request (from the 3rd party guys) to add a namespace to the XML file.
    So I found out, that if I add the 'namespace="<some namespace>" ' attribute to my XmlRootElement annotation (e.g- @XmlRootElement(name = "MerchantDetailsRequest",namespace = "http://www.myaddress.com/myPath/merchant-details")
    ), then I get the wanted xml:
    <ns2:MerchantDetailsRequest xmlns:ns2="http://www.isracard.co.il/cheques/merchant-details">
        <citySymbol>4</citySymbol>
        <merchantIdentifier>9090</merchantIdentifier>
        <merchantName>Marco Van Basten</merchantName>
        <merchantNumber>9</merchantNumber>
    </ns2:MerchantDetailsRequest>
    BUT, my xsd is now missing the 'element' required fields I discussed earlier. (instead they appear in another xsd file, only the element def)
    SO, I read somewhere, that if I create a package-info.java file, with the annotations:
    @XmlSchema(namespace="http://www.mySite.com/myPath/MerchantDetailsRequest",elementFormDefault= XmlNsForm.UNQUALIFIED)
    that it will take care of this. but instead, when compiling, I get noxsd file at all!!!
    I need a simple solution to a simple problem... adding a namespace to my outgoing xml files without changing the sxd's.
    If ayone can help, it will be much appreciated!!
    Thanks,
    Dave
    Message was edited by:
    Just_Dave

    I'm sorry!! but after talking with the 3rd party guys, I understood, that everythingis ok!
    What I asked here is not a problem at all.
    I have another problem(simple this time...) but it will get a thread of it's oun.

  • XSD Changes - Problem Exception - creating schema

    I am having a problem and need your help. New to SOA.
    I have a xsd file in my project. Based on the xsd definition in the file I have created a BPEL variable (using element) refering to the xsd element name. Added a simplae assign statement and I could see the child elements fine during the Assign statement.
    However when I add new child element in the xsd file or even change the name of the pre-existing child element name the variable in the assign activity gives the error "Problem Exception - creating schema". I created a completely new variable by refering the xsd element but still the new variable also gives error "Problem Exception - creating schema".
    It appears that it does not like me changing the xsd file at all. Am I missing any step. Do I need to take any more step after changing the xsd to be able to create a new variable based on the xsd file.
    Please help.
    Thanks

    I looked it from the variable definition by clicking on "Exeception - Problem Building Schema" and it showing more details. The error is "Duplicated definition for : VariableFetchPOData"
    Where can I see the duplicated definition information. ?
    Please advise
    Thanks

  • CLFMAS syndication problem

    Hello ,
    I need to syndicate MDM CLFMAS data to SAP.
    Can I use XSD of  CLFMAS.CLFMAS02 IDOC of ECC.
    How is the CLFMAS data is enterd in main material table in mdm. Is it that CLFMAS data is stored as attribute in mdm.
    If I keep CLFMAS data as a field in main table can I use
    XSD of CLFMAS.CLFMAS02.
    as per mdm team , they cannnot give me syndicated data in CLFMAS.CLFMAS02. MDM person wants to change the xsd of standard idoc and repeat the segment E1AUSPM. Means if
    todays mdm has to send 200 CLFMAS records , person is going to copy segment E1AUSPM in xsd and that XSD will be used while defining syndication map.
    Pl suggest at the earliest possible.
    thanks,
    Sharada

    Hi Sharada,
    Yes CLFMAS02 can be used to syndicate classification data. Follow below steps:
    1] For <OBKEY> which is a material number use <RemoteKey Value>.
    2] You need to have a field in main table looking upto a taxonomy table which actually stores all classification data. (Class/Subclass hierarchy , attributes and values).
    3] Once you have this field , syndicator will start showing up a field "Attrubute Name and Values" with two childrens "Attribute Name" and "Attribute Value" in source pane.
    4] Map this parent node to <E1AUSPM> node of CLFMAS.
    5] Map "Attribute Name" to <ATNAM> node of CLFMAS and "Attribute Value" to <ATWRT> node of CLFMAS.
    6] This would map all the required fields for Classification.
    Regards,
    Amol.

  • Workflow - syndication problem

    Dear All
    We have the workflow with syndication step. All has been working fine, but sudenly today syndication is not working. There is only an information in log: "The system cannot locate the resource specified. Error processing resource "
    What does it mean ?
    Manual syndication works fine, but it is not working with workflow.
    Thank you for help.
    BR
    Rafal

    Hello,
    was the server restarted recently.
    What entries do we have in the workflow log, also are check if the port associated with the syndication server is open for communication
    Regards,
    Abhishek
    Edited by: Abhishek Biwal on Dec 14, 2011 5:10 PM

  • XSD compilation problem

    Hi good afternoon..
    here i am compiling one XSD file but when i am doing..i facing following error..
    after this error ...
    I have already set the all the PATH, CLASSPATH..
    E:\XMLprog>scomp -out purchaseorder.jar purchaseorder.xsd
    Time to build schema type system: 0.705 seconds
    Time to generate code: 0.157 seconds
    java.io.IOException: Cannot run program "E:\XMLprog\javac": CreateProcess error=2, The system cannot find the file specified
    java.io.IOException: CreateProcess error=2, The system cannot find the file specified
    java.io.IOException: Cannot run program "E:\XMLprog\javac": CreateProcess error=2, The system cannot find the file specified
    at java.lang.ProcessBuilder.start(Unknown Source)
    at java.lang.Runtime.exec(Unknown Source)
    at java.lang.Runtime.exec(Unknown Source)
    at org.apache.xmlbeans.impl.tool.CodeGenUtil.externalCompile(CodeGenUtil.java:231)
    at org.apache.xmlbeans.impl.tool.SchemaCompiler.compile(SchemaCompiler.java:1126)
    at org.apache.xmlbeans.impl.tool.SchemaCompiler.main(SchemaCompiler.java:368)
    Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified
    at java.lang.ProcessImpl.create(Native Method)
    at java.lang.ProcessImpl.<init>(Unknown Source)
    at java.lang.ProcessImpl.start(Unknown Source)
    ... 6 more
    BUILD FAILED

    As it is showing error like:
    The system cannot find the file specifiedCheck for the following:
    1) purchaseorder.xsd is in the directory E:\XMLprog
    2) If purchaseorder.xsd includes any other .xsd files,
        all included files should also be at
            same directory E:\XMLprog
            or at the location specified in schemaLocation attribute in purchaseorder.xsd
    Thanks,
    Tejas

  • XSD elements problem

    Hi Guru's,
    I am working with SAP PI 7.0 and when I upload an XSD to PI I can see the following structure:
         <xs:element name="fields">
              <xs:complexType>
                   <xs:attribute name="Field1" type="xs:string" use="required"/>
                   <xs:attribute name="Field2" type="xs:string" use="required"/>
                   <xs:attribute name="Field3" type="xs:string"/>
              </xs:complexType>
         </xs:element>
    When I look in the message mapping in the repository I see that field 2 and field 3 has changed position, so in message mapping it's via the following sequence:
    <xs:attribute name="Field1" type="xs:string" use="required"/>
    <xs:attribute name="Field3" type="xs:string"/>
    <xs:attribute name="Field2" type="xs:string" use="required"/>
    How can this be?
    Best regards,
    Guido Koopmann

    I discussed this with a developer from SAP some times ago.
    When the XSD does not have a "sequence" tag, PI picks up the elements and attributes randomly.
    In principle an XML parser should not make a difference, in which order the attributes come.
    To avoid this behaviour, you have to add a sequence node:
    <xsd:complexType>
                   <xsd:sequence>
                      <xs:attribute name="Field1" type="xs:string" use="required"/>
                      <xs:attribute name="Field2" type="xs:string" use="required"/>
                      <xs:attribute name="Field3" type="xs:string"/>
                   </xsd:sequence>
                </xsd:complexType>

  • XSD validation problem?l

    Hi all,
    I have an XSD as follows ,which I am going to use to develop a Webservice.
    But in XMLSpy it gives the error "'factorsType' must refer to an existing simple or complex type.” , but I have seen Schema definition like this on the tutorials so what am I doing wrong here ?
    {code}
    <xs:schema ...>
    <xs:complexType name="inputType">
    <xs:sequence>
         <xs:element name="factors" type="factorsType"/>
         <xs:element name="traindata" type="trainDataType" />
         <xs:element name="testdata" type="trainDataType"/>                    
    </xs:sequence>     
    </xs:complexType>
    <xs:complexType name="factorsType">
    </xs:complexType>
    <xs:complexType name="trainDataType">
    </xs:complexType>
    <xs:schema>
    {code}

    Has the schema got a namespace?
    <xs:complexType name="factorsType">will be in the namespace of the schema, but the reference you've given (type="factorsType") doesn't have a namespace given.
    It's a bit of a guess, but that looks like it might be the case.

  • Syndication Problem

    Hi All,
    We are working on MDM 5.5 sp05.
    We had imported the material data from R/3 and trying to syndicate it.
    In syndicated XML file, all elements are not getting filled as per the records in MDM. We are using the standard maps for Material repository.
    Regards,
    NIkhil

    Hi Anita,
    When we apply standard mapping for syndication, those which mapped to the remote key of source are not filled in the XML.
    but we are using standard maps. but if we unmapped the current one and assign to the code, it will work.is this is the correct way
    Eg: in lookup table Material type, there are fields like name, code, Application.
    So in standard map, the map is b/w the remote key of the source and the field in destination.
    suppose we unmap this and map it to code, it will work.
    is it the right way.......we are using  standard map....
    Regards,
    Nikhil

  • Jaxb xsd:any problem

    I am not sure how to set the namespace (please see schema snippet below). Do I do this with setAny(java.lang.Object)? What kind of object do I pass to setAny() because it is trying to class cast it to JAXBObject. How do I create an instance of JAXBObject?
    I have in my xsd:
    <xsd:element name="order">
              <xsd:complexType>
                   <xsd:sequence>
                        <xsd:any namespace="urn:abc.com" minOccurs="0" maxOccurs="1"/>
                        <xsd:element ref="a"/>
                        <xsd:element ref="b"/>
                   </xsd:sequence>
                   <xsd:attribute name="locale" type="xsd:string" use="optional"/>
                   <xsd:attribute name="sourceid" type="xsd:string" use="optional"/>
              </xsd:complexType>
         </xsd:element>

    Refer to section
    E.2 Not Required XML Schema
    concepts
    "A JAXB implementation is not required to support the following XML Schema
    concepts for this version of the specification. A JAXB implementation may
    choose to support these features in an implementation dependent manner."
    E.2.2 Not supported while manipulating the XML
    content
    Schema component: wildcard
    (any)
    how can i know if an xml element with xsi:nil="true" (unmarshal)
    and set xsi:nil="true" for an element (marshal) ?
    According to the JAXB 1.0 specification:
    If {nillable} is "true", the methods setNil() and isNil() are
    generated.

Maybe you are looking for

  • Reg calling Transaction code in Webdynpro ABAP

    Hi All, Can I call Transaction code in Webdynpro ABAP Portal Application. If so, how can this be possible? Can anybody give me a lead? Thanks. Kumar Saurav.

  • Third Party DVD Player for MacIntel (not VLC)?

    The only software I miss from my Windoze days is PowerDVD. It had many features like step-backward, multiple FF and REW speeds that were keyboard shortcut accessible (vs. Apple DVD player where you set one speed and that's it), screen capture, and it

  • Import language (SMLT) after EHP 03

    Hello, we started with a few languages in ECC 600 directly imported after installation. But now we have to install another 2 languages. But meanwhile we have "upgraded" the system to 603 via EHP... If I start the SMLT import a package is found, but t

  • RAM NOT GIVING PERFORMANCE BOOST?

    I had 1gb of Ram in my Pc, and it was slow. I bought 2x 1gb ram and now have 2gb ram, and it is slower than before, why is this? is the Ram faulty? maybe too much use from used product?

  • Win-ca and ipad integration for vpn

    Hi Guys, I m trying to configure certificate based vpn for our office . we have ipad ,windows  2k3 standalone ca with scep componet installed on it . I am using iphone confiration utility(icu) for configure ipad . Ipad using corprate wifi to enroll t