WebService - XI - WSDL with addtional XSD-files

Hi all,
i have a WSDL-File which contains only the operations of a webservice.
Then i have different XSD-Files which contains the structure of the data.
I can't find an external reference in the WSDL-file to the XSD files...
How do i have to configure my interfaces in XI? If i use the WSDL-file only one parameter is shown (reqeuest).
If i use the XSD-Files i can do the mapping... But I don't need the WSDL-file??!!
Any ideas?
regards

Hi Wolfgang,
There is a tag called xsd:location which relates the WSDL to external schema files .
If you are calling a web service, then you can directly use xsd to create your data types but in some cases operation name is also required which is present in WSDL.
Data Type is just an way to send the required data, but what operation you are calling from Web Service. A Web Service may contain various operations. So to distinguish, operation name is also required.
Try creating your message throough XML SPY and see the input message generated , whether it matches with your XSD format or not.
Regards,
Piyush

Similar Messages

Webservice from WSDL with imported XSD

Hi all,
Firstly, as a newbie to Jdeveloper forgive the ignorance....
I'm trying to create and deploy a webservice (created top-down).
I have an XSD, and a WSDL which imports this via a relative reference of the kind ../../ etc. - this validates OK in JDeveloper
When I try to deploy this to WL I get a file not found error for this XSD, it can't find the XSD in the packaged archive to be deployed.
So my question, for the import statement in my WSDL which is currently....
<xsd:import namespace="http://xml.netbeans.org/schema/LoanApplication" schemaLocation="../../../LoanApprover.xsd"/> (i.e. XSD directory relative to WSDL directory at design time)
...what do I need to change it to so that when packaged it can find the XSD ?
Thanks in advance
MarkF

Solved on JDeveloper forum.

XML Validation with multiple XSD files (referenced)

Hello,
I know that XML validation with version 7.1 is possible now. However I was provided with a set of XSD files that have references to each other and need to be placed in a hierachical file system order so that references can be resolved.
An element <xsl:include schemaLocation="../../baseSchemas/baseSchema.xsd" /> is used for example. How can I handle that for XSD validation in PI? Can I create the same folder structure or do I need to put all XSD files in one directory and change the import manually?
But most important question: Is it possible it all to use more than one XSD for schema validation?

Dear Florian,
I had encountered such case in a project.
I was given 3 files. One main file and 2 others called Schema1.xsd and Schema2.xsd.
This happens because your data type is not in single namespace, but is being referred across namespaces and software components.
I am assuming that you have read the How to Guide for XML validations on PI 7.1
Best way to do this quickly is as follows.
1. Enable XML validation at adapter engine in the sender agreement.
2. Post a message using HTTP post. (http://sappihttpclient.codeplex.com)
3. Check communication channel in runtime workbench. There will be an error saying which is missing at what path.
4. Create the path mentioned and place the file at that path.
5. Repeat steps 2,3,4 for all the files.
When you are done with this, you will get a proper validation error in case XML file is not correct. And remember to generate XSD from message type and not data type.
Regards,
Vikas
Edited by: Vikas Aggarwal on Sep 2, 2009 8:45 PM
Edited by: Vikas Aggarwal on Sep 2, 2009 8:48 PM

Validate a XML file with a XSD File in ABAP

Hi everybody,
I am searching a way for validating a XML File with an external XSD File in ABAP. I know to validate with dtd is possible, but what about XSD?
Can you help me in my urgend problem ?
Greetings from Germany
ismail er

anyone an idea for my issue ???

ORA-19046 with valid xsd-file (on 11.2.0.2)

Hello Experts,
I got an xml-file and had to import it into some relational tables. The xsd-files are given.
I tried: creating ressources for the xsd-files - works; register schema's -> not possible, because of ORA-19046.
In XMLSpy validating all xsd-files (a total of seven files) is possible - not error found.
Are there any ideas, how to import the data to some tables? (I don't really need the xml-file in the database)
Thanky for any help!
Frank

XSD-Upload - Part 1/7
There are seven files - I will post the ORIGINAL Files without oracle annotations:
vda_root_V1.2.xsd
-> vda_header_V1.2.xsd
-> vda_body_V1.2.xsd
-> ehd_root_V1.40.xsd
-> keytabs_V1.40.xsd
-> ehd_header_V1.40.xsd
-> datentypen_V1.40.xsd
My Probelm-baby ist datentypen_V1.40.xsd
<?xml version="1.0" encoding="ISO-8859-1"?>

<xs:schema xmlns="urn:ehd/001" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:ehd/001" elementFormDefault="qualified" attributeFormDefault="unqualified">
     
     <xs:element name="id" type="id_typ">
          <xs:annotation>
               <xs:documentation>enthält eindeutige Instanz-ID</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="id_typ">
          <xs:attribute name="EX" type="xs:string" use="optional"/>
          <xs:attribute name="RT" type="xs:string" use="required"/>
          <xs:attribute name="RTV" type="xs:string" use="optional"/>
     </xs:complexType>
     <xs:complexType name="doc_id_typ">
          <xs:annotation>
               <xs:documentation>ist dem id_typ identisch</xs:documentation>
          </xs:annotation>
          <xs:complexContent>
               <xs:extension base="id_typ"/>
          </xs:complexContent>
     </xs:complexType>
     <xs:element name="set_id" type="id_typ">
          <xs:annotation>
               <xs:documentation>enthält eindeutige Instanz-ID, die über alle Versionen und zusammgengehörende Dokumente konstant bleibt</xs:documentation>
          </xs:annotation>
     </xs:element>
     
     
     <xs:element name="version_nbr" type="version_nbr_typ">
          <xs:annotation>
               <xs:documentation>Versionnummer des XML-Dokuments</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="version_nbr_typ">
          <xs:attribute name="V" type="xs:nonNegativeInteger" use="required"/>
     </xs:complexType>
     
     <xs:element name="document_relationship" type="document_relationship_typ">
          <xs:annotation>
               <xs:documentation>Beziehung zu anderen Dokumenten ("Anhang", "Ersatz")</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="document_relationship_typ">
          <xs:sequence>
               <xs:element name="document_relationship.type_cd" type="document_relationship.type_cd_typ">
                    <xs:annotation>
                         <xs:documentation>Art der Dokumentbeziehung ("Anhang", "Ersatz")</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element ref="related_document"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="document_relationship.type_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.101"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:element name="related_document" type="related_document_typ">
          <xs:annotation>
               <xs:documentation>Verweis auf das Original/Anhang-Dokument</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="related_document_typ">
          <xs:sequence>
               <xs:element ref="id"/>
               <xs:element ref="set_id" minOccurs="0"/>
               <xs:element ref="version_nbr" minOccurs="0"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     
     <xs:element name="document_type_cd" type="document_type_cd_typ">
          <xs:annotation>
               <xs:documentation>Dokumenttype Code</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="document_type_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.100"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     
     
     <xs:element name="service_tmr" type="service_tmr_typ">
          <xs:annotation>
               <xs:documentation>Gültigkeitszeitraum (date..date)</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="service_tmr_typ">
          <xs:complexContent>
               <xs:extension base="v_zeitraum_typ"/>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:element name="origination_dttm" type="origination_dttm_typ">
          <xs:annotation>
               <xs:documentation>Erstellungsdatum</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="origination_dttm_typ">
          <xs:complexContent>
               <xs:extension base="v_date_typ"/>
          </xs:complexContent>
     </xs:complexType>
     
     
     <xs:element name="intended_recipient" type="intended_recipient_typ">
          <xs:annotation>
               <xs:documentation>Empfänger / Zielgruppe der Daten</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="intended_recipient_typ">
          <xs:sequence>
               <xs:element name="intended_recipient.type_cd" type="intended_recipient.type_cd_typ" minOccurs="0"/>
               <xs:element ref="function_cd" minOccurs="0"/>
               <xs:element ref="person" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="organization" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="intended_recipient.type_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.102"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:element name="originator" type="originator_typ">
          <xs:annotation>
               <xs:documentation>Ersteller, Urheber des Dokuments / der Daten</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="originator_typ">
          <xs:sequence>
               <xs:element name="originator.type_cd" type="originator.type_cd_typ" minOccurs="0"/>
               <xs:element ref="function_cd" minOccurs="0"/>
               <xs:element ref="participation_tmr" minOccurs="0"/>
               <xs:element ref="person" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="organization" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="originator.type_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.103"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:element name="provider" type="provider_typ">
          <xs:annotation>
               <xs:documentation>Sender, Lieferant des Dokuments (kann gleichzeitig der Urheber sein)</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="provider_typ">
          <xs:sequence>
               <xs:element name="provider.type_cd" type="provider.type_cd_typ" minOccurs="0"/>
               <xs:element ref="function_cd" minOccurs="0"/>
               <xs:element ref="participation_tmr" minOccurs="0"/>
               <xs:element ref="person" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="organization" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="provider.type_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.104"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     <xs:element name="function_cd" type="function_cd_typ">
          <xs:annotation>
               <xs:documentation>Funktion/Rolle der Person/Organisation</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="function_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.105"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     <xs:element name="participation_tmr" type="v_zeitraum_typ">
          <xs:annotation>
               <xs:documentation>Zeitraum/Zeitpunkt der Teilnahme</xs:documentation>
          </xs:annotation>
     </xs:element>
     
     <xs:element name="person" type="person_typ">
          <xs:annotation>
               <xs:documentation>Person-Daten</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:element name="group" type="group_typ">
          <xs:annotation>
               <xs:documentation>zugehörende Gruppe, Ausprägung (z.B. Augenarzt)</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="group_typ">
          <xs:complexContent>
               <xs:extension base="v_s_string_typ">
                    <xs:sequence>
                         <xs:element ref="group.type_cd"/>
                    </xs:sequence>
               </xs:extension>
          </xs:complexContent>
     </xs:complexType>
     <xs:element name="group.type_cd" type="v_s_string_typ">
          <xs:annotation>
               <xs:documentation>Gruppebezeichnung (z.B. Facharztagruppe)</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="person_typ">
          <xs:sequence>
               <xs:element ref="id" minOccurs="0"/>
               <xs:element ref="person_name" minOccurs="0"/>
               <xs:element name="organization.nm" type="v_string_typ" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="addr" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="telecom" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:element name="telecom" type="v_string_typ">
          <xs:annotation>
               <xs:documentation>Telekomunnikation (tel,mail,fax,...)</xs:documentation>
          </xs:annotation>
     </xs:element>
     
     <xs:element name="person_name" type="person_name_typ">
          <xs:annotation>
               <xs:documentation>Name der Person</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="person_name_typ">
          <xs:sequence>
               <xs:element name="nm" type="person_name_nm_typ"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="person_name_nm_typ">
          <xs:choice minOccurs="0" maxOccurs="unbounded">
               <xs:element name="GIV" type="pnxp_string_typ">
                    <xs:annotation>
                         <xs:documentation>Vorname</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="MID" type="pnxp_string_typ">
                    <xs:annotation>
                         <xs:documentation>Zusatzname</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="FAM" type="pnxp_string_typ">
                    <xs:annotation>
                         <xs:documentation>Nachname</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="PFX" type="pnxp_string_typ">
                    <xs:annotation>
                         <xs:documentation>Titel (Dr.)</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="SFX" type="pnxp_string_typ">
                    <xs:annotation>
                         <xs:documentation>Namenzusatz</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="DEL" type="pnxp_string_typ">
                    <xs:annotation>
                         <xs:documentation>Trennzeichen</xs:documentation>
                    </xs:annotation>
               </xs:element>
          </xs:choice>
     </xs:complexType>
     
     <xs:element name="organization" type="organization_typ">
          <xs:annotation>
               <xs:documentation>Organisations-Daten</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="organization_typ">
          <xs:sequence>
               <xs:element ref="id" minOccurs="0"/>
               <xs:element name="organization.nm" type="v_string_typ" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="addr" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="telecom" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     
     <xs:element name="addr" type="addr_typ">
          <xs:annotation>
               <xs:documentation>Adresse</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="addr_typ">
          <xs:choice minOccurs="0" maxOccurs="unbounded">
               <xs:element name="STR" type="v_string_typ"/>
               <xs:element name="HNR" type="v_string_typ"/>
               <xs:element name="POB" type="v_string_typ"/>
               <xs:element name="ZIP" type="v_string_typ"/>
               <xs:element name="CTY" type="v_string_typ"/>
               <xs:element name="STA" type="v_string_typ"/>
               <xs:element name="CNT" type="v_string_typ"/>
               <xs:element name="ADL" type="v_string_typ"/>
          </xs:choice>
     </xs:complexType>
     
     <xs:element name="patient" type="patient_typ">
          <xs:annotation>
               <xs:appinfo>Patient-Informationen</xs:appinfo>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="patient_typ">
          <xs:sequence>
               <xs:element name="patient.type_cd" type="v_s_string_typ" minOccurs="0"/>
               <xs:element ref="person"/>
               <xs:element name="birth_dttm" type="v_date_typ" minOccurs="0"/>
               <xs:element name="administrative_gender_cd" type="v_s_string_typ" minOccurs="0"/>
               <xs:element ref="local_header" minOccurs="0"/>
          </xs:sequence>
     </xs:complexType>
     
     <xs:element name="local_header" type="local_header-cont.model">
          <xs:annotation>
               <xs:documentation>Element für weitere, datenartspezifische, Metainformationen</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="local_header-cont.model" mixed="true">
          <xs:choice minOccurs="0" maxOccurs="unbounded">
               <xs:any processContents="skip" minOccurs="0" maxOccurs="unbounded"/>
          </xs:choice>
          <xs:attribute name="ignore" type="ignore_typ" default="markup"/>
          <xs:attribute name="descriptor" type="xs:string"/>
          <xs:attribute name="render" type="xs:string"/>
     </xs:complexType>
     
     
     <xs:complexType name="v_string_typ">
          <xs:attribute name="V" type="xs:string" use="required"/>
     </xs:complexType>
     
     <xs:element name="TRANSLTN" type="transltn_typ">
          <xs:annotation>
               <xs:documentation>interne/alternative Kodes und Schlüsseltabellen</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="transltn_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ"/>
          </xs:complexContent>
     </xs:complexType>
     <xs:complexType name="v_s_string_typ">
          <xs:attribute name="V" type="xs:string" use="required"/>
          <xs:attribute name="DN" type="xs:string" use="optional"/>
          <xs:attribute name="S" type="xs:string" use="optional"/>
          <xs:attribute name="SN" type="xs:string" use="optional"/>
          <xs:attribute name="SV" type="xs:string" use="optional"/>
     </xs:complexType>
     
     <xs:complexType name="v_date_typ">
          <xs:attribute name="V" type="xs:date" use="required"/>
     </xs:complexType>
     
     <xs:complexType name="v_zeitraum_typ">
          <xs:annotation>
               <xs:documentation>Zeitraum: datum..datum</xs:documentation>
          </xs:annotation>
          <xs:attribute name="V" type="zeitraum_typ" use="required"/>
     </xs:complexType>
     
     <xs:complexType name="pnxp_string_typ">
          <xs:attribute name="V" type="xs:string" use="required"/>
          <xs:attribute name="QUAL" type="xs:NMTOKENS" use="optional"/>
     </xs:complexType>
     
     
     
     
     
     <xs:element name="interface" type="interface_typ">
          <xs:annotation>
               <xs:documentation>enthält Informationen über die Schnittstelle selbst</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="interface_typ">
          <xs:sequence>
               <xs:element name="id" type="interface_id_typ"/>
               <xs:element name="interface.nm" type="interface_nm_typ"/>
               <xs:element name="version" type="interface_version_typ"/>
               <xs:element ref="originator" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element name="description" type="description_typ" minOccurs="0"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="interface_id_typ">
          <xs:complexContent>
               <xs:restriction base="id_typ">
                    <xs:attribute name="RT" type="xs:string" use="required" fixed="1.2.276.0.76.5.109"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:complexType name="interface_nm_typ">
          <xs:annotation>
               <xs:documentation>Bezeichnung der Schnittstelle</xs:documentation>
          </xs:annotation>
          <xs:complexContent>
               <xs:extension base="v_string_typ"/>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:complexType name="interface_version_typ">
          <xs:annotation>
               <xs:documentation>Version der Schnittstellenbeschreibung</xs:documentation>
          </xs:annotation>
          <xs:complexContent>
               <xs:extension base="v_string_typ"/>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:complexType name="description_typ">
          <xs:annotation>
               <xs:documentation>Kurzbeschreibung oder Link auf die WebSite mit der Schnittstellenbeschreibung</xs:documentation>
          </xs:annotation>
          <xs:attribute name="V" type="xs:string" use="required"/>
          <xs:attribute name="URL" type="xs:anyURI" use="optional"/>
     </xs:complexType>
     
     <xs:element name="scope" type="scope_typ">
          <xs:annotation>
               <xs:documentation>Geltungsbereich</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="scope_typ">
          <xs:sequence>
               <xs:element name="id" type="scope_id_typ" maxOccurs="unbounded"/>
               <xs:element name="scope.type_cd" type="scope.type_cd_typ">
                    <xs:annotation>
                         <xs:documentation>z.B. 1=KV-Geltungsbereich</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="scope.nm" type="v_string_typ" minOccurs="0" maxOccurs="unbounded">
                    <xs:annotation>
                         <xs:documentation>Name des Bereichs zu dem id-Element (z.B. KV-Nord)</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="scope_id_typ">
          <xs:complexContent>
               <xs:restriction base="id_typ">
                    <xs:attribute name="RT" type="xs:string" use="required" fixed="1.2.276.0.76.5.106"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     <xs:complexType name="scope.type_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.107"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:element name="state" type="state_typ">
          <xs:annotation>
               <xs:documentation>Bearbeitungszustand</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="state_typ">
          <xs:complexContent>
               <xs:extension base="v_s_string_typ"/>
          </xs:complexContent>
     </xs:complexType>
     
     
     
     <xs:simpleType name="null.code.set">
          <xs:annotation>
               <xs:documentation>Ausprägungen für NULL-Attribut</xs:documentation>
          </xs:annotation>
          <xs:restriction base="xs:string">
               <xs:enumeration value="NI"/>
               <xs:enumeration value="NA"/>
               <xs:enumeration value="UNK"/>
               <xs:enumeration value="NASK"/>
               <xs:enumeration value="ASKU"/>
               <xs:enumeration value="NAV"/>
               <xs:enumeration value="OTH"/>
               <xs:enumeration value="PINF"/>
               <xs:enumeration value="NINF"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="guid_typ">
          <xs:annotation>
               <xs:documentation>Typ für einen Global Unique Identifier</xs:documentation>
          </xs:annotation>
          <xs:restriction base="xs:string">
               <xs:pattern value="[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="zeitraum_typ">
          <xs:annotation>
               <xs:documentation>Zeitraum datum..datum</xs:documentation>
          </xs:annotation>
          <xs:restriction base="xs:string">
               <xs:pattern value="([1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1]))\.\.[1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1])))|([1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1])))|(\.\.[1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1])))|([1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1]))\.\.)"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="ignore_typ">
          <xs:restriction base="xs:string">
               <xs:enumeration value="all"/>
               <xs:enumeration value="markup"/>
          </xs:restriction>
     </xs:simpleType>
</xs:schema>

External Definition (wsdl) with abstract xsd element

Hello All,
we are trying to call a webservice, here is the wsdl:
https://www.1link.com/fr/demo-sn/site/gaiwebservice.asmx?WSDL
the problem is that the GAIJobLine element is defined as abstract:
<s:complexType name="GAIJobLine" abstract="true">
and there several elements which are extending GAIJobLine, for example:
<s:complexType name="GAITyreLine">
<s:complexContent mixed="false">
<s:extension base="tns:GAIJobLine">
So in our mapping we need to map to those element which are extending base element and not to the abstract one, but Graphical mapping displays only GAIJobLIne base element.
Does anybody know how we can map to extended elements without mannually changing wsdl?
Best Regards,
Artsiom Anichenka

thanks for your reply!
the extended elements are seen when I open wsdl in XMLSpy.
they are also visible in external definition object, but the main problem is that in the mapping only the base lement is displayed and there is no possobility to choose the extension.
Maybe this kind os XSDs (with abstract base types and extended elements) are just not supported by PI711?

NullPointerException received on creating webservice from wsdl with jdevel

Hello experts,
I have the following problem when trying to create a web service from a wsdl file:
java.lang.NullPointerException
     at oracle.jdevimpl.webservices.wizard.jaxrpc.common.SpecifyWsdlPanel.fetchWSDL(SpecifyWsdlPanel.java:1054)
     at oracle.jdevimpl.webservices.wizard.jaxrpc.common.SpecifyWsdlPanel$1.run(SpecifyWsdlPanel.java:364)
     at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:655)
     at java.lang.Thread.run(Thread.java:662)
I'm using Jdeveloper 11.1.2.2.0.
Any ideas?
Thanks in advance and best regards!
Edited by: Carolik on 23.10.2012 01:28

are you trying access web service(old) which is free of cost.
nowdays, most of the webservices(free of cost) they are re-locating the service to somewhere else
anyhow, some of the service had been stopped.
so please post which web service are you trying access(if it belongs to public).
if it is private web service dont post here

PI does not combine .wsdl file with .xsd files.

Hi,
I imported .wsdl file with necessary .xsd files in PI system (7.1).
PI does not find fields in .wsdl already necessary .xsd files imported with .wsdl file.
Is there anyone to help me to solve problem with test it in PI system.
I send .wsdl file and necessary .xsd files as attachment his mail address.
Thanks.

Did you try opening the wsdl file in some XML tool...if there is problem in referring the XSD then it will be visible in the tool itself.....even I am working on PI7.1 and some of the WSDLs are referring XSDs...and i had no problem in using them.....dont know what is failing in your case
Do you want me to send .wsdl and .xsd files zipped into your mail box
instead you can post your wsdl file and the corresponding XSD here in SDN....even a dummy structure would do....we are not allowed to do personal email comunication
Regards,
Abhishek.

Best practice for how to access a set of wsdl and xsd files

I've recently beeing poking around with the Oracle ESB, which requires a bunch of wsdl and xsd files from HOME/bpel/system/xmllib. What is the best practice for including these files in a BPEL project? It seems like a bad idea to copy all these files into every project that uses the ESB, especially if there are quite a few consumers of the bus. Is there a way I can reference this directory from the project so that the files can just stay in a common place for all the projects that use them?
Bret

Hi,
I created a project (JDeveloper) with local xsd-files and tried to delete and recreate them in the structure pane with references to a version on the application server. After reopening the project I deployed it successfully to the bpel server. The process is working fine, but in the structure pane there is no information about any of the xsds anymore and the payload in the variables there is an exception (problem building schema).
How does bpel know where to look for the xsd-files and how does the mapping still work?
This cannot be the way to do it correctly. Do I have a chance to rework an existing project or do I have to rebuild it from scratch in order to have all the references right?
Thanks for any clue.
Bette

Rules Problem with multiple XSD

Hi,
I've done a jdev project for SOA Suite 11g including only one Business Rules which could be call by a Webservice.
When I used 2 differents XSD to define 1 input fact and 1 output fact, the rule engine failed with an UNEXPECTED element Error
<fault>
<faultType>0</faultType>
<operationErroredFault>
<part name="payload">
<errorInfo>
<errorMessage>unexpected element (uri:"http://www.arvato.fr/formatPivot", local:"CUSTOMER"). Expected elements are <{http://www.arvato.fr/formatPivot}ADDRESS>,<{http://www.arvato.fr/formatPivot}DedoublonnageRule>,<{http://www.arvato.fr/formatPivot}StatusRule></errorMessage>
</errorInfo>
</part>
</operationErroredFault>
</fault>
When I use only one XSD file in my facts fou my input and outpout values. It runs Well.
Here are the facts definition with Multiple XSD FIle :
http://lh5.ggpht.com/_noQvj60LDl4/S4-J8DcFEkI/AAAAAAAAAKU/fAtlSMgFS_8/separatedSchemas.png
Here are the facts definition with Single XSD FIle :
http://lh6.ggpht.com/_noQvj60LDl4/S4-J78qnj0I/AAAAAAAAAKQ/U1JNnaJyK50/includedSchema.png
Could you please answer me how to use multiple xsd file in facts ?
Regards,
Jerome.

Hi,
Does anybody have any idea ?
Regards,
Jerome

Create XML File from a specified XSD file

Hi,
I'd like to create an XML document with java. BUT How can we "bind" this creation with a XSD file. Hence, the creation may fail if the XSD binded file is not respected.
So I know how to create XML file but not bind to this creation my proper XSD file (XML schema). With which tool can I do this ?
Thanks.

Hi,
I'd like to create an XML document with java. BUT How can we "bind" this creation with a XSD file. Hence, the creation may fail if the XSD binded file is not respected.
So I know how to create XML file but not bind to this creation my proper XSD file (XML schema). With which tool can I do this ?
Thanks.

PI 7.1: Importing a wsdl file with references to other xsd files

Hi Experts,
I am trying to import a wsdl file that has got references to other xsd files. When i do this with SOAP UI, i can get the full message structure for the other xsd files. But when i try to import the same wsdl in the ESR, i only get to the messages and not the referenced xsd.
Any ideas!
Thank you in Advance,
Danny

Hi,
First convert your main WSDL in to XSD,use Stylus or any XML editors to convert the same,thecn check the genarated XSD refering sun XSD tsrutures.then zip the all xsd in to one File and import in PI,then select you main xsd in the folder,and select root element.
Normally withour converting in to XSD only if you group al import it in to PI,it wil work.
or
if you have some good knowledge about XSD then convert WSDL in to XSD and remove referece tags and include XSD content of sub xsds in to main XSD,and validate that one,and imnprt one XSD.
Regards,
Raj

To Import XSD file along with WSDL file in ED

Dear All,
I am doing a scenario web service1 XIRFCweb service2. Web service1 sends request to XI and XI sends to RFC and RFC response to web service2 and web service2 response (acknowledge) back to XI and XI sends back to web service1.
My client (web service2) has given me the web service (WSDL) file along with XSD file.
In the wsdl file there are number of elements and complex types.
<xs:element name="GetCustomer">
     <xs:complexType>
          <xs:sequence>
               <xs:element name="authentication" type="xx:AuthInfo"/>
               <xs:element name="CompanyName" type=" xx:AuthInfo "/>
          </xs:sequence>
     </xs:complexType>
</xs:element>
The type (xx:AuthInfo and xx:AuthInfo) are defined in XSD file.
My questions are
1)     Do I have to import the XSD file in ED or not.
2)     How do I map this XSD
3)     As WS1, RFC and WS2 all are synchronous MT do I have to use BPM for it.
4)     Can some one help with any docs please..
Thanks in advance

Hi,
>>Do I have to import the XSD file in ED or not
If you are having the wSDL files then you can take the structure from there itself. Just import the wsdl files in IR. You can also use XSD.
>>How do I map this XSD
XSD are same as Message Types. So create a MM and choose your XSD.
>>As WS1, RFC and WS2 all are synchronous MT do I have to use BPM for it.
Yes you have to because you are taking the responce from RFC and going to give it to WS2.
BPM steps:
1) receive (open sync bridge)
2) transformation 1
3) send (snyc)
4)transformation 2
3) send (close sync bridge)
https://weblogs.sdn.sap.com/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
Regards
Suraj

Getting response object field value as null when importing xsd file in wsdl

I have created a java webservice using X-Fire 1.2.6 framework and deployed on Tomcat 6.0 server. The response of the service is a java object named LoginDetail.
Inorder to reuse the basic elements and types we have defined them in a separate Types.xsd file which have been imported in the WSDl file using xsd:import by giving the path to the xsd file.
Below you can see the portion of the wsdl file
     <wsdl:types>
          <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
               attributeFormDefault="qualified" elementFormDefault="qualified"
               targetNamespace="http://webservices.gtl.de/xsd">
               <xsd:import namespace="http://webservices.gtl.de/xsd"
                    schemaLocation="file:///D:/wsdl/LoginTypes.xsd"></xsd:import>
          </xsd:schema>
     </wsdl:types>
After deploying the application on Tomcat I could access the WSDL using a web browser and after that I could successfully generate webservice client code using using XFire wsgen ant build.
But when tried to call the service the fields of the response object(in my case it is LoginDetail object) returns null.
Follwing are the main class used for running the client and the output received as webservice respone.
Main class
public static void main(String[] args) {
CCLoginNewClient client = new CCLoginNewClient();
CCLoginNewPortType service     = client.getCCLoginNewHttpPort();
LoginDetail loginDetail = service.getLogin("CCLoginNew", "DE", "DE", "100", "0", "CC", "15","9344");
System.out.println("service got in response : "+loginDetail.getService());
Output
service got in response : null
is this the right way to import an xsd file in a wsdl file?
Any input would be appreciated!
Thanks in advance

PramodDas wrote:
Output
service got in response : nullCheck with Apache TCPMonitor what response you are receiving from web service.
is this the right way to import an xsd file in a wsdl file?Make sure that you really need import, not the include. However, I guess it has nothing do with the actual issue. It just to make sure that you are using right option.

Generate Proxy from WSDL with multiple Files

I need to load a WSDL (to generate a web service consumer proxy). However, that WSDL is build from multiple files, both .wsdl and .xsd, not a single one. It seems the SAP wizard to generate the proxy does expect one single WSDL file however.
Is there a way in SAP to load a WSDL with multiple files, or do I need to (manually) flatten all these files into one single file?

I am not sure why it fails in WebSphere. Please try posting
this question to a WebSphere newsgroup.
Regards,
-manoj
http://manojc.com
"viswanath" <[email protected]> wrote in message
news:40aee7fa$1@mktnews1...
>
thanks manoj for your reply.
I'm using IBM WebSphere SDK for Web Services v5.1
for generation of java client.
I'm able to generate the client but the problem is
the WSDl2Java command ignored the SOAPHeaders while
generating the proxy. Since I'm using SOAP headers for
authentication the code fails.
Thanks,
Viswanath
"manoj cheenath" <[email protected]> wrote:
I am not sure which tool you are using
to generate web service clent. To generate
a WLS web service client you have to use clientgen.
Details here:
http://e-docs.bea.com/wls/docs81/webserv/anttasks.html
Regards,
-manoj
http://manojc.com
"viswanath" <[email protected]> wrote in message
news:40ad8a07$[email protected]..
HI,
I have a web service (implemented in .NET) which extends soap headersfor
doing
Authentication. WSDL is generated out of this web service. But wheni use
wsdl2java
(J2EE) to generate a proxy class, there is no interface generated forsoap
headers.
Without extending SOAP headers the web service works fine.
Basically, I'm looking for a way to generate java interfaces (ie.
proxies)
for
SOAP headers out of the WSDL file.
PFA the WSDL file and the proxy
Any help on this is appreciated.

WebService - XI - WSDL with addtional XSD-files

Similar Messages

Maybe you are looking for