Ambiguous Namespace

I use Dreamweaver to generate an XSL fragment and am
embedding that in an .aspx page. When I load the page, I'm getting
the following error message: "BC30560: 'XSLTransform' is ambiguous
in the namespace 'MM'." This is the code Dreamweaver generates for
me to insert the XSL fragment:
<%
Dim mm_xsl As MM.XSLTransform = new MM.XSLTransform()
mm_xsl.setXML("
http://webcentral.uc.edu/eprof/cfc/fetcheprofdata.cfc?method=getGroupMembersByName&groupna me=eprof.All.WestCampus.AS.BioSciences")
mm_xsl.setXSL(Server.MapPath("byDeptMembers.xsl"))
Response.write(mm_xsl.Transform())
%>
I'm a designer, not a developer, so please reply using
language I might be able to understand or pass along to our server
admin.
Thanks in advance,
Micah

I just solved the problem!! In fact, you guided me to the solution.
I opened the reference list and deleted all un-necessary references to Microsoft.Office.Interop.Excel and kept just Microsoft Excel 12.0 Object library. The problem gone.
The value of Microsoft.Office.Interop.Excel was 11.0, (if this is what you was asking for).
It was my fault, I did not know how to reach the reference list!!
Thanks all for your replies indeed.
Kind Regards
God help the rich man, let the poor man beg!
Aha! It seemed the only reasonable explanation -- just a matter of ironing out the symantecs.

Similar Messages

Repository Namespaces in XI 3.0

Hi people!
For the original setup of XI we are looking at how to set up the namespaces within the SWCV.
On the forum people say it is wise to setup a new namespace for each interface. In the demo examples that are delivered in the XI content this approach is not chosen. It looks like they use 'party' as a reason for a new namespace.
In the examples in the book 'SAP Exchange Infrastucture' it looks like they use a different namespace for each interfaceprocess.
What is your experience on this?
What are the advantages and disadvantages of the different approaches?
thanks a lot for your help!

Hi Alexander,
In our project we have chosen for a generic solution in which SWCV's names are based on Business Processes and all contained within one single product.
Namespaces in these SWC's are created based on the "type" of interface they represent i.e. a combination of sender/receiver party and message type. This last identifier in the namespace has been introduced in order to minimize the risks of having ambiguous namespaces.
This approach supports modularity in your SWC and also provides a flexible way to independently deploy interfaces. Last but not least; by using this approach you can clearly manage how you share/reuse objects from the different namespaces within one SWC.
Hope you have now a better picture of how to carry on with your namespaces.
Cheers,
Rob.

'CrystalReportViewer' is ambiguous in the namespace 'CrystalDecisions.Web'

I had to close my previous thread about this subject. I think I screwed something up with my last post. I tried to post code from my .aspx and now I can only see 4 of the 10 replies.
I have updated from CR 10 to CR 2008 SP3.
I only have on crystalreportviewer on one of my aspx pages.
Using VS 2008, CR 2008 SP 3, Framework 2.0 and asp.net 2.0
I have a link button one one of my .aspx pages that opens the .aspx page with the crystalreportviewer passing it the report name.
I tried deleting all references to CR, re-adding them and dropping a new viewer onto the page. Still get the error. I get the error on the production server, works fine on my local machine and the dev machine. The production server has CR 10 and CR 2008 installed on it. Have to have the older version because of older sites that have older reports and use it.
help me please!
Sorry for the re-threading.

See what [Modules|https://smpdl.sap-ag.de/~sapidp/012002523100006252802008E/modules.zip] tells you re. files being loaded on a box that works and one that does not work. Modules will compare the two outputs for you (Modules menu then select Differences).
Ludek

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.

About "using namespace std" and tool.h++

Hi,
I am a new starter working on some old code C++ using tools.h++ which was previous compiled under the 4.2 version. After reading early topics in this forum, I know that I can use in the new workshop 6 compiler by compiler options like "-library=rwtools7, iostream" to enable usage of both standard iostreams and classic iostreams, however I have problem with "using namespace std", which is plenty in original codes, even the following simple code won't pass: CC -library=rwtools7,iostream test1.cc
File: test1.cc
using namespace std;
#include <rw/rwstring.h>
#include <iostream>
#include <string>
int main()
RWCString s1("hello");
string s2("world");
cout<<s1<<s2<<endl;
return 0;
error code is :
Error :the name cout is ambiguous, cout and std::cout
Error: The operation "ostream << std::basic_string<char, std::char_traits<char>, std::allocator<char>>" is illegal
but if I marked "using namespace std" and replace cout with std::cout, everything works fine.
Thanks for the time.
PS: when I use -library=rwtools7_std, a CC warning of illegal option -library=rwtools7_std ignored, am I missing something in the system?

The C++ Standard Library, which you access by using headers such as <iostream> and <string>, does not mix well with classic iostreams.
One problem is that classic iostreams has identifiers that are the same as identifiers in standard iostreams, but in different namespaces. If you add
using namespace std;
to your code, you create conflicts among the names.
In general, "using namespace std;" is a Bad Idea in real applications. The standard library has so many names that you are likely to run into conflicts with names declared elsewhere. You can add individual using-declarations for types that you need, or qualify them explicitly.
#include <string>
#include <list>
using std::string;
std::list<string> ListOfString;
When mixing classic iostreams with the standard library, you cannot have any using-declaration or using-definition associated with names from either iostream library -- the names will conflict.
If you want to use the standard library with Tools.h++, we recommend not using classic iostreams at all. Use the option
-library=rwtools7_std
to get a version of Tools.h++ that works with the standard library.
Most simple iostream code works with both classic and standard iostreams, so this technique is worth a try. With luck, either you won't have to modify your source code at all, or the needed changes will be simple.
You mention you are using the "new WorkShop 6" compiler. Workshop 6 is over 5 years old, and was long ago declared End Of Life. No support is available for it. Maybe you mean WorkShop 6 update 2, which was released in 2001, and which has just been declared End Of Life. WS6u2 is the earliest version that supports the -library=rwtools7_std option.
In any case, you should look into upating to a current compiler.
http://www.sun.com/software/products/studio/index.xml
The current release is Sun Studio 10, listed here. But Sun Studio 11 will be released in two weeks. Watch that space (and this forum) for an announcement.
The C++ MIgration Guide that comes with the compiler explains every issue you can run into when porting code from C++ 4.2 to C++ 5.x in standard mode. It also shows you how to modify code when necessary to get the proper result.

GPIB class device is ambiguous

Hello,
I am using Visual Basic.Net to program a PXI system and trying to talk to GPIB instruments using the code, but when I dimension the variable as the Class Device, which contains the IEEE-4882 functionality, I get an error. The statement, taken from one of the .NET examples, reads "Private GPIB Device as Device". The error reads - 'Device' is ambiguous, imported from the namespaces or types 'NationalInstruments.NI4882, NationalInstruments.DAQmx'.
If I remove the DAQmx information (Imports NationalInstruments.DAQmx), then the error goes away. Also, it seems I can communicate with my GPIB instruments when I go into MAX under the GPIB information. I can query the instruments under "Communicate with Instruments" and they return the proper information.
Is there something that I am missing? Any help would be appreciated.
Thanks,
Mike

Hi Mike,
It seems that both DAQmx and NI 488.2 define something as a device, and they don't agree on that definition. The best practice would probably be to have sepearte assemblies run the DAQmx and NI 488.2 code segments, and avoid having the conflict that way. If there is a particulare reason that you need to have the code segment in the same assembly I am fairly certain if you explicity define the class path by placing.
Global.NationalInstruments.NI4882.Device
Instead of just device that you should be able to run the code. I would recommend just removing Imports NationalInstruments.DAQmx and implementing it in a seperate piece of code. Let me know if this is still causing trouble.
Have a great day,
Michael D
Applications Engineering
National Instruments

Exchange 2010 ambiguous URL'S issue while coexist with exchange 2013

Hi ,
Please correct me if i am wrong and also all of you tell me your valuable suggestions.
Like as said in the below article we are having an exchange 2010 ambiguous url's in place.
Referred
article :
http://blogs.technet.com/b/exchange/archive/2013/05/23/ambiguous-urls-and-their-effect-on-exchange-2010-to-exchange-2013-migrations.aspx
As said in this article, if we have exchange 2010 ambiguous url's in place we will face issues during exchange 2013 coexistence.I agree with that point .
Question : On such case why don't we use a separate namespace for internal and external outlook anywhere settings in exchange 2013 which is different from cas array name and also there is no need to disturb the existing exchange 2010
environment by changing the rpc client access attribute in exchange 2010 databases or by forcing the exchange 2010 internal outlook clients to connect via OA. Please clarify my doubt and say whether the mentioned scenario is possible or not ?
Note : Same time please consider the new namespace which is going to be utilized on exchange 2013 outlook anywhere settings is available on SAN certificate.
Regards
S.Nithyanandham

Hi ,
Please someone shed light on this case.
Regards
S.Nithyanandham
Thanks & Regards S.Nithyanandham

Overloading ambiguity errors

Any suggestions on how to resolve the error below?
"/opt/SUNWspro/current-compiler/include/CC/Cstd/./vector", line 1131: Error: Overloading ambiguity between
"std::distance<std::vector<bool, std::allocator<bool>>::const_iterator, unsigned>(std::vector<bool,
std::allocator<bool>>::const_iterator, std::vector<bool, std::allocator<bool>>::const_iterator, unsigned&)"
and "distance<std::vector<bool, std::allocator<bool>>::const_iterator, unsigned>(std::vector<bool,
std::allocator<bool>>::const_iterator, std::vector<bool, std::allocator<bool>>::const_iterator, unsigned&)".
Sometimes the subsequent "Where: While instantiating ...." helps locate the ambiguity.
(None in this case. ) If this error were coming from user code, specifying '::' or 'std::' helps.
But when it is in one of the CC include files, is there a recommended approach?
Any input is appreciated.
% CC -V
CC: Sun WorkShop 6 update 1 C++ 5.2 2000/09/11
Thanks.

If you have copied the error message correctly, it appears you have declared your own "distance"function template outside namespace std, which is causing the ambiguity.
If you haven't done that, you might have run into a compiler bug. C++ 5.2 is obsolete and is no longer supported, but you can download the most recent patches for it here
http://wwws.sun.com/software/products/studio/patches/index.html
and see if that fixes the problem. (In your case, select the link for Forte Developer 6 update 1. The most recent patches are from about 2002.)
If patches don't help, see if you can post a small compilable code sample that shows the problem.

Ambiguous reference to Main

I built a custom control based off Canvas, when I try to drop it into my Main.mxml code I get this cryptic error:
Ambiguous reference to Main. [Generated code (use -keep to save): Path: Main-generated.as, Line: 1110, Column: 10]
I’ve googled the error and everything on it seems to suggest that it is caused when you have two functions with the same name in the same namespace and Flex doesn’t know which one you mean, but I’ve renamed all my variables/functions in the custom class to really cryptic names to eliminate this possibility. I've also seen this error reported for classes that have properties with different access modifiers on their getter vs. setter but all my gets/sets are public. This is really driving me crazy, any help appreciated

Can you post any of your code? Or any of the generated code?

The name "Folder" does not exist in the namespace

I am trying to learn Wpf and doing some of the examples on the Microsoft site. https://msdn.microsoft.com/en-us/library/vstudio/bb546972(v=vs.110).aspx?cs-save-lang=1&cs-lang=vb#code-snippet-1
I am using Visual studio 2013. As I work through the example I am getting the following error.
Error 1
The name "Folder" does not exist in the namespace "clr-namespace:FolderExplorer".
c:\users\hbrown\documents\visual studio 2013\Projects\FolderExplorer\FolderExplorer\MainWindow.xaml
11 17
FolderExplorer
Error 2
The name "Folder" does not exist in the namespace "clr-namespace:FolderExplorer".
c:\users\hbrown\documents\visual studio 2013\Projects\FolderExplorer\FolderExplorer\MainWindow.xaml
16 7
FolderExplorer
Here is the code:
<Window x:Class="MainWindow"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:my="clr-namespace:FolderExplorer"
Title="Folder Explorer" Height="350" Width="525">
<Window.Resources>
<ObjectDataProvider x:Key="RootFolderDataProvider" >
<ObjectDataProvider.ObjectInstance>
<my:Folder FullPath="C:\"/>
</ObjectDataProvider.ObjectInstance>
</ObjectDataProvider>
<HierarchicalDataTemplate
DataType = "{x:Type my:Folder}"
ItemsSource = "{Binding Path=SubFolders}">
<TextBlock Text="{Binding Path=Name}" />
</HierarchicalDataTemplate>
</Window.Resources>
I have a class file named Folder.vb with this code.
Public Class Folder
Private _folder As DirectoryInfo
Private _subFolders As ObservableCollection(Of Folder)
Private _files As ObservableCollection(Of FileInfo)
Public Sub New()
Me.FullPath = "c:\"
End Sub 'New
Public ReadOnly Property Name() As String
Get
Return Me._folder.Name
End Get
End Property
Public Property FullPath() As String
Get
Return Me._folder.FullName
End Get
Set(value As String)
If Directory.Exists(value) Then
Me._folder = New DirectoryInfo(value)
Else
Throw New ArgumentException("must exist", "fullPath")
End If
End Set
End Property
ReadOnly Property Files() As ObservableCollection(Of FileInfo)
Get
If Me._files Is Nothing Then
Me._files = New ObservableCollection(Of FileInfo)
Dim fi As FileInfo() = Me._folder.GetFiles()
Dim i As Integer
For i = 0 To fi.Length - 1
Me._files.Add(fi(i))
Next i
End If
Return Me._files
End Get
End Property
ReadOnly Property SubFolders() As ObservableCollection(Of Folder)
Get
If Me._subFolders Is Nothing Then
Try
Me._subFolders = New ObservableCollection(Of Folder)
Dim di As DirectoryInfo() = Me._folder.GetDirectories()
Dim i As Integer
For i = 0 To di.Length - 1
Dim newFolder As New Folder()
newFolder.FullPath = di(i).FullName
Me._subFolders.Add(newFolder)
Next i
Catch ex As Exception
System.Diagnostics.Trace.WriteLine(ex.Message)
End Try
End If
Return Me._subFolders
End Get
End Property
End Class
Can someone explain what is happening.
Thanks Hal

Did you try to build the application (Project->Build in Visual Studio) ? If the error doesn't go away then and you have no other compilation errors (if you do you need to fix these first), you should replace "FolderExplorer" with the namespace
in which the Folder class resides. If you haven't explicitly declared a namespace, you will find the name of the default namespace under Project->Properties->Root namespace. Copy the value from this text box to your XAML:
xmlns:my="clr-namespace:FolderExplorer"
The default namespace is usually the same as the name of the application by default so if your application is called "FolderExplorer" you should be able to build it.
If you cannot make it work then please upload a reproducable sample of your issue to OneDrive and post the link to it here for further help.
Please remember to close your threads by marking helpful posts as answer and then start a new thread if you have a new question.

How to Get Portlet Namespace in a JSP attribute

Hi All,
The id of any component in a JSF application (with JSR168 portlets) takes the form
'view'+'<portlet:namespace/>'+':'+'formname:componentidname';
I need this id to be used for certain validations.
Currently I am using it as below :-
<h:intputText required="#{ ! empty param['viewns_7_CGAH47L000NAF0I04I42ND10P7_:form:login']}"/>
Presently I have hardcoded the portlet namespace 'ns_7_CGAH47L000NAF0I04I42ND10P7_' by looking into the html source of the rendered page.
Is there any way by which i can automatically get this portlet namespace within the param tag in the jsp.
I know for a fact that within javascript tags, it can be used as <portlet:namespace/> as shown below :-
<script type="text/javascript">
function doSomething()
buttonId= 'view' + '<portlet:namespace/>'+':'+'formName:buttonId';
document.getElementById(buttonId).disabled = true;
</script>
Kindly treat this on high priority.
Thanks and Regards,
Darshan Shroff

Perhaps so.
I need to use it within param as below
<h:inputText value="#{bean.userid}"
required="#{!empty param['viewns_7_CGAH47L00GLRE0I0BCOUKS00I5_:form:login']}" />
Here 'viewns_7_CGAH47L00GLRE0I0BCOUKS00I5_:form:login' is actually
'view' + '<portlet:namespace/>'+':'+'formName:buttonId';
I am just trying to check the presence of the client ID in the request paramameter map inorder to attain action dependent requiredness.
Kindly tell me how i could access it within param.
Thanks & Regards,
Darshan Shroff

Message no. SG028 Ambiguous... exchange rate relation

Hi Friends,
I have a free of charge order. While doing the Post Goods Issue step, I am getting the following error message
Ambiguous EUR/USD exchange rate relations
Message no. SG028
I have searched in the forum and made sure that in transaction OB08 Exchange Rate EUR/US and USD/EUR (Exchange Rate Type M) has maintained properly in the system.
I have also made sure that the entries are properly maintained in SPRO - General Settings - Currencies - Define Translation Ratios for Currency Translation.
But still the error is coming, I saw in one thread, some one has reported the same problem even after maintaining the exchange rates in OB08, but no solution was suggested as far as I check. could anyone please give some inputs why the same error coming even though the exchange rates are maintained and how to fix this issue as I stuck in Post Goods Issue step
Thank you

Hi Christian,
Thanks for your time.
I've found the below entries in OBBS
M   USD    EUR     01.01.1900        100 : 1
M   EUR    USD     01.01.1900         1    : 100
Alternative currency is blank in both entries
In OB07 for exchange rate Type M all the fields (Ref. currency, Buy and Sell rate) and the check boxes are blank. it is still unclear for me being a logistics guy
While doing Post Goods Issue in other scenario I didnt have any error where currency GBP EUR invovled. In this case the OBBS entries EUR/GBP as below
M   GBP    EUR     01.01.2000        1 : 1
M   EUR    GBP     01.01.2000        1 : 1
Alaternative currency is blank in this case as well.
Does the valid from date or the ratio make any difference?
I could not clarify with my FI consultant as he is on vacation. Could you please let me know how to fix it.
Thank you

Adding Namespace in Sender File Adapter Scenario.

Hi All
I have a scenario where XI has to Pick Up XML a file and process it. The structure of the file is as follows
<?xml version="1.0" encoding="UTF-8" ?>
<Header>
     <Seg1>
     </Seg1>
</Header>
This file does not contain any any namespace tag. I guess XI would not be able to pick up this file if there is no namespace in the XML file . The file expected by XI would be something like this.
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:MessageTypeName xmlns:ns0="...namespace...">
<Header>
     <Seg1>
     </Seg1>
</Header>
</ns0:MessageTypeName>
Is there a way this can be handled at the File Sender adapter side . I am aware about adding adapter module. Is there any other way to add the missing two namespace tags at the top and bottom of the file .
any help would be appreciated.
regards
Nilesh .
Edited by: Nilesh Taunk on Apr 7, 2008 2:11 PM

Hi Nilesh,
Yes it is possible in File sender adapter to give the namespace. In FCC you can give inside Document Specification.
Under Document Name, enter the name of the XML document.
The document name is inserted in the message as the main XML tag. This is mandatory for the mapping.
Under Document Namespace, enter the namespace of the document.
The namespace is added to the name of the document. This is mandatory for the mapping
I hope this will help you.
Regards
Aashish Sinha

J2SE adapter PI 7.1 issue with XML to flat conversion and namespace length

Dear reader,
We are facing an issue with J2SE Adapter PI7.1 for a number of flows.
The flow requirements:
[1] Namespace length for interfaces is up to 100 characters
[2] The XML message must be converted to Flat on the adapter channel
Our PI system is at patch level 7 and we implement J2SE adapter on patch level 7 as well.
We found that the J2SE adapter on patch level 7 does not support long namespaces [1] (as it should since this is an PI 7.1 j2SE adapter) but no issues where found with the XML to flat conversion [2].
Experimenting with J2SE adapter on patch level 6 we found the long namespaces [1] are supported however an issue is found with the XML to flat conversion [2] as stated in SAP note 1335527.
An SAP Customer Message is raised on this issue however your input is highly appricated!
With Kind Regards,
Harald Kastelijn
Edited by: Harald Kastelijn on Mar 6, 2010 9:17 AM
Edited by: Harald Kastelijn on Mar 6, 2010 9:19 AM

We found that the J2SE adapter on patch level 7 does not support long namespaces [1] (as it should since this is an PI 7.1
j2SE adapter) but no issues where found with the XML to flat conversion [2]
I think the restriction of namespace length still remains in design time (IR).....the same however has been extended in configuration and runtime...this SAP note has some information: https://service.sap.com/sap/support/notes/870809

How to take back up of my XI scenraios ( namespaces and Objects )

Hi
I have done some scenarios on XI sytem which has been crashed. Present it is not working . J2ee Engine is not starting.
Now we have installed new XI system. I want to take backup of my old scenarios and i need to import it into new XI system. How to take backup from old XI system which is not working now and import it into new one.
Could you please help me.....
Regards
- Ravi Shankar B

Hi,
You could not able to recover the data from crashed system i.e old XI system.
For that now you have to develop all as new one in the current new XI system.
But whatever development that you will be doing that you could create backup.
I.e follow below steps..
1. After development and testing select the software component and right click on it --> Export or Tools -->Export Design Objects.
2. select transport as file system, for CMS again it will go on Java Engine that will be not as backup and give the name of file.
2. Select the namespaces or individual object to be taken as backup.
3. Process it and finish the wizard.
4. This will lead you to download it to local PC that you could keep it as backup
For Importing goto
Tools---> Import design object.
Similarly you can export and import Integration directory objects also
thanks
Swarup

Ambiguous Namespace

Similar Messages

Maybe you are looking for