Skip to Main Content

Integration

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Name space issues with my xsds when I import in my SOA Composite

2962796Feb 25 2016 — edited Feb 28 2016

Hi,

I am migrating to SOA from a .NET project and the project xsd files were created in .NET with XML studio like below.

I see Namespace issues with my xsds when I import the xsds in my SOA Composite!

In my XSDs the namespace is defined like below.

<?xml version="1.0" encoding="utf-8"?>

<!-- Created with Liquid XML Studio 1.0.8.0 (http://www.liquid-technologies.com) -->

<xs:schema xmlns:tns="http://www.XXX.ae/DataDictionary/CommonTypes" elementFormDefault="qualified" version="2.0" id="PersonRegister" xmlns:xs="http://www.w3.org/2001/XMLSchema">

  <xs:import schemaLocation="CommonTypes.xsd" namespace="http://www.XXX.ae/DataDictionary/CommonTypes"/>

  <xs:element name="Person.Register">

    <xs:complexType>

    ...

    ...

I imported this in my Business rules component and when I build the SOA project it gives me the error saying Invalid Name space.

So,  in order to keep my test simpler,  first, I created a new dummy WSDL in my JDeveloper and dragged this xsd file  into the WSDL and the namespace appears as blank!!

Like below in my WSDL file...

<?xml version="1.0" encoding="UTF-8" ?>

<definitions targetNamespace="urn:WSDLDocument1" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="urn:WSDLDocument1"

             xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"

             xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"

             xmlns:types="">

  <types>

    <xsd:schema targetNamespace="urn:WSDLDocument1/types" elementFormDefault="qualified"/>

    <xsd:schema>

      <xsd:import schemaLocation="../../../SOA/Schemas/PersonRegister.xsd" namespace=""/>

    </xsd:schema>

  </types>

</definitions>

Please let me know what is the solution/workaround...

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Mar 27 2016
Added on Feb 25 2016
12 comments
2,897 views