Problem Import WSDL with XSD import Schema

Hi SCN, i have problem
I have a WSDL that references an xsd, but the structure is not visible in PI.
   <wsdl:types>
      <xsd:schema targetNamespace="http://tempuri.org/Imports">
         <xsd:import schemaLocation="http://bilbolab****.net/ServiceItemHO.svc?xsd=xsd0" namespace="http://tempuri.org/" />
         <xsd:import schemaLocation="http://bilbolab.****.net/ServiceItemHO.svc?xsd=xsd1" namespace="http://schemas.microsoft.com/2003/10/Serialization/" />
         <xsd:import schemaLocation="http://bilbolab.*****.net/ServiceItemHO.svc?xsd=xsd2" namespace="http://schemas.datacontract.org/2004/07/ItemHO.BO" />
      </xsd:schema>
   </wsdl:types>
   <wsdl:message name="iVistaHO_AddItemHO_InputMessage">
      <wsdl:part name="parameters" element="tns:AddItemHO" />
   </wsdl:message>
WSDL works well using SoapUI.
When imported to PI parameters is not displayed
I Need Help
Thank you.

Hi, Dihiansan. I don't understand your proposal
I need you see the structure in PI how in SoapUI.
It is possible?
Regards

Similar Messages

Import WSDL with xsd:long incorrectly results in INT4

When importing a WSDL, all fields marked as xsd:long result in INT4 in the proxy class. But long is [supposed to be|http://www.w3schools.com/schema/schema_dtypes_numeric.asp] 8-byte (64 bit). We thus get the following error:
SOAP:1.001 CX_SY_CONVERSION_OVERFLOW:XSLT exception.
An error occurred when deserializing in the simple transformation program
/1SAI/TXS291D096A2B8E35E8375E.
Overflow converting from '2147483648'
<xsd:element minOccurs="0" name="Available" type="xsd:long"/>

Hello Marc
The only way is to manually edit the WSDL file and replace xsd:long
with xsd:string with pattern="\d+" and length="<n>"or
xsd:decimal with fractionDigits="0" totalDigigs="<n>"
Afterwarts regenerate proxy and you'll see that the
technical ABAP-Type is changed to STRG/DEC.
addtional info:
We recomment to use
xsd:decimal with totalDigits="19"
fractionDigits="0"
This is the shortest DEC that is big enought to accept the largest
xsd:long.
Future sight:
In release SAP_BASIS 702 this workaround is already fixed,
here you can change the technical type for xsd:long in proxy
editor directly to STRG or DEC(0,19) without modify the WSDL.
Thanks
Kenny

Importing WSDLs with references to schema

Hi all,
I am trying to invoke a webservice from PI and have imported the WSDLs for the same. But i couldn't see the various data types.
When i noticed that wsdl, i could see that there are rexternal references with relative path.
schemaLocation="..\External\external-common.xsd"/>
So i have a doubt about how to bring these references to PI. Since these are relative path, do i need to change them to absolute path?
If yes, how?
Thanks and best regards,
Kulwant

Hi Kulwant,
The schema files should always be present at the relative paths.
You try out by importing these schema files also under External Definitions along with the main WSDL and check whether they are referenced.
OR
Manipulate the WSDL in any of XML editior and to Include the schema files into the main WSDL. and then import the WSDL.
Regards,
AshwinM

Importing WSDL with external references issue

Hi guys,
pls help me on this:
I have a WSDL file which referes to external data types. Obviously, if I want to create a message mapping I can't see the WSDL data type. How are such situations resolved? How to import external types into PI?
Thx, A.

HI,
You have to inport the WSDL alongwith all its external references.
You can refer the following threads:
Import WSDL with external reference
Re: PI 7.1: Importing a wsdl file with references to other xsd files
http://help.sap.com/saphelp_nwesrce/helpdata/en/26/9e97b0f525d743882936c2d6f375c7/content.htm

JAX-WS generated WSDL uses xsd:import and no option to inline schemas

Is it possible to configure JAX-WS 2.0/2.1 so that when generating WSDL at runtime it will inline the schema definitions instead of using the <xsd:import> method? Unfortunately, some clients (Adobe Flex, for example) do NOT know how to process schema imports. I realize that Adobe (and others) should fix the problem on their end and become fully spec compliant, but the cold reality is that they are not.
Any advice, suggestions, or solutions would be greatly appreciated.
Regards,
Todd

You should post this question either to the JAXB 2.0 and JAX-WS 2.0 forum (http://forums.java.net/jive/forum.jspa?forumID=46) or the JAX-WS dev mailing list ([email protected]) so that the team is aware of the issue.
That functionality currently does not exist. The only work around that I am aware of is to generate the WSDL before deployment and rearrange it as necessary.

Problem: bpel deployment with xsd choice

hi!
i have the problem that after deploying my bpel process i dont see the choice defined in my xsd. with a very simple example the choice just dont show in the bpel console. (bpel processes => initiate => xml source just shows the xml without the choice)
i use jdeveloper 10.1.3.1.0.3984.
does anyone know a solution for this problem?
thanks
my xsd:
<?xml version="1.0" encoding="ISO-8859-15" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
            xmlns="http://www.example.org"
            targetNamespace="http://www.example.org"
            elementFormDefault="qualified">
<xsd:element name="exampleElement">
    <xsd:annotation>
      <xsd:documentation>
        A sample element
      </xsd:documentation>
    </xsd:annotation>
    <xsd:complexType>
      <xsd:sequence>
        <xsd:element name="element1" type="xsd:string"/>
        <xsd:choice>
          <xsd:element name="element3" type="xsd:string"/>
          <xsd:element name="element4" type="xsd:string"/>
        </xsd:choice>
      </xsd:sequence>
    </xsd:complexType>
</xsd:element>
</xsd:schema>the bpel process consists just of an assign-component.

Is JAXB 1.0 used to generate the client code. xsd:choice is supported, but xsd:any is not supported by JAXB 1.0.

Import collides with another import statement

Suppose I have 2 packages, train and plane. Each package has a class called Engine. In addition, train.Engine and plane.Engine have nothing in common. In a 3rd class, I import both of these:
import train.Engine;
import plane.Engine;Doing so results in the following error:
The import plane.Engine collides with another import statement
How do I do this?

One of these imports have to be commented. The imports are reside in the source code, not just in jar or other class path entries. If the imports are in different files then you'd browse the sources and find import with the same name but in different name spaces. This is happened if you you don't wanna add a big jar to the class path instead you created a class file with the same name because of huge references. And you just wanted route it out of the jar and possibly remove dependency.

The import collides with another import statement

What is this? Why this happens? I've just imported a class name to the JSP that has much more level imports. This JSP isn't even validated. I don't wanna rename my class has the same name as in one of the jar files on the class path.

nromanc wrote:
Skipping imports is not possible."skipping" as in not having any. Not possible? Why?
More naturally fully qualified names could be used in the rarely used practices.
much more typing and increase in the file size happens.The size of your source file might increase, yes.
Wild-cards also lead to not optimized imports hence bad performance.Imports are a compile-time only construct. Any performance impact import wildcards might have are limited to compile-time.
I didn't find correct answer in an old thread.
I've posted correct answer but a moderator is blocked it.The reason for blocking it is given as "your post as it doesn't make much sense, and detracts from the good advice already given and well received."
I do not know what you wrote. I cannot see blocked posts. I have no reason to doubt the reason given.

Problem validating XML with XSD

Hi everyone. I have an xsd schema and I want to validate some XML doc with the schema using SAX parser.
The user make the xml and then upload it to the server.
I want to enable client side validation but, for security reasons, I want also to validate this document when it's uploaded to the server.
The schema called ContentSchema.xsd
<?xml version="1.0" encoding="ISO-8859-1" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
     targetNamespace="www.mysite.com/Content" xmlns="www.mysite.com/Content">
     <xs:element name="content">
          <xs:complexType>
A document produced by the client starts in this way:
<?xml version="1.0" encoding="UTF-8"?>
<p:content xmlns:p="www.mysite.com/Content" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="www.mysite.com/Content ContentSchema.xsd">
in this way users can validate the XML doc before uploading. If the XSD is in the same folder of the uploaded XML the validation is ok.
The problem is that, on the server, I've stored the xsd file in a folder and I want the SAX parser to use this xsd to validate the XML. Even I pass the complete URI of the file to the parser, it won't work:
SAXParserFactory spf = SAXParserFactory.newInstance();
          spf.setValidating(true);
          spf.setNamespaceAware(true);
          spf.setFeature("http://apache.org/xml/features/validation/schema",true);
          spf.setFeature("http://apache.org/xml/features/validation/schema-full-checking", true);
          SAXParser sp=spf.newSAXParser();
          sp.setProperty("http://apache.org/xml/properties/schema/external-schemaLocation", schemaURL );
I set the schemURL with setProperty method but it's like the parser is looking for the XSD in the URL declared in the XML doc and not in the URI I specify. Anyone can help me?
Thank you very much

You will have to associate the schema with the namespace, like in your xsi:schemaLocation attribute.
Try something like this:
sp.setProperty("http://apache.org/xml/properties/schema/external-schemaLocation", "www.mysite.com/Content "+schemaURL);

Problem in mapping with xsd:restriction and xsd:enumeration

Hello All,
Our BPEL process is invoked from a .net client and has a JCA adapter as target. We need to map the input schema to JCA schema and the output should look like the following:
Listing 1:
<callMethod name='F4211FSBeginDoc' app='XMLInterop'
runOnError='no'>
<params>
<param name='mnCMJobNumber' id='1'></param>
<param name='cCMDocAction'>A</param>
<param name='cCMProcessEdits'>1</param>
<param name='szCMComputerID' idref='2'></param>
<param name='cCMUpdateWriteToWF'>2</param>
<param name='szCMProgramID'>XMLInterop</param>
<param name='szCMVersion'>ZJDE0001</param>
<param name='szOrderType'>SO</param>
<param name='szBusinessUnit'> M30</param>
<param name='mnAddressNumber'>4242</param>
<param name='jdOrderDate'>2000/03/29</param>
<param name='szReference'>10261</param>
<param name='cApplyFreightYN'>Y</param>
<param name='szCurrencyCode'></param>
<param name='cWKSourceOfData'></param>
<param name='cWKProcMode'></param>
<param name='mnWKSuppressProcess'>0</param>
</params>
We have our JCA schema as follows:
Listing 2:
<types>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:iwaysoftware:jde/services/JDEJAVA_CSALES/B4200310/F4211FSBeginDoc"
xmlns:ns="urn:iwaysoftware:jde/services/JDEJAVA_CSALES/B4200310/F4211FSBeginDoc" elementFormDefault="qualified">
<xsd:element name="jdeRequest">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="callMethod">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="params">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="param" minOccurs="0" maxOccurs="112">
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="name" use="required">
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="mnCMJobNumber"/>
<xsd:enumeration value="cCMDocAction"/>
<xsd:enumeration value="cCMProcessEdits"/>
<xsd:enumeration value="szCMComputerID"/>
<xsd:enumeration value="cCMErrorConditions"/>
<xsd:enumeration value="cCMUpdateWriteToWF"/>
<xsd:enumeration value="szCMProgramID"/>
<xsd:enumeration value="szCMVersion"/>
<xsd:enumeration value="szOrderCo"/>
<xsd:enumeration value="mnOrderNo"/>
<xsd:enumeration value="szOrderType"/>
<xsd:enumeration value="szBusinessUnit"/>
<xsd:enumeration value="szOriginalOrderCo"/>
<xsd:enumeration value="szOriginalOrderNo"/>
<xsd:enumeration value="szOriginalOrderType"/>
<xsd:enumeration value="mnAddressNumber"/>
<xsd:enumeration value="mnShipToNo"/>
<xsd:enumeration value="jdRequestedDate"/>
<xsd:enumeration value="jdOrderDate"/>
<xsd:enumeration value="jdPromisedDate"/>
<xsd:enumeration value="jdCancelDate"/>
<xsd:enumeration value="szReference"/>
<xsd:enumeration value="szDeliveryInstructions1"/>
<xsd:enumeration value="szDeliveryInstructions2"/>
<xsd:enumeration value="szPrintMesg"/>
<xsd:enumeration value="szPaymentTerm"/>
<xsd:enumeration value="cPaymentInstrument"/>
<xsd:enumeration value="szAdjustmentSchedule"/>
<xsd:enumeration value="mnTradeDiscount"/>
<xsd:enumeration value="szTaxExplanationCode"/>
<xsd:enumeration value="szTaxArea"/>
<xsd:enumeration value="szCertificate"/>
<xsd:enumeration value="cAssociatedText"/>
<xsd:enumeration value="szHoldOrdersCode"/>
<xsd:enumeration value="cPricePickListYN"/>
<xsd:enumeration value="mnInvoiceCopies"/>
<xsd:enumeration value="mnBuyerNumber"/>
<xsd:enumeration value="mnCarrier"/>
We are not able to create a valid structure from the above schema. Our output variable looks like
Listing 3:
ns5:jdeRequest
     type
     session
     sessionidle
     ns5:callMethod()
          name
          app
          runOnError
          returnNullData
          trans
          ns5:params
               ns5:param
                    name
No variables are displayed under the 'name' tag.
How can we map the input elements to Listing 2 and produce Listing 1? This is a bit urgent requirement for our client and any help will be greatly appreciated.

Hi,
With reference to your question.
Can any operator perform this task..I don't think any single operator will help you.
I suggest using an intermediate (staging) table by using a PL SQL procedure with output port to store the values of account number provided the number of accounts are limited. Else use an array variable for account of an employee.
In short no simple solution because of the bad source design else the pivot/unpivot operator would have helped you.
Cheers
- Mohammed

Database to XML with XSD (XML schema)

I have an Oracle 9 DB.
I need to convert data from a table (Java ResultSet) to XML (I have an XML schema file).
How can I do?
Is there a tool?
Thanks, Ludo.

Refer to
Oracle Xml Sql Utility.
http://www.xml.com/pub/r/846

HUGE PROBLEM: xsd:import generates invalid WSDL during deploy (11.1.1.3.0)

Hi,
I have a big problem:
if I create a bpel/mediator based on XSDs that use xsd:import, like this:
<xsd:import schemaLocation="./Generic.xsd" namespace="http://test.mydomain.com/test/Generic"/>
when i deploy, I get an error trying to test the service using oracle EM.
THe error looks like:
Either the WSDL URL is invalid or the WSDL file is not valid or incorrect. - java.io.IOException: WSDLException: faultCode=OTHER_ERROR: Lettura di WSDL da http://dev-oraclevmmac:8001/soa-infra/services/default/TestSOAProject/bpelprocess2_client_ep?XSD=./xsd/Test.xsd non riuscita: WSDL non trovato
What can I do ?

Yes, of course XSD and WSDL are valid inside JDev. I validated them also using XMLSpy.
The problem is that the WSDL becomes invalid through deployment.
But, after some hour of investigation, I've come to a solution: I have to puth the ABSOLUTE PATH ('relative' to the .bpel file) inside each xsd:import and inside wsdls.
So, my example is now:
<xsd:import schemaLocation="../xsd/Generic.xsd" namespace="http://test.mydomain.com/test/Generic"/>

Generating the wsdl with inline schema for the bpel process

Hi
When a BPEL process is deployed, we can get the WSDL of the same by logging into the BPEL console, but the WSDL contains the reference to the schema using the namespace. Can we generate the wsdl with the inline schema.
Suggestions are highly appreciated.
Thanks

Hi,
If the wsdl is referring to a Schema file you won't be able to see the schema definition in the WSDL file itself,for that you have to refer to the deployed jar which contains the XML schema.The default path for the deployed jar is <Oracle_SOA_Installed_Home>/bpel/domains/<domain_name>/tmp/<bpelprocess.jar>
Otherwise if you have the source project you can always refer to it in JDev.
Rgrds.

Import command error while importing in oracle 8i database.

Hi,
Trying to import a schema using imp utility in oracle 8i using sucessfully exported dump file in oracle 11g. But getting below errors.
IMP-00010: not a valid export file, header failed verification
IMP-00000: Import terminated unsuccessfully
Please provide any solution for this above error so that i can import a schema in Oracle 8i database.
Thanks.

dump file created in 11g database can't be imported in lower 8i version.
Restrictions When Using Different Releases of Export and Import
The following restrictions apply when you are using different releases of Export and Import:
Export dump files can be read only by the Import utility because they are stored in a special binary format.
Any export dump file can be imported into a later release of the Oracle database.
The Import utility cannot read export dump files created by the Export utility of a later maintenance release. For example, a release 9.2 export dump file cannot be imported by a release 9.0.1 Import utility.
Whenever a lower version of the Export utility runs with a later release of the Oracle database, categories of database objects that did not exist in the earlier release are excluded from the export.
Export files generated by Oracle9i Export, either direct path or conventional path, are incompatible with earlier releases of Import and can be imported only with Oracle9i Import. When backward compatibility is an issue, use the earlier release or version of the Export utility against the Oracle9i database.
Thanks
Kuljeet Pal Singh
Edited by: Kuljeet Pal Singh on Mar 19, 2012 7:43 PM

Validating WSDL with schema imports

Hello,
i'm trying to validate a WSDL that uses a schema import construction, like
<wsdl:types>
<xsd:schema>

<xsd:import namespace="http://foo" schemaLocation="http://localhost/foo.xsd"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="MyMessage">
<wsdl:part name="bar" type="foo:BarType"/>
</wsdl:message>
I keep getting the error :
Validating foo.wsdl
Schema type not found: QName(http://foo, BarType)
Validate WSDL: has errors.If I paste the content of foo.xsd inline in the wsdl file, it works ok.
The wsdl file validates in XMLSpy; it can even successfully generate SOAP requests from it.
Am I wrong somewhere ?
Did anyone succeed in importing an external schema inside a wsdl file with JDev ?
thx.

Does anyone know if this is working in JDeveloper 10.1.3?
Another (relared) question: we use multiple wsdl files to define our web services (according to the Venetian Blind design). Since the project uses WebLogic as AS we used their mechanism to generate the webservice. The only thing is that generating a stub via WebLogic JAX-RPC fails due to namespace errors.
When I try to generate a stub based on the JDeveloper 10.1.3 wizards using the top-level wsdl (the one importing other wsdl's) I get an invalid wsdl message and the options in the wizard are disabled. Anyone know whether multiple wsdl's are supported in JDeveloper 10.1.3?
Ronald

Problem Import WSDL with XSD import Schema

Similar Messages

Maybe you are looking for