Defining Additional DC Namespace Prefixes

Hi,
I've created a SC via SLD and I've defined a Namespace Prefix for DC Category(comany.com/apps/*). When I imported Development Configuration and tried to create a DC, it creates normally.
Now, I want to add a new DC Namespace Prefix so I want to choose it also. (comany.com/portal/*)
Although I've added the prefix, I deleted and reimported Dev.Conf. I cannot see it, Why?

Yes
All changes made in the SLD are visible to the CMS and NWDS GUI only after you have performed a "Update CMS", from the Domain Data tab in the Landscape configurator.

Similar Messages

XML Namespace Prefix required

Hello,
our partner uses Biztalk to receive our SOAP calls. They tell us that each attribute and element needs to have the namespace prefix otherwise Biztalk cannot read it.
We are sending:
SAP XI Output
<?xml version="1.0" encoding="utf-8" ?>
<ns11:Receive_SAP xmlns:ns11="http://zzz.com/it/mmpur/sem/xi">
<part>
 <xform id="SWI:PLG:Order Header - SAP">
 <model>A</model>
 </xform>
</part>
</ns11:Receive_SAP>
They want:
Biztalk Requirement:
<?xml version="1.0" encoding="utf-8" ?>
<ns11:Receive_SAP xmlns:ns11="http://zzz.com/it/mmpur/sem/xi">
<ns11:part>
 <ns11:xform id="SWI:PLG:Order Header - SAP">
 <ns11:model>A</ns11:model>
 </ns11:xform>
</ns11:part>
</ns11:Receive_SAP>
Can that be done with the XI 3.0 Graphical mapping or do I have to use JAVA Mapping or XSLT?
Did anyone come accros this before with Biztalk Server and it there an option to avoid it on the Biztalk Server side?
Thanks
Stefan

Hi Stefan,
Where did you obtain the schema (XSD) from?
Most likely, the elements you are using are local elements and do not belong to the target namespace, but to an unnamed global namespace. This is a typical characteristic of schema's defined by SAP.
The short answer/solution is probably putting elementFormDefault="true" in the header of your target schema. That should do the trick.
Kind regards, Guy Crets

Java Mapping to override namespace prefix (startPrefixMapping)

Does anyone have an example of using a Java Map to override the default XI namespace prefix. The method startPrefixMapping looks like it might do the job but I can't find any example of how this works.

You can use the Anonymizer Module Processor.
In your adapter, go to the "Modules" tab, than insert a new entry before the default adapter module processor. Enter module name localejbs/AF_Modules/XMLAnonymizerBean and Local Enterprise Bean type. In the parameters tab, enter parameter anonymizer.acceptNamespaces and parameter value '<namespace>' <prefix>. You can enter more than one namespace, like in '<namespace1>' <prefix1> '<namespace2>' <prefix2>.
Note that your namespace must be inside apostrophes by default. If instead you want to use quotes to define the namespace, you must use another parameter before the one above: parameter name anonymizer.quote and in the value enter a single quote ".
To define an empty prefix (meaning, that namespace is the default namespace) use '' (two apostrophes) instead of <prefix> (or "" (two quotes), if you have used anonymizer.quote).
Check SAP Note 880173 for more information.
Regards,
Henrique.

XML Namespace Prefix Lost

I am working on a RFC to JMS scenario and am having trouble getting the XML in the required format. I have loaded the XML file provided in my mapping. However the result was not what I had anticipated.
 
This is the XML provided and what I want to produce:
 
<
?xml version="1.0" encoding="UTF-8" ?> 
<MyNS3:Maint_Struc 
 xmlns:MyNS1="http://www.MyTest.com/My_Namespace/Part1" 
 xmlns:MyNS2="http://www.MyTest.com/My_Namespace/Part2" 
 xmlns:MyNS5="http://www.MyTest.com/My_Namespace/Part5" 
 xmlns:MyNS3="http://www.MyTest.com/My_Namespace/Part3" 
 xmlns:MyNS4="http://www.MyTest.com/My_Namespace/Part4" 
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
 xsi:schemaLocation="www.MyTest.com/My_Namespace/Part3 file:/C:/MyStructure.xsd">
 
 <
 MyNS2:SubStruc_1> 
 <
 MyNS2:Fld_1_1_A>Value001<
 /MyNS2:Fld_1_1_A> 
 <
 MyNS2:Fld_1_1_B>Value002<
 /MyNS2:Fld_1_1_B> 
 <
 /MyNS2:SubStruc_1> 
 
 <
 MyNS3:SubStruc_2> 
 <
 MyNS1:SubStruc_2_1> 
 <
 MyNS1:Fld_2_1_A>Value003<
 /MyNS1:Fld_2_1_A> 
 <
 MyNS1:Fld_2_1_B>Value004<
/MyNS1:Fld_2_1_B> 
 <
/MyNS1:SubStruc_2_1> 
 <
MyNS4:Fld_2_A>Value005<
/MyNS4:Fld_2_A> 
 <
MyNS4:Fld_2_B>Value006<
/MyNS4:Fld_2_B> 
 <
/MyNS3:SubStruc_2> 
 
 <
MyNS3:SubStruc_3> 
 <
MyNS5:SubStruc_3_1> 
 <
MyNS5:Fld_3_1_A>Value007<
/MyNS5:Fld_3_1_A> 
 <
MyNS5:Fld_3_1_B>Value008<
/MyNS5:Fld_3_1_B> 
 <
/MyNS5:SubStruc_3_1> 
 <
MyNS3:Fld_3_A>Value009<
/MyNS3:Fld_3_A> 
 <
MyNS5:Fld_3_B>Value010<
/MyNS5:Fld_3_B> 
 <
MyNS2:Fld_3_C>Value011<
/MyNS2:Fld_3_C> 
 <
/MyNS3:SubStruc_3> 
<
/MyNS3:Maint_Struc> 
 
However I am getting the following when mapped: 
<
?xml version="1.0" encoding="UTF-8"?> 
<
ns0:Maint_Struc 
 xmlns:MyNS4="http://www.MyTest.com/My_Namespace/Part4" 
 xmlns:MyNS5="http://www.MyTest.com/My_Namespace/Part5" 
 xmlns:MyNS2="http://www.MyTest.com/My_Namespace/Part2" 
 xmlns:MyNS1="http://www.MyTest.com/My_Namespace/Part1" 
 xmlns:ns0="http://www.MyTest.com/My_Namespace/Part3" 
 xmlns:ns1="http://www.w3.org/2001/XMLSchema-instance" 
 ns1:schemaLocation="www.MyTest.com/My_Namespace/Part3 file:/C:/MyStructure.xsd"> 
 <
ns2:SubStruc_1 xmlns:ns2="http://www.MyTest.com/My_Namespace/Part2"> 
 <
ns2:Fld_1_1_A>Value001<
/ns2:Fld_1_1_A> 
 <
ns2:Fld_1_1_B>Value002<
/ns2:Fld_1_1_B> 
 <
/ns2:SubStruc_1> 
 
 <
ns0:SubStruc_2> 
 <
ns3:SubStruc_2_1 xmlns:ns3="http://www.MyTest.com/My_Namespace/Part1"> 
 <
ns3:Fld_2_1_A>Value003<
/ns3:Fld_2_1_A> 
 <
ns3:Fld_2_1_B>Value004<
/ns3:Fld_2_1_B> 
 <
/ns3:SubStruc_2_1> 
 <
ns4:Fld_2_A xmlns:ns4="http://www.MyTest.com/My_Namespace/Part4">Value005<
/ns4:Fld_2_A> 
 <
ns4:Fld_2_B xmlns:ns4="http://www.MyTest.com/My_Namespace/Part4">Value006<
/ns4:Fld_2_B> 
 <
/ns0:SubStruc_2> 
 
 <
ns0:SubStruc_3> 
 <
ns5:SubStruc_3_1 xmlns:ns5="http://www.MyTest.com/My_Namespace/Part5"> 
 <
ns5:Fld_3_1_A>Value007<
/ns5:Fld_3_1_A> 
 <
ns5:Fld_3_1_B>Value008<
/ns5:Fld_3_1_B> 
 <
/ns5:SubStruc_3_1> 
 <
ns0:Fld_3_A>Value009<
/ns0:Fld_3_A> 
 <
ns5:Fld_3_B xmlns:ns5="http://www.MyTest.com/My_Namespace/Part5">Value010<
/ns5:Fld_3_B> 
 <
ns2:Fld_3_C xmlns:ns2="http://www.MyTest.com/My_Namespace/Part2">Value011<
/ns2:Fld_3_C> 
 <
/ns0:SubStruc_3> 
<
/ns0:Maint_Struc> 
 
Things that are wrong with the mapped XML: 
- the namespace "http://www.MyTest.com/My_Namespace/Part3" was prefixed with MyNS3 but XI reassigned it to ns0
 - original prefixes are not used in the element tags 
 
Appreciate if anyone can help. 
Thanks.

Thank you for all your valuable suggestions. Does any know why XI/PI does not acknowledge/use the namespace prefix that is defined in the XML? Is there no other way around this short-coming apart from using XSLT mapping?
 
I did try using the anonymizer (as suggested by Manjusha). With the anonymizer I am able to change the namespace prefix in the element tags to the way I want it. However the namespace definition is still showing in the element tag.
 
 <MyNS2:SubStruc_1 xmlns:MyNS2="http://www.MyTest.com/My_Namespace/Part2"> 
 <MyNS2:Fld_1_1_A>Value001</MyNS2:Fld_1_1_A> 
 <MyNS2:Fld_1_1_B>Value002</MyNS2:Fld_1_1_B> 
 </MyNS2:SubStruc_1> 
 
This is almost perfect only if I am able to remove the definition xmlns:MyNS2="http://www.MyTest.com/My_Namespace/Part2" from the element tag. Suggestion any one?
Thanks All.

Controlling Namespace Prefix in OSB10gR3

Hi,
I am doing a xquery transformation in my application, where I have defined a few namespaces with prefixes, but the prefixes get changed in my output. Is there anyway I can control the namespace prefixes.
Thanks,
Balaji.

Hi Balaji,
Have you defined those namespaces in OSB configuration with same prefix? If no, please do so, it should work.
Few alternate approaches are mentioned here -
Re: Namespace replace/rename issue in ALSB
Regards,
Anuj

Ld namespace prefix in data service files

Mike,
Strange question. As you know typically when importing a schema the import will look something like this:
import schema namespace ns="http://www.test.com/test/1/" at "ld:schemas/SomeSchemaFile_1_0.xsd";
The namespace prefix in the URI "ld", I know you need that because it tells the data service that the file is local to the data service project. My question is it possible to import schema files in an external project outside the data space project? Also where is the ld prefix defined?
The only way I was able to import a schema file was using an absolute path from my hard drive...this would not be a good thing to do.
Mike

It would be embarrassing for me to tell you it is possible, and then three minutes later you post saying that you tried it and it isn't. So try it first and then let us all know.Yes, it would be embarrassing! Of coarse I tried, but according to the xquery spec when defining schema import they must be absolute paths, so I wasn't sure if there was an ODSI implementation specific mechanism for declaring other types of paths...like the ld namespace prefix, but a custom one.
>
import schema namespace ns="http://www.test.com/test/1/" at "ld:schemas/SomeSchemaFile_1_0.xsd";
Also where is the ld prefix defined?I believe the string following the "at" in an import statement in xquery is "implementation dependent" (you can check the spec). The 'protocol' ld is just something ODSI uses to indicate that schema will be self-contained in the dataspace. I'm guessing that the protocols http and file will also work - you can try that to answer the first part of your question. I believe if you have an update function, you'll find you that datagraph.xsd is accessed via http.
- MikeI haven't tried but I am willing to bet the http path will work because that is an acceptable path based on the xquery spec. I am thinking to get what I want to happen, I could write a small ant task to copy the schemas from the external project to the data space when building. As always thanks for the quick reply!
Mike

Namespace prefix in SOAP Elements causes problems in XI

Hi guys,
I'm using code generated by NW Developer Studio for use inside Portal components acting as a web service consumer. The problem is that the code generated includes a namespace prefix for each element in the body of the message, but XI doesn't like the namespace prefixes and throws back a DeliveryException.
The SOAP message created by the generated NWDS code is:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wn3="http://www.w3.org/1999/XMLSchema" xmlns:wn2="http://www.w3.org/2000/10/XMLSchema" xmlns:wn1="http://www.w3.org/2001/XMLSchema" xmlns:wn0="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wn4="http://allieddomecq.com/poc" xmlns:tns="http://allieddomecq.com/poc">
 <SOAP-ENV:Body>
 <wn4:PortalSOAP_MT_Request>
 <wn4:CustomerIdentifier>0001000064</wn4:CustomerIdentifier>
 <wn4:SalesOrganization>ES50</wn4:SalesOrganization>
 <wn4:SystemIdentifier>R3D</wn4:SystemIdentifier>
 </wn4:PortalSOAP_MT_Request>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
The problem is the "wn4" prefixes on the CustomerIdentifier, SalesOrganization, and SystemIdentifier tags. When we send the soap request from XML Spy without the prefixes, the response comes back OK with the expected data.
I've had a very good look around the generated code - the serializers for creating the soap request - but could not find what exactly might be changed to leave off the prefixes.
Alternatively, is there something I could ask our XI consultant to do, to make his component accept the request with the redundant prefixes in the tags?
Many thanks for any advice/help,
Laura

Hi Laura,
you have to realize that the two documents
<ns:CustomerRecord xmlns:ns="http://company.com">
<ns:CustomerNumber> </ns:CustomerNumber>
<ns:CustomerDetails> </ns:CustomerDetails>
</ns:CustomerRecord>
and
<ns:CustomerRecord xmlns:ns="http://company.com">
<CustomerNumber> </CustomerNumber>
<CustomerDetails> </CustomerDetails>
</ns:CustomerRecord>
from an XMl point of view have totally fifferent structure. Thus, a mapping which is able to deal with the first structure will fail for the second and vice versa.
Surely, both structures somehow can carry the same information, but they do this with different languages (Maybe you can compare this to the fact, that you may deliver the same information in English or in German language).
When you model the structure in Integration Repository using datatypes and message types (what I think you did), you will always get a structure that looks like the second one. This is just a convention (like the convention that all information in this forum should be presented in English). When defining a message mapping for this structure it also relies on this fact and thus will not understand the other kind of document.
External Definitions are more flexible. They are also able to understand structures that are modelled the other way. This greater flexibility is due to the fact that External Definitions were designed to understand structures that come from an external world where different conventionts might be used.
To come to a conclusion: If the structure you have to deal with has been defined externally then it is not intended that you model it inside the Integration Builder using datatypes and message types. In this case the external source should provide a description of the message as XSD, WSDL, or DTD. You upload this as External Definition, and everything works fine.
If you have designed the structure yourself, you can model it with datatypes and message types. But then you will always get a structure which looks like the second one. In this case you should make sure that all other participants in the game also stick to that structure. Then everything will be fine, too.
Greetings Stephan

Removing namespace prefixes

I am familiar with the XmlOptions.setUseDefaultNamespace() to remove the namespace prefixes on the XML generated by my XMLBean. However, how do I specify which namespace prefix should be removed (if my XMLBean contains multiple namespace prefixes)? The docs for XmlOptions specify:
"If this option is set, the saver will try to use the default namespace for the most commonly used URI. If it is not set the saver will always created named prefixes."
Doing some testing, I have found that sometimes the correct namespace is being set as the default namespace. If my original document is:
<ns1:a ...>
<ns1:b ...>foo
<ns2:c ...>bar</c>
</a>
if I use the xmlText(XmlOptions) method then I sometimes get back:
<a ...>
foo
<ns2:c ...>bar</c>
</a>
and sometimes get:
<ns1:a ...>
<ns1:b ...>foo
<c ...>bar</c>
</a>
Any thoughts?

Hello,
I'm using xmlbeans in my project. I'm constructing xml using the xmlbeans
generated sources from the XML Schema files. The server to which I'm
sending the request doesn't recognize the namespace URI's or the prefixes.
so, once the XML document is constructed, I'm trying to strip of the
namespace URI's and prefixes using the below code and couldn't get it to
work.
Map m=
new HashMap();
m.put(
http://www.abc.com/schemas/myproj/avail/2008/01, "");
m.put(
http://www.abc.com/schemas/myproj/common/2008/01,"";);
opts.setLoadSubstituteNamespaces(m);
opts.setUseDefaultNamespace();
SampleRQDocument propAvailRQDoc = SampleRQDocument.Factory.*newInstance*
(opts);
The schemas are defined under 3 different namespaces.
How can I remove the Namespace URI's and Prefixes after I construct the XML
document?
Next thing, when the server sends the response, the response doesn't include
any Namespace URI or the prefixes. How can I embed the URI's and Prefixes in
the response document after I receive it so, I can use XML Beans
to bind the XML to the generated sources.
I searched on google but couldn't find a suitable solution.
Any help in this regard is greatly appreciated.
Thanks,
Sridhar.

Mapping Question p3: .. etc.. namespace prefixes

Does anyone know why xi uses namespace prefixes like p3: p2: etc..? I am trying to map based on an rfc as the target and a message from a wsdl as the source. I can not test the map because it expects the test file ( from our partner ) to have all these P3:'s in it and it doesn't. Here is a snippet of what is happening at translation ....
<p3:Execute2 xmlns:p3="http://www.some/namespace/">
<p3:transaction-limit type="Amount"><p3:value>99999999999</p3:value></p3:transaction-limit><p3:transaction-limit type="Number"><p3:value> 9999</p3:value></p3:transaction-limit></p3:daily-transaction-limits><p3:single-transaction-limits></p3:single-transaction-limits><p3:monthly-transaction-limits></p3:monthly-transaction-limits></p3:authorization-control><p3:request-type>Activate</p3:request-type>
Message was edited by: Andrew Alpaugh

Hi Andrew,
the question is a little bit unclear to me. When I get you right, you have a WSDL that describes a message you get from a partner. You use this WSDL to define a Message Mapping. The Message Mapping does not work as expected. The fragment you have posted is probably what the Message Mapping seems to expect (according to the test panel). But the message you get from your partner looks different (it does not have all these prefixes).
I suppose that the schema contained in the WSDL (more precisely in the types-section) states that all elements have to be namespace-qualified (this could e.g. be done by having an elementFormDefault="qualified" in the schema). Thus, if the elements are unqualified in the message you get from your partner it simply means that the partner does not stick to the WSDL.
If this does not help you, I would have to see the WSDL and an example message that failed to work.
Note, however that there are different ways to express namespaces. If the document sent by your partner looks as follows:
<Execute2 xmlns="http://www.some/namespace/">
<transaction-limit type="Amount">...
it is logically equivalent to the one you posted, and the Message Mapping will treat them identical.
Greetings
Stephan

Namespace prefix null in FaultCode

Hello,
I am seeing this null namespace prefix in faultcode in the fault I received. When I browsed this forum discussing fault details, generally I noticed pretty much everyone have this same null prefix in fault codes.
<Fault>
*<faultcode>null:remoteFault</faultcode>*
<faultstring>business exception</faultstring>
<faultactor>cx-fault-actor</faultactor>
</Fault>
Does anyone have any insight into what is causing the Fault message to put "null" prefix?
With Regards,
Ranjith

Hi Ranjith,
In my 10.1.3.5 server, I get a remote exception as follows:
<Fault soapenv="http://schemas.xmlsoap.org/soap/envelope/" >
<faultcode ns1="http://schemas.oracle.com/bpel/extension" >ns1:remoteFault</faultcode>
<faultstring>business exception</faultstring>
<faultactor>cx-fault-actor</faultactor>
<detail>
<summary>when invoking locally the endpoint 'http://enduro:9700/orabpel/default/BPELProcess1/1.0', ; nested exception is: ORABPEL-02104 Process mode closed. The process class "BPELProcess1" (revision "1.0") is not in an open mode. New instances may not be created when the process is not open; existing instances are permitted to complete normally. Only the active revision of a process class (that is, the most recently deployed) may be open; all other revisions are automatically closed. </summary>
<detail>ORABPEL-02104 Process mode closed. The process class "BPELProcess1" (revision "1.0") is not in an open mode. New instances may not be created when the process is not open; existing instances are permitted to complete normally. Only the active revision of a process class (that is, the most recently deployed) may be open; all other revisions are automatically closed. </detail>
</detail>
</Fault>So I think it might be a 10.1.3.3 issue or specific to your installation.
Can you confirm you have the file $ORACLE_HOME/bpel/system/xmllib/RuntimeFault.wsdl and its contents define the fault elements in the bpelx:("http://schemas.oracle.com/bpel/extension") namespace and in your bpel files you have defined the bpelx namespace extension to that?
regards,
Shanmu.

Better rss feeds without jf namespace prefix

Hi Discussions,
It would be nice if the RSS feeds provided did not use these 'jf' namespace prefixed tags, but rather plain old RSS tags that most RSS readers, inclusive of Safari & Mail currently understand. The feeds contain tags like:
<jf:creationDate>Mon, 31 Mar 2008 14:02:16 -0500</jf:creationDate>
<jf:modificationDate>Mon, 31 Mar 2008 14:02:16 -0500</jf:modificationDate>
<jf:author>J.K. ROFLing</jf:author>
<jf:replyCount>0</jf:replyCount>
it would be better if they were something like:
<pubDate>Mon, 31 Mar 2008 14:02:16 -0500</pubDate>
<author>J.K. ROFLing</author>
or
<dc:creator>J.K. ROFLing</dc:creator>
or if they included such standard tags in addition to the jf: tags. As it is now, an rss reader doesn't know what these tags are and gives each entry the pubDate of the entire feed, and includes no author or subject info.
The feeds could also include the discussion group name as a "category" tag for each entry. that would perhaps be even better when a couple of feeds are grouped together.
As it is today the RSS feeds aren't nearly as compatible with Safari and Mail or other RSS readers as one might reasonably hope/expect. With all the work already sunk into providing the feeds at all, it would be nice to go the last couple of inches and make them (more) useable.
Cheers,
Chris

Hi Nick,
I added the namespace to the file (as per the below) but it gives compilation errors (C:\JDeveloper\mywork\FeedReader\RSSViewController\public_html\rssFeedReader.jsff - Error(4,11): This attribute is not recognized)
<?xml version='1.0' encoding='windows-1252'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
xmlns:af="http://xmlns.oracle.com/adf/faces/rich"
xlmns: h="http://java.sun.com/jsf/html">
<af:panelGroupLayout layout="vertical" id="qjgpgl1">
<af:outputText value="#{bindings.titleHead.inputValue}"
inlineStyle="color:Black; font-weight:bold;" id="qjgot1"/>
<af:outputText value="#{bindings.titleDesc.inputValue}"
inlineStyle="color:Gray;" id="qjgot2"/>
<af:spacer width="10" height="10" id="qjgs1"/>
<af:forEach var="row" items="#{bindings.Feed.rangeSet}">
<h:panelGrid columns="1" id="qjgpg1">
<af:goLink text="#{row.title}"
destination="#{row.link}"
inlineStyle="width:100%; font-weight:bold; color:ActiveCaption;"
id="qjggl1"/>
<af:outputText value="#{row.description}"
inlineStyle="color:Black;" id="qjgot3"/>
<af:spacer width="10" height="5" id="qjgs2"/>
</h:panelGrid>
</af:forEach>
</af:panelGroupLayout>
</jsp:root>

Unknown namespace prefix Error - when using custom Aliases with RDF aliases

I am getting unknown namespace prefix error when I use custome SEM_ALIAS with rdf SEM_ALIAS. It seems once you specify custom SEM_ALIAS, the default rdf alias is not recognized. Following are the details of queries
I have a sem_Model "test" which has "event" as a class and "Merger" as a sub-class of event, with "acquiringorg" as a property having the domain "org". "Org" is also defined as a class with the literal attribute "hasname". I have added one instance of "merger" class with appropriate values for "acquiringorg" property. There is one instance or "Org" as well for reference in the instance above.
the following query(return all objects having property "acquiringorg" and its .e. "hasName" attribute for the object) runs fine and returns appropriate resultset
select x event,z acquiringorg ,l acquireeorg from table(SEM_MATCH(
'(?x Evnt:AcquiringOrg ?y)(?k orgn:hasName ?l)',
SEM_MODELS('test'),
null,
SEM_ALIASES(SEM_ALIAS('Evnt','http://www.abc.com/Event/Merger/'),
SEM_ALIAS('orgn','http://www.abc.com/Org/')),
null));
However when I want to add another criteria i.e. show me events of type merger(?x rdf:type :Merger) , the query fails with the "unknown namespace prefix error" as above
select x event,z acquiringorg ,l acquireeorg from table(SEM_MATCH(
'(?x rdf:type :Merger)(?x Evnt:AcquiringOrg ?y)(?k orgn:hasName ?l)',
SEM_MODELS('test'),
null,
SEM_ALIASES(SEM_ALIAS('Evnt','http://www.abc.com/Event/Merger/'),
SEM_ALIAS('orgn','http://www.abc.com/Org/')),
null));
specifying "rdf" ALIAS explicitly also does not work
select x event,z acquiringorg ,l acquireeorg from table(SEM_MATCH(
'(?x rdf:type :Merger)(?x Evnt:AcquiringOrg ?y)(?k orgn:hasName ?l)',
SEM_MODELS('test'),
null,
SEM_ALIASES(_SEM_ALIAS('rdf', 'http://www.w3.org/1999/02/22-rdf-syntax-ns#'),_
SEM_ALIAS('Evnt','http://www.abc.com/Event/Merger/'),
SEM_ALIAS('orgn','http://www.abc.com/Org/')),
null));
I am unable to figure out why default namespace i.e. rdf is returning this error
Stuck at this point badly!!Any pointers would be useful!!

Full error details are as below
ORA-29532: Java call terminated by uncaught Java exception: oracle.spatial.rdf.server.ParseException: Unknown namespace prefix ''
ORA-06512: at "MDSYS.RDF_MATCH_IMPL_T", line 153
ORA-06512: at "MDSYS.RDF_MATCH_IMPL_T", line 842
ORA-06512: at "MDSYS.RDF_MATCH_IMPL_T", line 235
ORA-06512: at line 1
29532. 00000 - "Java call terminated by uncaught Java exception: %s"
*Cause: A Java exception or error was signaled and could not be
resolved by the Java code.
*Action: Modify Java code, if this behavior is not intended.

Declaring Namespace Prefixes

Hello,
I tried to use the expression "xdofx:upper(email_addr)" but am getting this error:
Caused by: oracle.xdo.parser.v2.XPathException: Namespace prefix 'xdofx' used but not declared. So how do you declare namespace prefixes?
Regards,
Smita

Hello,
I'm using xmlbeans in my project. I'm constructing xml using the xmlbeans
generated sources from the XML Schema files. The server to which I'm
sending the request doesn't recognize the namespace URI's or the prefixes.
so, once the XML document is constructed, I'm trying to strip of the
namespace URI's and prefixes using the below code and couldn't get it to
work.
Map m=
new HashMap();
m.put(
http://www.abc.com/schemas/myproj/avail/2008/01, "");
m.put(
http://www.abc.com/schemas/myproj/common/2008/01,"";);
opts.setLoadSubstituteNamespaces(m);
opts.setUseDefaultNamespace();
SampleRQDocument propAvailRQDoc = SampleRQDocument.Factory.*newInstance*
(opts);
The schemas are defined under 3 different namespaces.
How can I remove the Namespace URI's and Prefixes after I construct the XML
document?
Next thing, when the server sends the response, the response doesn't include
any Namespace URI or the prefixes. How can I embed the URI's and Prefixes in
the response document after I receive it so, I can use XML Beans
to bind the XML to the generated sources.
I searched on google but couldn't find a suitable solution.
Any help in this regard is greatly appreciated.
Thanks,
Sridhar.

Implication of Namespace Prefix

Hi All,
Something I need to understand:
What is the implication do creating a namespace prefix? For example, I have create a SC with:
Vendor: trial.com.ex1
Name: TEST_PROD
Then I create an SC with:
Vandor: trial.com.ex1
Name: TEST_SC
Now I create a Development Component namespace prefix as trial.com.ex1/TEST.
Now I go to my developer studio and create a DC with Vendor: trial.com (note: I didn't give trial.com.ex1).
Name: trialdc
What effect will this have on my build? Should it have allowed me to create a DC with this vendor? Or is this some other Development Component and has nothing to do with the DC I created. I am basically trying to understand the significance of the namespace prefix w.r.t. the categories.
My concepts about the namespaces are not clear and I couldn't find any satisfactory explanation for this.
Nirav

My personal experience is that it takes a while for a defined namespace prefix to become available in the NWDS. In our case it seemed not get there at all, so we triggered an Update CMS and restarted our NWDS's. After a while the namespace prefix became available, but we're not sure if that was because of the Update CMS.
Note that you must have defined a NameServer Configuration in the DTR for these namespace prefix definitions to become available at all in your NWDS.
Once you have this working correctly, you will not be able to use something different than what has been defined in your NWDS as you were able to do now. On the other hand I don't think using this other vendor will give you any trouble.
Message was edited by: Pascal Willemsen

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

Defining Additional DC Namespace Prefixes

Similar Messages

Maybe you are looking for