Problem in the Namespace

Hi All,
I am trying to upload an xml file. but while uploading the file in the External Definition, there i am not getting any message nor the namespace in the MESSAGE tab.
The url which i am is using is like for Ex::( "http://www.checkfreeisolutions.com/xmlschema/cspintegration/v1.0") .
But when i am using some other url or when i am truncating the url also i am getting it right,
Now the problem is i have to use this url only.
So if anyone can let me know how can i do this. Or how can i increase the namespace length.
or if there is any other way out then please let me know .
thanks

XI namespace has a limit of 60 character. And the namespace http://www.checkfreeisolutions.com/xmlschema/cspintegration/v1.0 has more than 60 chars.
U cant increase the limit. So better to use some other namespace.
Regards,
Prateek

Similar Messages

[Castor] Problem with the namespace

Hello,
I'm using Castor for generate XML file with Java Object(generate with Castor with XSD).
I have a problem with the syntax and particulary with the reference of the namespace.
I obtain this :
<?xml version="1.0" encoding="UTF-8"?>
<TEST ID="">
<ns1:PERSON xmlns:ns1="http://www.w3.org/a/">
<ns1:CALCUL>
<ns1:SOURCE>RED</ns1:SOURCE>
<ns1:TIMESTAMP>2004-10-27-11.38.25.237113</ns1:TIMESTAMP>
</ns1:CALCUL>
<SIREN>666</SIREN>
<ns1:DOSSIER>
<ns1:TYPE>DN</ns1:TYPE>
<ns1:IDENTIFIANT>333</ns1:IDENTIFIANT>
</ns1:DOSSIER>
</ns1:PERSON>
<ENTITY>
<COMMON>
<ns2:ENTITY_ID xmlns:ns2="http://www.w3.org/a/">602449226</ns2:ENTITY_ID>
<ns3:RATING xmlns:ns3="http://www.w3.org/a/">NDE</ns3:RATING>
</COMMON>
<SPECIFICS_DATA>
<ns4:RATING_FC xmlns:ns4="http://www.w3.org/a/">2-</ns4:RATING_FC>
</SPECIFICS_DATA>
</ENTITY>
</TEST>
but I'd like to obtain :
<TEST ID="">
<PERSON >
<CALCUL>
<nSOURCE>RED</SOURCE>
<TIMESTAMP>2004-10-27-11.38.25.237113</TIMESTAMP>
</CALCUL>
<SIREN>666</SIREN>
<nDOSSIER>
<TYPE>DN</TYPE>
<IDENTIFIANT>333</IDENTIFIANT>
</DOSSIER>
</PERSON>
<ENTITY>
<COMMON>
<ENTITY_ID >602449226</ENTITY_ID>
<RATING>NDE</RATING>
</COMMON>
<SPECIFICS_DATA>
<RATING_FC >2-</RATING_FC>
</SPECIFICS_DATA>
</ENTITY>
</TEST>
"http://www.w3.org/a/" is the namespace reference in the xsd, here the begin of the xsd:
<xs:schema xmlns:FIN_Referential="http://www.w3.org/c/" xmlns:Rating_Referential="http://www.w3.org/f/" xmlns:Global_Referential="http://www.w3.org/a/" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
To marshall I use this code :
StringWriter fluxXmlSw = new StringWriter() ;
Marshaller mar = new Marshaller(fluxXmlSw);
mar.marshal(Test(),fluxXmlSw);
//Test() is the root element of the file xml
I hope somebody could help me, it's urgent I solve this problem.
Thanks for all responses

just a thought..... did u try removing xmlns:p1="http://ofcom.co.uk/unify/CustomerMaster" from your WSDL file ?
Try to remove that and proceed in your development.

Problem with the namespace in the soap message ' xmlns:p1'

Hi,
I have released a WSDL file which the siebel system is consuming to send the data to SAP XI .
the extract of the WSDL file is as below
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions name="MI_Customer" targetNamespace="http://ofcom.co.uk/unify/CustomerMaster" xmlns:p1="http://ofcom.co.uk/unify/CustomerMaster" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"><wsdl:types><xsd:schema targetNamespace="http://ofcom.co.uk/unify/CustomerMaster" xmlns="http://ofcom.co.uk/unify/CustomerMaster" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><xsd:element name="MT_Customer" 
if we see in the there is a attribute called xmlns:p1 which is creaing the problem as data sent is as below
 <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <MT_Customer xmlns="http://www.siebel.com/xml/MT_Customer" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <Customer>
<Cust_No>0005000013</Cust_No>
<Title>Mr.</Title>

due to this the XI system is not triggring the mapping.
as XI expects the data in the below format which we generated with the stylus studio tool
 <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <p1:MT_Customer xmlns:p1="http://ofcom.co.uk/unify/CustomerMaster" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
- <Customer>
<Cust_No>1232</Cust_No>
<Title>mr.</Title>

If anyone has any Idea as to how can we overcome this problem
Thanks
Nikhil

just a thought..... did u try removing xmlns:p1="http://ofcom.co.uk/unify/CustomerMaster" from your WSDL file ?
Try to remove that and proceed in your development.

Problems with the OPC Connector for older OPC DA servers?

Hello,
we are developing a solution involving OPC data access and want to utilize xMII as a gateway between the OPC server and our application. The xMII installation we use works fine with three different demoservers we connected, even when accessing them remotely.
When first trying to connect to our real datasource, we encountered problems. The namespace was not browsable from within the xMII Query Template editor. A taglist was given though, but the tags did not give proper results. The general log stated, that an "invalid server" was being used.
Other OPC clients which are designed for diagnostic use did not have any problems with namespace browsing or accessing the data in our server, so the problem was limited to the use of xMII. Reconfiguring the namespace of the OPC server led to data access working in xMII, but the namespace is still not browsable from within xMII.
We use a Simatic NET OPC Server, which states it fulfills OPC DA specification 1.0A and SAP xMII 11.5.1 with an OPCDatasource2_5_0_4beta Connector. The question is, if our problems could arise from our use of such an old OPC specification in the server? It is stated that the DataSource Connector works with "any OPC server", but as I understand it the actual specification is OPC DA 3.0, which would be quite a distance in versions.
Thanks in advance for any useful hints!
Andreas Gössling

Hello Martin,
thanks a lot for the answer! This is exactly the information I need to explain my senior staff members why it is not my fault.
Luckily, I found a stable state for cooperation between my components. Now I have the validation that this state must not be altered by others.
Thanks again!
Andreas

Problem importing WSDL having the namespace morethan 60 chars

Hi all,
I tried to import a WSDL file in external definition of namespace more than 60, it didnt show me any error but I was not able to see the message objects. When I change the namespace and then tried to import it I am getting the message objects. Is there any way to over come this problem?
Can I import the WSDL file by reducing the namespace length to less than 60 and is it possible to override the namespace during configuration time or runtime?
Regards,
Sivakumar Raja.R

Hi SivaKumar,
There is no solution, what SAP says is that this is fixed in SP14.
you cannot override the namespace at ID or IR.
Anyway, it does not affect you if you change the namespace and load the XSD. but only in case of CB routing u get trouble (especially when msgs come inwith a bigger namespace)
check this link (2 issues are discussed, one is yours)
Re: Does SAP XI support international XML standards like OASIS UBL?
Regards
Vishnu

The type or namespace name 'VisualStudio' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?)

we are using VS 2013. i have created new build definition and run that created build its getting failed and showing error message as "The type or namespace name 'VisualStudio' does not exist in the namespace 'Microsoft' (are you missing an assembly
reference?)" and "The type or namespace name 'WinComboBox, UITestControl, WinTitleBar.....etc' could not be found (are you missing a using directive or an assembly reference?)". in the error log is showing the error number are "error CS0234
& error CS0246".
Actually i have created build for automation execution from MTM lab environment. i have to assign the build to the test plan. once the build is passed , i will assign to the test plan and run with automation options.
if i build the solution its getting successfully build. but when i run the created build definition it show the error message's.
Could you guide me how to resolve the above error's ?
Thanks in Advance...

Hello Divakar Ponnada,
I have checked the error CS0234 from here:
http://msdn.microsoft.com/en-us/library/0e92xd7b.aspx
It means your project cannot find the proper reference to your type "Visual Studio" from the namespace Microsoft.
May I ask this question, does your build definition means something like the following blog described?
http://www.asp.net/web-forms/overview/deployment/configuring-team-foundation-server-for-web-deployment/creating-a-build-definition-that-supports-deployment
"A build definition is the mechanism that controls how and when builds occur for team projects in TFS. "
If that is the problem, may I ask whether your build agent is in the same machine where you build your application?
The build agent will first search for the reference from its local GAC and if it cannot find it, the error like you said will reports. Please manually build your project from your build agent machine to see the result, or install Visual Studio to your build
agent machine. In that way I think your problem may fixed.
Best regards,
Barry
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Tutorial - Create a blog reader Store app (C++) - Error:The name does not exist in the namespace!

I'm trying to create my first store app based on msdn's sample.
Link to the sample:
https://msdn.microsoft.com/pl-PL/library/windows/apps/hh465045.aspx
I have problem doing last step (number 3) of part 3.
In code below in file App.xaml the compiler get the error "The name 'FeedDataSource' does not exist in the namespace 'using:SimpleBlogReader'"
<Application
x:Class="SimpleBlogReader.App"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:local="using:SimpleBlogReader">
<Application.Resources>
<local:FeedDataSource x:Key="feedDataSource"/>
</Application.Resources>
</Application>
In the file App.xaml.h I added line #include "FeedData.h", and FeedData.h looks like:
//feeddata.h
#pragma once
#include "pch.h"
namespace SimpleBlogReader
namespace WFC = Windows::Foundation::Collections;
namespace WF = Windows::Foundation;
namespace WUIXD = Windows::UI::Xaml::Documents;
namespace WWS = Windows::Web::Syndication;
/// <summary>
/// A FeedDataSource represents a collection of FeedData objects
/// and provides the methods to retrieve the stores URLs and download
/// the source data from which FeedData and FeedItem objects are constructed.
/// This class is instantiated at startup by this declaration in the
/// ResourceDictionary in app.xaml: <local:FeedDataSource x:Key="feedDataSource" />
/// </summary>
[Windows::UI::Xaml::Data::Bindable]
public ref class FeedDataSource sealed
private:
Platform::Collections::Vector<FeedData^>^ m_feeds;
FeedData^ GetFeedData(Platform::String^ feedUri, WWS::SyndicationFeed^ feed);
void DeleteBadFeedHandler(Windows::UI::Popups::UICommand^ command);
public:
FeedDataSource();
property Windows::Foundation::Collections::IObservableVector<FeedData^>^ Feeds
Windows::Foundation::Collections::IObservableVector<FeedData^>^ get()
return this->m_feeds;
property Platform::String^ CurrentFeedUri;
void InitDataSource();
void RetrieveFeedAndInitData(Platform::String^ url, WWS::SyndicationClient^ client);
How to solve this problem?

You're testing this too early. You haven't yet finished writing code that your current code depends on. Feeddata.cpp won't build, so you can't use the data object that hasn't yet been created.
In particular, feeddata.cpp doesn't build since it has many references to items which get added in later steps.
For example, TextHelper is added in part 5 and App::RemoveFeed is added in part 10.
You'll need to either wait until you've implemented those before you test or comment out the calls to the unimplemented features until they're done. TextHelper looks like it adds quite a bit and you're almost there, but you can probably get away with commenting
out the calls to RemoveFeed and GetTitlesFromUri for now.

XAML DataContext: name does not exist in the namespace

I have created a new C# WPF Application project in VS 2013, named dataconfigtest. The namespace is dataconfigtest.
I add a new, public class named "TestDataClass". It is also in the dataconfigtest namespace.
I add the following code to the XAML file (MainWindow.xaml) in the <Window> section:
xmlns:local="clr-namespace:dataconfigtest"
I then define the datacontext as follows:
<Window.DataContext>
<local:TestDataClass />
</Window.DataContext>
When I build the project, I receive the following error:
The name "TestDataClass" does not exist in the namespace "clr-namespace:dataconfigtest"
I have tried:
closing/opening VS
removing/adding the project
creating a fresh project
cleaning and rebuilding
including the assembly information in the XAML "local" namespace definition
Note that I can set the datacontext in the C# code-behind. It's only in the XAML that I have problems.
Thank you for any help!
EDIT: I opened the same VS project file on a different computer and it worked. I will try repairing my installation of VS.
EDIT2: I have repaired the installation and rebooted. Same issue. I will try re-installing VS.

Hi Qubert,
>>The name "TestDataClass" does not exist in the namespace "clr-namespace:dataconfigtest"
From this error message,i think that your namespace could be incorrect or you need to rebuild the project.
This is my code snippets:
<Window x:Class="dataconfigtest.MainWindow"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:local="clr-namespace:dataconfigtest"
Title="MainWindow" Height="350" Width="525">
<Window.DataContext>
<local:TestDataClass></local:TestDataClass>
</Window.DataContext>
<Grid>
</Grid>
</Window>
public class TestDataClass
public string data { get; set; }
>>EDIT: I opened the same VS project file on a different computer and it worked. I will try repairing my installation of VS.
In my experience,your environment might be some problems, So please feel free to tell me the result of repairing your VS.

Error on new windows 8.1 project: The type or namespace name 'Foundation' does not exist in the namespace

I upgraded to win 8.1 and VS 2013. I created a new Windows 8.1 C# grid project and tried to compile it and I'm seeing the following error: Error 1 The type or namespace name 'Foundation' does not exist in the namespace [my namespace](are
you missing an assembly reference?)
The errors are in navigationhelper.cs line 59
[Windows.Foundation.Metadata.WebHostHidden] // Foundation has the squigglies
public class NavigationHelper : DependencyObject
and app.xaml.cs line 68 ==> rootFrame.Language = Windows.Globalization.ApplicationLanguages.Languages[0]; which causes this error: Error 2 The type or namespace name 'Globalization' does not exist in the namespace [my namespace] (are you missing
an assembly reference?)
Windows phone and mvc projects are working fine and I've installed all the updates and even tried to fix vs 2013.
Any help Is greatly appreciated.

I did some more investigation and noticed that if I create an app with a "." in the name then this problem occurs. For example create a windows store project with the default name "App1": this will compile.
However if I name the project "App1.Forms" to correspeond with the default namespace I want, then this problem occurs. Still investigating but anyone should be able to repro it with that step.

Problem in the XSD generation

Hi people,
In our project we are working a POC to integrate MDM. For it, the MDM people request the XSD that generated XI.
We send this XSD:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" >
 <xsd:complexType name="NombreDT">
 <xsd:sequence>
 <xsd:element name="campo1" type="xsd:string"></xsd:element>
 <xsd:element name="campo2" type="xsd:string"></xsd:element>
 <xsd:element name="campo3" type="xsd:string"></xsd:element>
 <xsd:element name="campo4" type="xsd:string"></xsd:element>
 <xsd:element name="campo5" type="xsd:string"></xsd:element>
 <xsd:element name="campo6" type="xsd:string"></xsd:element>
 </xsd:sequence>
 </xsd:complexType>
</xsd:schema>
The XML that we sent through scenario created in XI is:
<?xml version="1.0" encoding="UTF-8"?>
<NombreDT>
 <campo1>data1</campo1>
 <campo2>data2</campo2>
 <campo3>data3</campo3>
 <campo4>data4</campo4>
 <campo5>data5</campo5>
 <campo6>data6</campo6>
</NombreDT>
When MDM wants to import the XML to MDM's repository using the XSD as Schema, it shows the following error:
Logon Error: Failed to Parse XML file.
Error:
COM error: 80004005 Unspecified error
Source = Description =
SAX2Error: errCode=80004005, PublicId =,
Error Message= The element "NombreDT" is used but not declared in DTD/Schema.
They have provided us a XSD and a XML that works to them correctly:
XSD:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
<xs:element name="DataSuper">
<xs:complexType>
<xs:sequence>
<xs:element ref="MiniData" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="MiniData">
<xs:complexType>
<xs:attribute name="code1" use="required" type="xs:integer"/>
<xs:attribute name="code2" use="required" type="xs:NCName"/>
<xs:attribute name="code3" use="required" type="xs:NMTOKEN"/>
<xs:attribute name="code4" use="required" type="xs:NMTOKEN"/>
<xs:attribute name="code5" use="required" type="xs:NCName"/>
</xs:complexType>
</xs:element>
</xs:schema>
XML:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<DataSuper>
<MiniData code1="22550" code2="ppp" code3="150" code4="30" code5="dat1"/>
<MiniData code1="22551" code2="out" code3="400" code4="30" code5="dat2"/>
<MiniData code1="22552" code2="out" code3="350" code4="30" code5="dat3"/>
<MiniData code1="22553" code2="ppp" code3="1505" code4="30" code5="dat1"/>
</DataSuper>
Is it the problem of the XSD generated in XI?
What is the difference between xsd:element and xs:element?
Can we generate in XI a XSD of the type xs:element?
King Regards

Hi,
I think the problem is, that the xsd you posted contains only a type definition but no element definition. I would recommend trying:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" >
<xsd:complexType name="NombreDT">
<xsd:sequence>
<xsd:element name="campo1" type="xsd:string"></xsd:element>
<xsd:element name="campo2" type="xsd:string"></xsd:element>
<xsd:element name="campo3" type="xsd:string"></xsd:element>
<xsd:element name="campo4" type="xsd:string"></xsd:element>
<xsd:element name="campo5" type="xsd:string"></xsd:element>
<xsd:element name="campo6" type="xsd:string"></xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="NombreDT" type="NombreDT" />
</xsd:schema>
The reason why the original xsd you got from the Message TYpe contained this import statement is, that you decided to spread the definition of your Message Type over two namespaces. I assume that you changed the content of the field XML namespace in the Message Type to BLANK (by default it equals the technical namespace you define your Message Type in, in your case probably "myNamespace").
Greetings
Stephan

Inbound IDOC error (Name MARA is not in the namespace for generated BW Metaobjects)

Hi everybody,
we are currently having some issues with importing idocs into our ERP DEV System and i cannot figure out what the problem could be.
I am trying to import an IDOC Type ARTMAS (5) but i keep getting the following error "Name MARA is not in the namespace for generated BW Metaobjects"
The system is a ERP only system with no BI content activated at all.
I don´t find any more errors nor any dumps or SLG1 entries related to this issue.
Did someone already experienced that kind of problem, or do some of you maybe have an idea where to have a deeper look.
thanks & best regards
Peter
EDIT:
Running on ERP 6.0 EHP 7 SPS 4

Hi Ganesh,
I guess there is something wrong with the data in the ODS.
Check this post:
Re: error 18 in the update!
Bye
Dinesh

Name TCURC is not in the namespace for generated BI meta objects

Hi,
When I try to load data into infocube, I get a short dump during the DTP load with the below message
UNCAUGHT_EXCEPTION
Exception: CX_RSR_X_MESSAGE
Upon analysing the dump analysis I found the below system fields
SY-MSGTY E
SY-MSGID R7
SY-MSGNO 019
SY-MSGV1 TCURC
which gives the message text "Name TCURC is not in the namespace for generated BI meta objects"
If I remove the mapping with Amount KF in the TRFN and load data it works fine without error but on mapping the KF with currency unit I get this error.It is something related to Currency but I'm unable to figure out the problem.
Any suggestions on what could be the problem?
Thanks.

Is this the real error?
Please, can you check the currency conversion with the function module CONVERT_TO_LOCAL_CURRENCY?
Have you customize the currency-tables? Use the functions RSA1 -> source system -> context menu -> global settings + exchange rate
Sven

Problem with xml namespace

Hi,
I want to convert a csv-file that has follow structure as textfile:
field1,field2,field3
in a xml-file.
I also have created a mapping, so I get a mapping error when i want to convert the txt-file to xml
In the message monitoring the generated xml-file has follow structure:
<ns:target>
<Recordset>
 <source>
 <source_value_1>Source_value_1</source_value_1>
 <source_value_2>source_value_2</source_value_2>
 <source_value_3>source_value_3</source_value_3>
 </source>
</Recordset>
</ns:target>
and the xsd has follow structure:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
 <xs:element name="source">
 <xs:annotation>
 <xs:documentation>Comment describing your root element</xs:documentation>
 </xs:annotation>
 <xs:complexType>
 <xs:sequence>
 <xs:element name="source_value_1" minOccurs="0"/>
 <xs:element name="source_value_2" minOccurs="0"/>
 <xs:element name="source_value_3" minOccurs="0"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
</xs:schema>
So I get an error that there is a conflict in the namespace.
Can ynybody help me please.
Thanks
Regards
Stefan

Hi Stefan,
I do not think that your problem is the difference between xs and ns.
Indeed <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" >
and
<ns:schema xmlns:ns="http://www.w3.org/2001/XMLSchema" >
are logically equivalent.
Also
<ns:schema xmlns:ns="http://www.im-c.de/test_01">
and
<xs:schema xmlns:xs="http://www.im-c.de/test_01">
are logically equivalent.
The problem is rather that in the first case the schema element belongs to the namespace
http://www.w3.org/2001/XMLSchema
whereas in the second case it belongs to the namespace
http://www.im-c.de/test_01
It is not clear to me how the second element was exactly produced but to me this seems not to make sense.
Greetings
 Stephan

XSLT problems convert with namespaces

We have a problem with xslt.
we are working with RAD 6.0.1.
We are Trying to convert XML that contain many tags to another xml using xsl file.
on some of the tags we have namespaces.
When we are trying to run our application that convert between the 2 xmls we are getting a new tag (the wanted tag) but all the attributes are empty. it is happanning only when the original tag has namespaces.
has anyone have the answer to this ?
Thanks in advance.
P.

In XSLT you put a prefix before the XPATH rule like this:
p1:root/p2:subnode/element
you declare the namespaces in header as attribute xmlns:p1="..."
Something like:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:p1="..." ...>
In your example you have to consider, that namespaces without prefix are inherited to subnodes. That means you have to build your XPATH like this:
p1:NemRefusionIndberetningSamling/p2:NemRefusionIndberetningStruktur/p3:HeaderStruktur/p3:ReferenceAttributTekst

Change in the namespace of the Client proxy?

Hi All,
I want to know if there is way to change the name space in an existing client proxy. The problem is the provider system is not fully set up yet. So the provider keeps changing the URL to the web services. What is the best way to handle such a situation ?
Do I need to re-create the proxy each time the namespace is changed or just the regeneration of the proxy is enough? In either case I believe WSDL file should be updated. Please guide me...
Regards,
Vamsi
Edited by: varaprasad bhagavatula on Apr 20, 2010 7:03 PM

changing URL of endpoint(webservice) won't affect your proxy but changing namespace will affect (there is difference between namespace and endpoint url),
1. If URL is changing then there is no need to create proxy again but change configuration part in SOAMANAGER.
2. If namespace is changed then you need to create proxy again.
Regards,
Gourav

Problem in the Namespace

Similar Messages

Maybe you are looking for