Namespace issue--No target namespace in the xsd

Hi All,
Currently facing error at the time of deploying composites because of namespace issues
I have two source system XSD's without targetnamespace and both schemas are defaulted to the same namespace as xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
i am using these xsd's in bpel process as below
My Bpel processA (Using XSD-A) invoking source system with Operation A and source returns the XML content in string format and i am parsing the XML content using XSD-A. After parsing based on the business logic i am invoking Bpel process C.
After Invoking bpel process C , Bpel process A invokes Bpel process B with 3 input parameters. Now my Bpel process B invokes source system with Operation B and source returns the XML content in string format and i am parsing the XML content using XSD-B.
Now at the time of deployment i am facing issue in deploying Bpel Process-A and getting errors as *"element names are duplicated"*. In Both XSD most of the element are named as same including root element.
I am sure this happens because there is no qualifier namespace in the xsd to avoid ambiguous.
Could some one please help me in solving this issue by using same xsd without namespace
Regards,
Tarak.

Hi,
Thanks for the response
No simple solution... You will have to work this around... In your case you have the xml as string, so may you can inject a namespace there and change the XSD's accordingly...
Yes.. Its difficult to get the solution for this and more over i am not using both xsd's but using wsdl file of sever address side in reference panel which as the second XSD with same namespaces.
I tried injecting custom namespace to solve the issue but at run time i am not able to get the node values because source system giving with default namespace and in SOA i am accepting with custom targetnamespace.Because of this my xpath is not working.
Separate into two composites would be another way, but that doesn't seem to be an option...
This can be done but again one composite should reference the other one which in turn coming back to the same problem.
For Work around i have create one more service which can break the dependency between two services using xsd's of same default namespace. But i feel this is not an effective solution for designing the process.
Let me know if you strike with some work around on this.
Regards,
Tarak.

Similar Messages

Namespace issue while generating XML based on xsd

Hi All,
I am using Jdeveloper-11.1.1.6
SOA:- 11.1.1.6
WLS:- 11.3.6
When i am publishing xml message i am getting name space issue.
My process design as i am getting a message from AQ JMS and doing a transformation with out any logic and writing into a file based on the xsd.
Here is the my target xsd structure
<xs:schema id="RelieveIntransitSchema"
targetNamespace="http://tempuri.org/RelieveIntransitSchema.xsd"
elementFormDefault="qualified"
xmlns="http://tempuri.org/RelieveIntransitSchema.xsd"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="RelieveIntransits">
<xs:complexType>
<xs:sequence>
<xs:element name="RelieveIntransit" minOccurs="1" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="RelieveStore" minOccurs="1" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence></xs:sequence>
<xs:attribute name="StoreID" type="xs:string"/>
<xs:attribute name="Units" type="xs:double"/>
<xs:attribute name="RelieveAllStores" type="xs:boolean"/>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="HeaderID" type="xs:string" use="optional"/>
<xs:attribute name="ProductID" type="xs:string" use="required"/>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
My actual target xml should be of
<?xml version="1.0"?>
<RelieveIntransits xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://tempuri.org/RelieveIntransitSchema.xsd">
<RelieveIntransit HeaderID="DA41198901491301" ProductID="D037-63-1270S">
<RelieveStore StoreID="D001" Units="0002092 " />
<RelieveStore StoreID="D003" Units="0000022 " />
</RelieveIntransit>
</RelieveIntransits>
But the out xml generating as below which is not accepted by target system
<?xml version="1.0" encoding="UTF-8"?>
<RelieveIntransits xmlns="http://tempuri.org/RelieveIntransitSchema.xsd" xmlns:ns5="http://tempuri.org/RelieveIntransitSchema.xsd"> <ns5:RelieveIntransit ProductID="6534562" HeaderID="10R7771-6534562001-109"> <ns5:RelieveStore Units="5" StoreID="118"/>
<ns5:RelieveStore Units="5" StoreID="118"/>
</ns5:RelieveIntransit>
</RelieveIntransits>
Could some one please help me how to generate actual one as shown above with out namespace prefix "ns". I tried xsl code for removing name space prefix using https://forums.oracle.com/forums/thread.jspa?threadID=1122673 but it is removing url also.
Regards,
Tarak
Edited by: Tarak on Jul 26, 2012 11:39 AM

Hi,
Sorry for my delay response.
Both xmls are valid and equivalent for me... should be equivalent to <ns1:a xmlns:ns1="namespace"/>...
I agree to your point.
What is your target system? If that makes difference for your target system I would say it is not fully XML compliant...
Target system is an old one called as MID. Yes i agree it is not fully XML Compliant. I am publishing the message through file adapter and it is reading the file.
But anyway... The trick in the other thread should work... What do you mean by "removing url also" ???
Using the Namespaces remove xsl code i am getting structure as below. In this alone with prefix name space url also getting removed.
<RelieveIntransits>
<RelieveIntransit HeaderID="DA41198901491301" ProductID="D037-63-1270S">
<RelieveStore StoreID="D001" Units="0002092 " />
</RelieveIntransit>
</RelieveIntransits>
I am expecting like this
<?xml version="1.0"?>
<RelieveIntransits xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://tempuri.org/RelieveIntransitSchema.xsd">
<RelieveIntransit HeaderID="DA41198901491301" ProductID="D037-63-1270S">
<RelieveStore StoreID="D001" Units="0002092 " />
</RelieveIntransit>
</RelieveIntransits>

Target Namespace in imported WSDL

Hello All,
I have an interface that sends data from SAP to 3rd party system.
3rd party team gave us the WSDL and some XSD's of the interface they have on their system.
Now, the problem - target namespace on that WSDL is more than 60 characters. Because of this PI 7.0 is unable to recognise XSD's which are external references on imported WSDL document.
When i reduced the target namespace on the WSDL manually to less than 60 characters and uploaded WSDL again, external references are identified by PI.
Now, can i use this WSDL by reducing the target namespace? Will it work? Will i get any problems because of this in the future?
Can I delete target namespace from WSDL and use the WSDL as target namespace is optional?
Thanks
Chandra
Edited by: Chandra Sekhar H on Jul 19, 2010 10:45 AM

Now, can i use this WSDL by reducing the target namespace? Will it work? Will i get any problems because of this in the
future?
You can use the wsdl without any issue. If you need to know more: https://service.sap.com/sap/support/notes/901988
Regards,
Abhishek.

No namespace tag in target message (Test Interface mapping)

Hi,
I'm doing a IDoc to file scenario, and I'm using external definitions and a XSLT mapping. When I try to test the mapping in Interface Mapping he maps it but I can't see the tree view, I only get the source code...
<?xml version="1.0" encoding="utf-8"?>
<SenderID/><ReceiverID/><DocumentDate>20051028090653</DocumentDate>
<DocumentNumber>456184</DocumentNumber><TestIndicator> P</TestIndicator>
<Version>1.0/SSCC</Version>
<Desadv><MessageReferenceNumber>81749973</MessageReferenceNumber></Desadv>
I presume that there is a namespace tag needed like
<ns:Desadv xmlns:ns="http://www.certione.com/RFDesadv/Schema">
but I don't know what to do to have it added to the target message which is external definition Desadv with namespace http://www.certione.com/RFDesadv/Schema in the XSD...
Any help would be appreciated!
Kind regards..
Message was edited by: Bart De Saedeleer

Hello,
Could you put your XSD definition ?
And check your mapping because it seems that you don't have a root node in output.
<?xml version="1.0" encoding="utf-8"?>
<MYROOTNODE>
<SenderID/><ReceiverID/><DocumentDate>20051028090653</DocumentDate>
<DocumentNumber>456184</DocumentNumber><TestIndicator> P</TestIndicator>
<Version>1.0/SSCC</Version>
<Desadv><MessageReferenceNumber>81749973</MessageReferenceNumber></Desadv>
</MYROOTNODE>
Regards,
Chris
Message was edited by: Christophe DUMONT

BizTalk Server 2013 R2 EDI EDIFACT custom Target Namespace is not being used

I have a client that has a partner that doesn't use the "out of the box" BizTalk EDIFACT 97A DELFOR schema. I'm using BizTalk Server 2013 R2. I need to use a custom target namespace. I have created a custom schema for EFACT_D97A_DELFOR with
a different namespace http://schemas.microsoft.com/BizTalk/EDI/EDIFACT/2006_<partnername>.
In the Parties agreement/Transaction Set Settings/Local Host Settings, I have the following in a separate row under the "Default", UNH2.1=DELFOR, UNH2.2=D, UNH2.3=97A and TargetNamespace=http://schemas.microsoft.com/BizTalk/EDI/EDIFACT/2006_<partnername>
It wants to use the out of the box schema from the error below but I need it to use the custom schema. If I change the input file with a UH2.5 value along with changing the root node to match it EFACT_D97A_DELFOR_<UNH2.5), it works but the partner
will not be sending this, so it's not an option.
Error details: An output message of the component "Unknown " in receive pipeline "Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
is suspended due to the following error:
Error encountered during parsing. The Edifact transaction set with id '' contained in interchange (without group) with id '000010080', with sender id '<senderid>', receiver id '<receiverid>' is being suspended with following
errors:
Error: 1 (Miscellaneous error)
70: Finding the document specification by message type "http://schemas.microsoft.com/BizTalk/EDI/EDIFACT/2006#EFACT_D97A_DELFOR" failed. Verify the schema deployed properly.
Error: 2 (Miscellaneous error)
71: Transaction Set or Group Control Number Mismatch
Error: 3 (Miscellaneous error)
29: Invalid count specified at interchange, group or message level
Any thoughts for this issue?
Thanks,
Sean

All,
Because the trading partner is not sending the UNH2.5, UNG2.1 and UNG2.2 values in the incoming message, the EDIFACT custom targetnamespace schema will not be used. I created a decode custom pipeline component where I inject the UNH2.5 element,changed
the rootnode to the trading partner specific schema to EFACT_D97A_DELFOR_XYZ (where "XYZ" is the value in the UNH2.5) and in the Party agreement->TransactionSetSettings->LocalHostSettings default row specifying the UNH2.1, UNH2.2
and UNH2.5, it will then use the custom schema(http://schemas.microsoft.com/BizTalk/EDI/EDIFACT/2006#EFACT_D97A_DELFOR_XYZ. I could've injected the UNG segment
and used a custom target namespace and not changed the rootnode of the custom schema but didn't want to add all that extra segment information.
The example below assumes that the UNH segment only has values "up to" UNH2.4 only and appends the UNH2.5. Uses the UNA segement to dynamically set the componentDataElementSeparator.
//UNA segment e.g. UNA:+.? '
//this example above has ' as the segmentTerminator, : as the componentDataElementSeparator, + as the dataElementSeparator
string unaSegment = messageBody.Substring(0, messageBody.ToUpper().IndexOf("UNA") + 9);
string componentDataElementSeparator = unaSegment.Substring(3, 1);
string dataElementSeparator = unaSegment.Substring(4, 1);
string segmentTerminator = unaSegment.Substring(8, 1);
string UNH_Segment = messageBody.Substring(messageBody.ToUpper().IndexOf("UNH"));
UNH_Segment = UNH_Segment.Substring(0, UNH_Segment.IndexOf(segmentTerminator));
//inject UNH2_5 in the existing UNH_Segment
messageBody = messageBody.Replace(UNH_Segment,
UNH_Segment + componentDataElementSeparator + UNH2_5);
Thanks All for all your help!!
Sean Boman

Very Frustrated Namespace Issues Again !

Ok, This is crazy, I have created a freakin schema with simple string element. I then import to project. I then change message type to use this schema. I then create my bpel stuff. I then verify the wsdl and continue to get a Qname error stating it can't find the element.
Validating C:\OraBPELPM_1\integration\jdev\jdev\mywork\PreQual_Workspace1\USPSII\USPSII.wsdl
Schema element not found: QName(http://www.tnsi.com/ReadFileIn/, BatchID)
Validate WSDL: has errors.
I have no idea how to use namespace, the namespace will never be valid anywhere but internal to this application. Can someone please refer or show me what you should use as a namespace (project location or ????)
It will compile and deploy fine, its just when I use SoapScope or something to check the syntax it barfs, or if I simply ask J-Dev to verify WSDL.

Is there an address I can send you the project file so you can see... basically I have created a schema file, imported it, defined the target namespace in the schema. Then I set the input message type to use the imported schema file element. Once I verify the wsdl the imported the schema is can never find the element. This is just one of many issues with the namespacing.
I tried to keep my namespace consistent across the application but now I am getting duplicate namespace issues.
Any help would be much appreciated.

How to remove namespace prefix from target payload when using HTTP in PI7.0

Hi,
i have a requirement to remove namespace prefix from target payload when receiver receives the payload by an HTTP request.
i am not able to use XML Anonymizer Bean as in HTTP channel its not possiile.
Target structure after mapping now is:
<?xml version="1.0" encoding="UTF-8"?>
<ns3:Order xmlns:ns3="urn:xxx-com:pi:project">
fields
</ns3:Order>
i need the target structure after mapping should look like:
<?xml version="1.0" encoding="UTF-8"?>
<Order xmlns:="urn:xxx-com:pi:project">
fields
<Order>
i removed namespace from source and target Message Type of message mapping but still getting "ns3" prefix. My requirement is to just have this ns3 removed.
Please reply if anyone has solved this problem before.
Thanks

Hi ,
>>>i removed namespace from source and target Message Type of message mapping but still getting "ns3" prefix. My requirement is to just have this ns3 removed.
Which process you've used for removing namespace...java/xslt mapping. In case of java mapping plese remove ns3 while creating the target element. Please go through the below blog it may help you.
Quick Tips: Dealing with Namespaces in XI/PI
Regards,
Priyanka

XSLT Mapping and Namespace Issues

I have been reading through similar threads on this topic, but have not found the right combination for my problem. I am doing an XSLT map and it works fine in Stylus Studio. When I take it to PI, I get a "Prefix 'ns0' is not mapped to a namespace" error. I have a namespace that is within the XSD files I received from my partner (http://www.ups.com/XMLSchema/EBR/Billing/v1). I also have the namespace I made in PI for the source (http://graybar.com/upsbilling/) and a different namespace in PI for the destination (http://graybar.com/cold/invoice/).
XSLT:
<?xml version='1.0' encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ns0="http://www.ups.com/XMLSchema/EBR/Billing/v1" xmlns:ns1="http://graybar.com/cold/invoice/">
<xsl:template match="/">
<ns1:ColdInvoiceData>
<Header>
<RecordID>HDR</RecordID>
<InvoiceDate>
<xsl:value-of select="ns0:UPS_EBR_BILL/ns0:InvoiceDetails/ns0:Invoice/ns0:InvoiceDateCCYYMMDD"/>
</InvoiceDate>
Source XML
<?xml version="1.0" encoding="ISO-8859-1" ?>
<UPS_EBR_BILL xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.ups.com/XMLSchema/EBR/Billing/v1" xsi:schemaLocation="http://www.ups.com/XMLSchema/EBR/Billing/v1 Billing_XML_Schema.xsd">
<XMLBillFileVersion>1.0.1</XMLBillFileVersion>
<Recipient>
When I change the XSLT namespace from http://www.ups.com/XMLSchema/EBR/Billing/v1 to http://graybar.com/upsbilling/, the TransfromerException in PI goes away, but none of my referenced mappings work either (just my text hardcodes).
Can someone tell me why this works in Stylus Studio, but not in PI? Do I have too many namespaces?
Message was edited by:
Keith Wendel (to uncomment xsl:stylesheet line)

> <ns1:ColdInvoiceData xmlns:ns1="http://graybar.com/cold/invoice/">
This change did not affect anything. Still works in Stylus Studio though.
Did you mean to show any changes at the <xsl:value-of select> line? I did not notice anything there.
Can anyone explain what "not mapped to a namespace" means? I have the declaration of ns0 at the top, so I don't see what else needs to be mapped. Do I have to have my PI namespace where I store the partner's XSDs set as "http://www.ups.com/XMLSchema..." (partner's namespace)?

Java mapping & namespace issue

Hello,
I am doing a java mapping from a flat file to an IDOC. After the document is mapped succesfully I call an RFC via the Adapter. When monitoring the adapter I get the error:
com.sap.aii.af.rfc.RfcAdapterException: failed to read funtionname from XML document: missing namespace declara
so I added the namespace reference to my java mapping to look like this :
<ns0:IDOC_INBOUND_ASYNCHRONOUS xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
But when I test my java mapping in the builder (interface mapping) the namespace xmlns="urn:sap-com:document:sap:rfc:functions" is added to my above ns0:IDOC_INBOUND_ASYNCHRONOUS tag. The consequence is that while mapping in the integration engine the "ns0" prefix is then removed and I get the error:
Delivery of the message to the application using connection AFW failed, due to: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was.
Any help or sample code resolving the namespace issue is welcome.
Frank

Hi Frank,
I am getting the same error message. You fixed yours. Can you help me with mine. The error message is
" Delivery of the message to the application using connection AFW failed, due to: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was ."
I am trying to send data to SAP SRM4.0 from SAP R/3 using SAP XI. XI content is delivered by SAP.
The message is sent from R/3 to XI successfully and the XML monitor does not show any errors in XI . But the messages does not show up in SRM.
Thanks
Kishore.

Namespace issue with oracg generated classes

Hi,
I'm having problems generating classes with oracg from the Java Xdk from an XML schema. All classes are generated, but do not compile. In some sources (mostly in the type classes) "public void addSomething(null.Something theSomething)" is generated as the method declaration, and that doesn't compile. When I add a targetnamespace to the xsd file, the generated sources compile (the 'null.' is replaced with 'myPackage.', but when I generate an XML document, I contains a namespace reference (ns1) like this:
<ns1:Note xmlns:ns1 = "http://www.somewhere.org">
<ns1:Form>
<ns1:Reference>
<ns1:ReferenceNbr>1</ns1:ReferenceNbr>
<ns1:ReferenceType>1</ns1:ReferenceType>
</ns1:Reference>
</ns1:Form>
</ns1:Note>
What I want is this:
<Note>
<Form>
<Reference>
<ReferenceNbr>1<ReferenceNbr>
<ReferenceType>1<ReferenceType>
</Reference>
</Form>
</Note>
How can I get this result ?
Kind regards.

Did you try adding the the XmlSeeAlso annotation to the webservice
@XmlSeeAlso({<package.name>.AccountIC.class})
This will add the schema for the data type (AccountIC) to the WSDL.
Hope this helps.
-Ajay

Namespace issue in a B2B scenario

Hi all,
I have an iDoc to iDoc B2B scenario (R/3<->XI<->XI<->R/3),
My partner has defined an iDoc extention and sent me the xsd.
Now I have a problem in defining the interface because I don't have the same iDoc definition(different R/3 version) so I cannot import it into the IR, and I cannot define the message type and message interface as an external definition because the MI is in the iDoc reserved namespace.
How can I solve this conflict ?
Thanks,
Elad.

Hi Elad (or Ofir?),
my idea was to change temporary connection data for import from SAP system of SWKV. The question is, if you dont have connection to that system, how do you want to connect with XI and how do you want to test?
2. idea was: instead of imported idoc you just create a dummy interface in repository. The interfaces itselfes (and so the imported idocs) will not be validated by integration engine. Only if you use message mapping you really NEED a correct XSD schema.
So something like R/3 idoc -> own interface -> any mapping except message mapping -> loaded idoc interface -> other R/3
Regards,
Udo

Changing default target namespace for a JPD

Hi,
Is there a way in Workshop 8.1 to change the target namespace used when a WSDL
is generated from a JPD? Currently, Workshop uses http://www.openuri.org. I
have tried to use the @common:target-namespace annotation in my JPD, but that
appears to only be valid for JWS files. Is there a way to globally set the default
target namespace for an entire Workshop project?
Thanks,
Nick

And to just make it more clear :
and here is the SAP help on the subject:
Transport Layer in ABAP Workbench
The Change and Transport System supports the distribution of development work on large projects across multiple SAP Systems.
The packages in each development system are grouped into one transport layer.
The transport layer determines whether objects are assigned to a local or transportable change request.
Use
Each of your SAP development systems is assigned a transport layer as its standard transport layer. If you use Extended Transport Control, you can assign different standard transport layers to certain clients.
You can define at the most one consolidation target for each SAP System and transport layer.
When you create a package, it is assigned the standard transport layer of the SAP System.
If you want to assign a different transport layer to a package, you require the administration authorization for the Change and Transport System.
The objects in a package automatically have the transport attributes defined for the corresponding transport layer.
If a consolidation route originating in their SAP System is defined, then the objects are assigned to a transportable request, and transported into the consolidation target when it is released.
If a consolidation route is not defined, the objects are assigned to a local request, and are not transported.
Customizing settings are not assigned to a package. They have the transport attributes of the standard transport layer of the system or client.
It is best to assign a package a standard transport layer for which a consolidation route originating in the development system is defined.
To display and maintain the transport layers and routes, use the Transport Management System (transaction STMS).
Only the system adminstrator can make changes.
Caution:
The tables TSYST, DEVL, TWSYS, TASYS are no longer productive as of Release 4.0A and cannot be maintained.
Best regards,
Menelaos

Error target namespace must be absolute URI when consuming external WSDL

Hi,
I'm trying to consume external WSDL which has relative target namespace.
Through SE80 transaction I select Create -> Enterprise Server -> Service Consumer.
I have tried with URL and local file options but the result is the following in both cases:
At the en of the wizard I receive the errors "exception in Error-Handler" and "Error target namespace must be absolute URI".
I'm on ECC 6.0 SP 18.
Anybody knows how to solve this problem? Maybe is not possible to consume external WSDL with relative URI?
Thanks
Regards

Hi,
I think the problem is that the WSDL is not WS-I compliant.
I have found note 1327511 (Limiations and common problems in ABAP WSDL processing) and with the report RSSIDL_DESERIALIZE_DEMOI have found the same error.
Anybody can confirm this?
Is there any other document or reference where SAP indicates this fact?
Thanks
Regards

Namespace issue after updating to AIR 3.9

I am using Flash Builder 4.6. I just downloaded the new AIR SDK 3.9 and copied the files in it over a copy of Flex SDK 4.6.0 After doing this, when I create a new Flex Mobile Project, I see multiple namespace issues. Any idea what might be the issue?

Any help on this? I tried both on Mac and PC, both have same issues. When I create a new Flex Mobile project, the parent tag of the main application is Application while it should have been a ViewNavigatorApplication. The default HomeView screen created starts as:
<fx: xmlns:fx="http://ns.adobe.com/mxml/2009"
Any help on this?

Target Namespace in a WSDL file

Hi,
I had generated a JPD from a WSDL file using the "Generate JPD file" option in
weblogic workshop. The WSDL file has a target namespace specified ("wli.abc.com").
When i access the JPD as a webservice using the WebService Proxy , the target
namespace is the default target namespace(ie http://www.openuri.org/"), due to
which the methods on the webservice cannot be accessed. Is there a way i can change
the target namespace from http://www.openuri.org/ to wli.abc.com
Thanks in Advance

Hi Kiran,
You set the targetNamespace for the JPD-based Web service, in the Javadoc comments
section before the class declaration. It shows the place in the property sheet,
if you click on the JPD code, but I don't have the patience to figure out where
all the little "click-here-to-make-this-show-up" thingies are :-) It easier just
to go to the line before the */, and paste this:
* @common:target-namespace namespace="http://mortgagefamily.cendant.com/2003/10/cssg/webservice/appraisal"
Regards,
Mike Wooten
"kiran" <[email protected]> wrote:
>
Hi,
I had generated a JPD from a WSDL file using the "Generate JPD file"
option in
weblogic workshop. The WSDL file has a target namespace specified ("wli.abc.com").
When i access the JPD as a webservice using the WebService Proxy , the
target
namespace is the default target namespace(ie http://www.openuri.org/"),
due to
which the methods on the webservice cannot be accessed. Is there a way
i can change
the target namespace from http://www.openuri.org/ to wli.abc.com
Thanks in Advance

Namespace issue--No target namespace in the xsd

Similar Messages

Maybe you are looking for