Java Development Tools

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!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

WSDL generation and xmlns:ns0 reference

4098Jan 25 2006 — edited Feb 8 2006

(JDeveloper 10.1.2.0.0 on WinXP with jdk1.4.0._06)

Anyone knows how to avoid the following reference in Web Service generation (and why is it generated in the first place)? What should I do to eliminate it from WSDL, since .NET developers cannot create proxy based on it - Visual Studio fails on import:

Header looks like this:

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


<definitions
name="SymphonyIntegration"
targetNamespace="http://helix/symInt/HelixListenerImp.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://helix/symInt/HelixListenerImp.wsdl"
xmlns:ns1="http://helix.symInt/ISymphonyIntegration.xsd">
<types>
<ns0:schema
targetNamespace="http://helix.symInt/ISymphonyIntegration.xsd"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="http://schemas.xmlsoap.org/wsdl/">

My question is: why is there xmlns:ns0 generated for this schema definition?

Much appreciated,
Dejan

Locked Post

New comments cannot be posted to this locked post.

Locked on Mar 8 2006

Added on Jan 25 2006

#application-development-in-java, #jdeveloper-and-adf

2 comments

538 views