Register namespace prefixes in JDeveloper?

Hi,
Is it possible to register namespace prefixes for namespaces in JDeveloper, so you can use the same prefixes for the same elements in different BPEL processes?
As it is JDeveloper generates prefixes like ns1, n2 etc. which makes BPEL code less readable/maintainable...
Groeten,
HJH

Hi,
I would love to know if this is possible and how to do it.
And if the namespace configuration file could be shared across a team of developers using JDev that would be Nirvana!
Robert

Similar Messages

JDeveloper 10.1.3 - Disabling ns0: namespace prefix in soap body children ?

I am attempting to use a PeopleSoft web service. However, the PeopleSoft web service does not recognize operations which have a namespace prefix. Using visual studio, namespace prefixes are not used in the child elements of the soap body element. I am able to call the service using visual studio.
JDeveloper 10.1.3 uses a namespace prefix for children of the body element which is recommended by the soap spec. However, I need to disable that behavior so that I can actually get the program working with PeopleSoft.
Can anyone tell me if there is an easy way to disable the ns0: prefix that is used by the generated web service proxy stub? I have traced through the generated proxy code but I do not see any properties that can be modified. The only thing I can think of is to modify the generated code but I do not want to go that route.
Thanks,
Rich

Delete the NS0: related text, in JDev, from your WSDL and it should work. I had the same problem with .NET not liking it also.
Keep in mind you'll have to tweak the WSDL again if you regenerate it.
You sure you're using 10.1.3? I upgraded and it shows the NS0: as a problem in existing projects. I'm working on the latest, production download so maybe it's been corrected.

Namespace prefix in Root element missing during variable assignment in SOA Suite 11g

I need qualified element Namespaces in one of the target variables. All elements being referred to would have the namespace prefixed. This is working for all child elements, but not the for root element. How can i get the root element prefixed with the namespace?
We are using SOA Suite 11g and the Jdeveloper version we are using is 11.1.1.6.0
when i use transform operation to populate the target variable the variable gets populated something like this :
<inputVariable>
<part name="payload">
<Message>
<msg:Header>
<head:field1>xxxxxx</head:field1>
<head:field2>2013-07-09T08:00:55</head:field1>
</msg:Header>
</Message>
But the actual output we need is
<inputVariable>
<part name="payload">
<msg:Message>
<msg:Header>
<head:field1>xxxxxx</head:field1>
<head:field2>2013-07-09T08:00:55</head:field1>
</msg:Header>
</msg:Message>
We tried the fix suggested in one of the SOA threads but its not working for us and looks like that will work only for SOA SUITE 10g.
Please provide us any help/suggestions if anyone know the solution.
Thank you in advance for the help.

Any one can help us please.......

Namespace prefix in Root element missing during variable assignment

In bpel 10.1.3.4, I need qualified element Namespaces in one of the target variables. I have an xsd that has elementFormDefault = "qualified" set, therefore all elements being referred to would have the namespace prefixed. This is working for all child elements, but not the root element. How can i get the root element prefixed with the namespace?
If i use transform or copy/append operation to populate in the target variable the variable gets populated something like this :
<Invoice xmlns:pidx="http://www.api.org/pidXML/v1.0" pidx:transactionPurposeIndicator="Original" pidx:version="1.0" xmlns="http://www.api.org/pidXML/v1.0">
<pidx:InvoiceProperties>
<pidx:InvoiceNumber>test123</pidx:InvoiceNumber>
</pidx:InvoiceProperties>
</Invoice>
Whereas i need :
<*pidx:*Invoice xmlns:pidx="http://www.api.org/pidXML/v1.0" pidx:transactionPurposeIndicator="Original" pidx:version="1.0" xmlns="http://www.api.org/pidXML/v1.0">
<pidx:InvoiceProperties>
<pidx:InvoiceNumber>test123</pidx:InvoiceNumber>
</pidx:InvoiceProperties>
</*pidx:*Invoice>
Is there some way to accomplish this?
Regards,
Sandeep

Hi Sandeep,
We have exactly the same issue, but, when we implemented the solution, we are getting the following error, when we tried to compile the code, we are using 11.1.1.4.0 version of SOA 11g, appreciate if there is any way you can help us on this:
Jul 12, 2011 2:40:28 PM com.collaxa.cube.CubeLogger info
INFO: validating "BPELProcess1.bpel" ...
oracle.jrf.UnknownPlatformException: JRF is unable to determine the current application server platform.
     at oracle.jrf.ServerPlatformSupportFactory.getInstance(ServerPlatformSupportFactory.java:79)
     at oracle.integration.platform.blocks.WLSPlatformConfigurationProvider.<clinit>(WLSPlatformConfigurationProvider.java:44)
     at oracle.integration.platform.blocks.FabricConfigManager.<clinit>(FabricConfigManager.java:154)
     at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.loadXpathFunctions(FabricXPathFunctionResolver.java:282)
     at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.loadXPathConfigFile(FabricXPathFunctionResolver.java:156)
     at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.init(FabricXPathFunctionResolver.java:49)
     at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.loadFabricXpathFunctions(BPELXPathFunctionNameResolver.java:57)
     at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.<init>(BPELXPathFunctionNameResolver.java:48)
     at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.<clinit>(BPELXPathFunctionNameResolver.java:44)
     at com.collaxa.cube.lang.compiler.bpel.XPathExprValidatorVisitor.<init>(XPathExprValidatorVisitor.java:122)
     at com.collaxa.cube.lang.compiler.bpel.AssignValidator.<init>(AssignValidator.java:89)
     at com.collaxa.cube.lang.compiler.bpel.BpelParser.<init>(BpelParser.java:452)
     at com.collaxa.cube.lang.compiler.bpel.BPELValidator.validate(BPELValidator.java:60)
     at com.collaxa.cube.lang.compiler.BPEL1Processor.validate(BPEL1Processor.java:329)
     at com.collaxa.cube.lang.compiler.BPEL1Processor.process(BPEL1Processor.java:153)
     at com.collaxa.cube.lang.compiler.CubeParserHelper.compile(CubeParserHelper.java:47)
     at oracle.fabric.bpel.bpelc.BPELComponentValidator.validate(BPELComponentValidator.java:40)
     at oracle.soa.scac.ValidateComposite.validateComponentTypeServicesReferences(ValidateComposite.java:1117)
     at oracle.soa.scac.ValidateComposite.doValidation(ValidateComposite.java:500)
     at oracle.soa.scac.ValidateComposite.run(ValidateComposite.java:150)
     at oracle.soa.scac.ValidateComposite.main(ValidateComposite.java:135)
Jul 12, 2011 2:40:29 PM CubeProcessGenerator compile
WARNING: classpath is: C:\oracle\Middleware\jdeveloper\jdev\extensions\oracle.sca.modeler.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;C:\oracle\Middleware\oracle_common\modules\oracle.fabriccommon_11.1.1\fabric-common.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.mediator_11.1.1\mediator_client.jar;C:\oracle\Middleware\oracle_common\modules\oracle.mds_11.1.1\mdsrt.jar;C:\oracle\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xmlparserv2.jar;C:\oracle\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xml.jar;C:\oracle\Middleware\jdeveloper\jdev\extensions;;C:\JDeveloper\mywork\InvoiceTransferApp\InvoiceTransferProj\SCA-INF\classes;C:\JDeveloper\mywork\InvoiceTransferApp\InvoiceTransferProj\SCA-INF\classes;C:\JDeveloper\mywork\InvoiceTransferApp\InvoiceTransferProj\SCA-INF\gen-classes;C:\oracle\Middleware\oracle_common\modules\commonj.sdo_2.1.0.jar;C:\oracle\Middleware\oracle_common\modules\oracle.fabriccommon_11.1.1\fabric-common.jar;C:\oracle\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xmlparserv2.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\bpel1-1-xbeans.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-common.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\bpel_coherence_config.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-exts.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\thirdparty.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\bpm-analytics.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-thirdparty.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\wsif-binding.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-validator.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\monitor-rt-xbean.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\oracle.soa.bpmn.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel1.jar;C:\oracle\Middleware\jdeveloper\soa\modules\user-patch.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.thirdparty.jar;C:\oracle\Middleware\jdeveloper\uddi\lib\oracle.soa.uddi.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\bpm-infra.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\testfwk-xbeans.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-ext.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\soa-infra-scheduler.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\xmlunit-1.1.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\soa-infra-tools.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\soa-xpath-exts.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\oracle-soa-client-api.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.wls.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-client.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime-ext-was.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime-ext-wls.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\oracle.soa.fabric.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.ext_11.1.1\classes
Regards,
Sireesh

"Cleaning" disambiguated namespace prefixes

Hello,
In a bind here. Have a solution that depends upon a "clean" namespace prefix. Over time, we find that prefix gets disambiguated and we have no way to "flush" or "Clean" what appears to be a cache. For arguments sake, lets say the prefix is "ABCD:". As the production artist works on so many different files and apps throughout a day, somewhere at some time, the prefix becomes "ABCD_1_:" thus crippling our solution. In the recent past, simply quitting all Adobe apps and relaunching seemed to "flush" the disambiguation, but no more. People i've consulted with seem to think it is an "easy" thing to fix, but not for me. Please describe or prescribe a solution or recommendation and I would be quite happy.
Thank you in advance

Hi,
You should never expect a prefix to be nonambiguous.
As in XML, the namespace prefix in XMP serves only as a key to look up the appropriate URI. The combination of URI and property name is the unique and "qualified" name, the prefix serves as a kind of variable name and can be anything.
If a prefix is used twice for different namespaces you might see the above behaviour (adding _1_), this is correct behaviour to keep the URI lookup nonambiguous.
In our XMPCore library you can register your costum namespace and add a prefered prefix which will be used during serialization of xmp.
For more details please read the XMP specification part 1:
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/xmp/pdfs/cc-201306/XM PSpecificationPart1.pdf
-Samy

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>

How to insert namespace prefix when using xmltype

Hi,
I have registered the following XML schema into XMLDB.
<s:schema xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" xmlns:m="https://suora.tietopalvelut.com/ATJkysely/" targetNamespace="https://suora.tietopalvelut.com/ATJkysely/" elementFormDefault="qualified" xdb:schemaURL="http://www.fennia.fi/Hae121.xsd">
     <s:element name="Hae" type="m:Hae121" xdb:SQLType="Hae121"/>
     <s:complexType name="Hae121" xdb:SQLType="Hae121" xdb:maintainDOM="false">
          <s:sequence>
               <s:element name="kayttajatunnus" type="m:Kayttajatunnus" minOccurs="0" xdb:SQLName="kayttajatunnus" xdb:SQLType="Kayttajatunnus121" xdb:SQLInline="true"/>
               <s:element name="palvelutunnus" type="s:string" minOccurs="0" xdb:SQLName="palvelutunnus" xdb:SQLType="VARCHAR2" xdb:SQLInline="true"/>
               <s:element name="kyselylaji" type="s:string" minOccurs="0" xdb:SQLName="kyselylaji" xdb:SQLType="VARCHAR2" xdb:SQLInline="true"/>
               <s:element name="rekisteritunnus" type="s:string" minOccurs="0" xdb:SQLName="rekisteritunnus" xdb:SQLType="VARCHAR2" xdb:SQLInline="true"/>
               <s:element name="laji" type="s:string" minOccurs="0" xdb:SQLName="laji" xdb:SQLType="VARCHAR2" xdb:SQLInline="true"/>
               <s:element name="ajoneuvoluokka" type="s:string" minOccurs="0" xdb:SQLName="ajoneuvoluokka" xdb:SQLType="VARCHAR2" xdb:SQLInline="true"/>
               <s:element name="valmistenumero" type="s:string" minOccurs="0" xdb:SQLName="valmistenumero" xdb:SQLType="VARCHAR2" xdb:SQLInline="true"/>
               <s:element name="jarjestelmatunnus" type="s:string" minOccurs="0" xdb:SQLName="jarjestelmatunnus" xdb:SQLType="VARCHAR2" xdb:SQLInline="true"/>
          </s:sequence>
     </s:complexType>
     <s:complexType name="Kayttajatunnus" xdb:SQLType="Kayttajatunnus121" xdb:maintainDOM="false">
          <s:sequence>
               <s:element name="username" type="s:string" minOccurs="0" xdb:SQLName="username" xdb:SQLType="VARCHAR2" xdb:SQLInline="true"/>
               <s:element name="password" type="s:string" minOccurs="0" xdb:SQLName="password" xdb:SQLType="VARCHAR2" xdb:SQLInline="true"/>
               <s:element name="statcode" type="s:string" minOccurs="0" xdb:SQLName="statcode" xdb:SQLType="VARCHAR2" xdb:SQLInline="true"/>
               <s:element name="enduserid" type="s:string" minOccurs="0" xdb:SQLName="enduserid" xdb:SQLType="VARCHAR2" xdb:SQLInline="true"/>
               <s:element name="timestamp" type="s:string" minOccurs="0" xdb:SQLName="timestamp" xdb:SQLType="VARCHAR2" xdb:SQLInline="true"/>
               <s:element name="checksum" type="s:string" minOccurs="0" xdb:SQLName="checksum" xdb:SQLType="VARCHAR2" xdb:SQLInline="true"/>
               <s:element name="ticket" type="s:string" minOccurs="0" xdb:SQLName="ticket" xdb:SQLType="VARCHAR2" xdb:SQLInline="true"/>
          </s:sequence>
     </s:complexType>
</s:schema>
In PL/SQL I populate the object types, which have been automatically generated.
Then I create an XMLTYPE object using the following code:
akeobject "Hae121";
v_schema VARCHAR2 (1000) := 'http://www.fennia.fi/Hae121.xsd';
v_schema_element VARCHAR2 (100) := 'Hae';
--akeobject populated here
v_xml_out := XMLTYPE (akeobject, v_schema, v_schema_element);
DBMS_OUTPUT.put_line ('v_xml_out:' || v_xml_out.getstringval ()) shows the following:
<Hae xmlns="https://suora.tietopalvelut.com/ATJkysely/">
<kayttajatunnus>
<username>kayttaja</username>
<password>salasana</password>
<statcode>tiltunn</statcode>
<enduserid>loppukay</enduserid>
<timestamp>20060822100700</timestamp>
<checksum>E77B30394D23F83D422A63027F8F63A8</checksum>
<ticket>nyckkeli</ticket>
</kayttajatunnus>
<palvelutunnus>PALVELUTUNNUS</palvelutunnus>
<kyselylaji>41</kyselylaji>
<rekisteritunnus>BRF-444</rekisteritunnus>
<ajoneuvoluokka>1</ajoneuvoluokka>
<valmistenumero>BBBB</valmistenumero>
<jarjestelmatunnus>AAAA</jarjestelmatunnus>
</Hae>
There are no namespace prefixes.
When I create a model XML file using XMLSpy, I get the following:
<?xml version="1.0" encoding="UTF-8"?>

<m:Hae xmlns:m="https://suora.tietopalvelut.com/ATJkysely/">
     <m:kayttajatunnus>
          <m:username>String</m:username>
          <m:password>String</m:password>
          <m:statcode>String</m:statcode>
          <m:enduserid>String</m:enduserid>
          <m:timestamp>String</m:timestamp>
          <m:checksum>String</m:checksum>
          <m:ticket>String</m:ticket>
     </m:kayttajatunnus>
     <m:palvelutunnus>String</m:palvelutunnus>
     <m:kyselylaji>String</m:kyselylaji>
     <m:rekisteritunnus>String</m:rekisteritunnus>
     <m:laji>String</m:laji>
     <m:ajoneuvoluokka>String</m:ajoneuvoluokka>
     <m:valmistenumero>String</m:valmistenumero>
     <m:jarjestelmatunnus>String</m:jarjestelmatunnus>
</m:Hae>
What am I doing wrong because there are no namespace prefixes when using XMLTYPE in PL/SQL?
My environment is 10g 10.2.0.2.
Thanks,
Veli-Matti

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

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

Missing namespace prefix in the soap body

Hello
The soap body that is produced along with soap header for my webservice. I
am the client talking to a server. The first piece in RED color is what
weblogic generates to send to the client but does NOT work. The one below
though works fine which is what I manipulated by hand to send to the
server. I have no idea why weblogic drops the namespace prefix in the
BODY.
-Narahari
The message is as shown below
POST /FS HTTP/1.1
Host: asgappsrv10:6211
Content-Type: text/xml; charset=utf-8
Connection: close
SOAPAction: "ListDomains"
<?xml version="1.0" encoding="utf-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header>
<n1:Credentials xmlns:n1="urn:criticalpath:fs:api:1.0"
xsi:type="n1:Credentials">
<Username xsi:type="xsd:string">admin@default</Username>
<Password xsi:type="xsd:string">password</Password>
<SessionId xsi:nil="true"/>
</n1:Credentials>
</env:Header>
<env:Body
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<Fulfill xmlns:n2="urn:criticalpath:fs:api:1.0"
xsi:type="n2:Fulfill">
<Request xsi:type="xsd:string">ListDomains</Request>
<RequestAttributes soapenc:arrayType="n2:Attribute[0]"/>
<Async xsi:type="xsd:boolean">false</Async>
</Fulfill>
</env:Body>
</env:Envelope>
When you see the data carefully, the env:Body has the Fulfill element. But
it does have a namespace prefix on it. This causes the call to fail. If I
change the above segment manally to look like
POST /FS HTTP/1.1
Host: asgappsrv10:6211
Content-Type: text/xml; charset=utf-8
Connection: close
SOAPAction: "ListDomains"
<?xml version="1.0" encoding="utf-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header>
<n1:Credentials xmlns:n1="urn:criticalpath:fs:api:1.0"
xsi:type="n1:Credentials">
<Username xsi:type="xsd:string">admin@default</Username>
<Password xsi:type="xsd:string">password</Password>
<SessionId xsi:nil="true"/>
</n1:Credentials>
</env:Header>
<env:Body
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<n2:Fulfill xmlns:n2="urn:criticalpath:fs:api:1.0"
xsi:type="n2:Fulfill">
<Request xsi:type="xsd:string">ListDomains</Request>
<RequestAttributes soapenc:arrayType="n2:Attribute[0]"/>
<Async xsi:type="xsd:boolean">false</Async>
</n2:Fulfill>
</env:Body>
</env:Envelope>

Hi All,
we are also facing the same issue, Please provide the solution if anyone knows. We are also using the SOA Suite 11g Version.

Extracting XML values with namespace prefixes

Hint: I put this topic in "SQL and PL/SQL" but that was a bad idea, I think.
Hi!
I have a XML file:<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="http://test.epuap.gov.pl/FeResourceServlet/wzor_lokalny/InstytucjaPubliczna/Deklaracja_DT/styl.xsl"?>
<wnio:Deklaracja
xmlns:adr="http://crd.gov.pl/xml/schematy/adres/2008/05/09/"
xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
xmlns:ev="http://www.w3.org/2001/xml-events"
xmlns:inst="http://crd.gov.pl/xml/schematy/instytucja/2008/05/09/"
xmlns:meta="http://crd.gov.pl/xml/schematy/meta/2008/05/09/"
xmlns:oso="http://crd.gov.pl/xml/schematy/osoba/2008/05/09/"
xmlns:str="http://crd.gov.pl/xml/schematy/struktura/2009/11/16/"
xmlns:wnio="http://test.epuap.gov.pl/FeResourceServlet/wzor_lokalny/InstytucjaPubliczna/Deklaracja_DT/"
xmlns:xforms="http://www.w3.org/2002/xforms"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xxforms="http://orbeon.org/oxf/xml/xforms"
xsi:schemaLocation="http://test.epuap.gov.pl/FeResourceServlet/wzor_lokalny/InstytucjaPubliczna/Deklaracja_DT/ http://test.epuap.gov.pl/FeResourceServlet/wzor_lokalny/InstytucjaPubliczna/Deklaracja_DT/schemat.xsd">
                            <wnio:OpisDokumentu><str:CID>[email protected]</str:CID><meta:Identyfikator typIdentyfikatora="idFormularza"><meta:Wartosc>InstytucjaPubliczna/Deklaracja podatku od środków transportowych DT-1</meta:Wartosc></meta:Identyfikator></wnio:OpisDokumentu>
                            <wnio:Naglowek>
                                <wnio:KodFormularza kodSystemowy="DT-1(3)"/>
                                <wnio:WariantFormularza>3</wnio:WariantFormularza>
                                <wnio:Rok>2008</wnio:Rok>
                                <wnio:ObowiazekSkladaniaDeklaracji>1</wnio:ObowiazekSkladaniaDeklaracji>
                                <wnio:MiejsceSkladania/>
                            </wnio:Naglowek>
                            <wnio:Podatnik>
                                <wnio:OsobaPrawna>
                                    <wnio:NIP>345678901</wnio:NIP>
                                    <wnio:PelnaNazwa>Testowa Instytucja Publiczna</wnio:PelnaNazwa>
                                    <wnio:NazwaSkrocona/>
                                    <wnio:REGON>234512345</wnio:REGON>
                                </wnio:OsobaPrawna>
                                <wnio:AdresSiedzibyZamieszkania>
                                    <wnio:KodKraju>PL</wnio:KodKraju>
                                    <wnio:Wojewodztwo>ŚLĄSKIE</wnio:Wojewodztwo>
                                    <wnio:Powiat>Katowice</wnio:Powiat>
                                    <wnio:Gmina>Katowice (gmina miejska)</wnio:Gmina>
                                    <wnio:Ulica>ul. Mikołowska</wnio:Ulica>
                                    <wnio:NrDomu>100</wnio:NrDomu>
                                    <wnio:NrLokalu>924</wnio:NrLokalu>
                                    <wnio:Miejscowosc>Katowice (miasto)</wnio:Miejscowosc>
                                    <wnio:KodPocztowy>40-065</wnio:KodPocztowy>
                                    <wnio:Poczta>Katowice</wnio:Poczta>
                                </wnio:AdresSiedzibyZamieszkania>
                            </wnio:Podatnik>
                            <wnio:PozycjeSzczegolowe>
                                <wnio:D.1>
                                    <wnio:P_22/>
                                    <wnio:P_23/>
                                </wnio:D.1>
                                <wnio:D.2>
                                    <wnio:P_28/>
                                    <wnio:P_29/>
                                </wnio:D.2>
                                <wnio:P_82/>
                                <wnio:P_83/>
                            </wnio:PozycjeSzczegolowe>
                            <wnio:Zalacznik_DT-1A>
                                <wnio:P_1/>
                                <wnio:P_2/>
                                <wnio:P_22>1</wnio:P_22>
                            </wnio:Zalacznik_DT-1A>
                            <wnio:Zalacznik_DT-1A>
                                <wnio:P_1/>
                                <wnio:P_2/>
                                <wnio:P_22>3</wnio:P_22>
                            </wnio:Zalacznik_DT-1A>
                        </wnio:Deklaracja>and an overloaded function:
function dodaj_DT1_z_xml(p_dt1 in out nocopy XMLType) return number as
r_dt1   POD_SRTR_DT1%rowtype;
r_dt1a POD_SRTR_DT1A%rowtype;
r_sdek POD_SRTR_DEKLARACJE%rowtype;
l_wariantDT1 number(2);
l_xosf XMLType;
l_xosp XMLType;
l_xadr XMLType;
l_xszcz XMLType;
l_zal   XMLType;
l_z     XMLType;
l_zno   pls_integer;
l_xml   XMLType;
l_ns    varchar2(10);
-- xmlns:wnio="http://test.epuap.gov.pl/FeResourceServlet/wzor_lokalny/InstytucjaPubliczna/Deklaracja_DT/"
begin
if --p_dt1.existsNode('/wnio:Deklaracja')=0 and
     p_dt1.existsNode('/Deklaracja','xmlns:wnio="http://test.epuap.gov.pl/FeResourceServlet/wzor_lokalny/InstytucjaPubliczna/Deklaracja_DT/"')=0
then return -2; end if;
if p_dt1.existsNode('/wnio:Deklaracja')=1 then
    l_ns := 'wnio:';
end if;
if p_dt1.existsNode('/'||l_ns||'Deklaracja')=0 then                     return -2; end if;
if p_dt1.existsNode('/'||l_ns||'Deklaracja/'||l_ns||'Naglowek')=0 then            return -3; end if;
if p_dt1.existsNode('/'||l_ns||'Deklaracja/'||l_ns||'Podatnik')=0 then            return -4; end if;
if p_dt1.existsNode('/'||l_ns||'Deklaracja/'||l_ns||'PozycjeSzczegolowe')=0 then return -5; end if;
return 1;
end;
function dodaj_DT1_z_xml(p_dt1 in out nocopy CLOB) return number is
l_xml   XMLType;
begin
l_xml := XMLType(p_dt1);
return dodaj_DT1_z_xml(l_xml);
end dodaj_DT1_z_xml;I run the code:declare
v_clob CLOB;
v_out   number;
begin
SELECT dok_content INTO v_clob FROM EPUAP.epuap_dokumenty WHERE dok_id=13;
v_out := POD_PCK_SRTR_DT1.DODAJ_DT1_Z_XML(v_clob);
DBMS_OUTPUT.put_line(v_out);
end;the output is -2. What must I change to find the node "wnio:Deklaracja"? I'm newbie in XML and namespaces :(
Help me, please...
Oracle version is 10.2.0.3

Hi,
If you declare a namespace prefix then corresponding elements must be qualified.
So, either do :
p_dt1.existsNode('/wnio:Deklaracja','xmlns:wnio="http://test.epuap.gov.pl/FeResourceServlet/wzor_lokalny/InstytucjaPubliczna/Deklaracja_DT/"')or use a default namespace declaration :
p_dt1.existsNode('/Deklaracja','xmlns="http://test.epuap.gov.pl/FeResourceServlet/wzor_lokalny/InstytucjaPubliczna/Deklaracja_DT/"')BTW, could you explain what are you trying to accomplish?

Disable namespace prefixes in Transformer

hi
I am stuck in a cyclic problem. JAXP XSLT and SchemaValidator do not work together. (Java 1.5 and 1.6)
I have a XSD with a namespace.
When I generate the XML using an XSLT I specify namespace using the namespace attribute of xsl:element
The JAXP transformer always generate the namespace prefix and equate the prefix with the actual URI
Is there a way to disable this behavior, that is, I do want the xmlns URI in the root element but not the prefix?
There are two reasons for wanting an XML without prefixes:
1) The Schema Validator provided with JRE is not able to validate the message with prefix, but it works fine with xmlns URI
<rootelem xmlns="urn:xmlns:xyz.abc.com"> validates fine
but
<ns0:rootelem xmlns:ns0="urn:xmlns:xyz.abc.com"> fails validation with error:
org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the declaration of element 'ns0:rootelem'.
I am able to generate the first case when I use Saxon based OrangeXSLT plugin for Eclipse but JAXP based transformer always generate the second case.
2) More importantly, I have XML consumers that could use parsing without namespace support and prefixed element will not work there.
I am using StreamResult in the Transformer.transform() call and my guess is that the internal implementation of Transformer might be using a SAX ContentHandler (XML Serializer) to write XML to the outputStream and I guess one way to get around could be that I write a custom ContentHandler and use a SAXResult in the transform call. I am not sure if I am thinking in the right direction.
If I am correct in my guess, could someone please point to some implementation of XMLSerializer that could be overridden just to disable namespace prefixing behavior?
I have removed the namespace from the XSD for things to work. I would appreciate any help with this.

Moving to latest Xalan and Xerces solved the problem.
But a new one surfaced.
Xalan's latest transformer does not handle StreamSource correctly and throws some exception internally (IOException related to end of stream), with the message:
SystemId Unknown; Line #-1; Column #-1; Premature end of file.
It work correctly if a DOMSource is provided as the input. This does not make sense, since the InputStream my code is using for StreamSource is ByteArrayInputStream for an in-memory XML and such error would happen if this stream is read more than once without calling a reset in between.
Please let me know if this seems like a valid bug or if I am doing something wrong.

How to suppress n0: default Namespace prefix in Transformations

Hi,
I use Simple Transformations for serialization of deep structured data.
In the XML File the whole tree needs to use a special namespace. Therefore i use the attribute xmlns="ABC.de" without a namespace prefix in my root element. During serialization SAP generates a default namespace prefix like 'n0:'.
Is it possible to suppress the generated namespace prefix?
Thank you very much for reply
René
Edited by: René Libbert on Feb 14, 2012 8:09 AM

Maybe somebody is interested.
It seems to be a problem on old 640. On a NW 702 the result is as expected. NW 700 was not tested.
Workaround for the 640 is to use as result a STRING field not an XSTRING.
Greetings René

Problem with namespace prefix

Dear all,
I'm using code generated by NW Developer Studio 2004s 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 ECC (ERP 6.0) doesn't like the namespace prefixes (the namespace was not recognised by the ECC mapping tool.)and throws back a DeliveryException.
The SOAP message created by the generated NWDS code is:
<?xml version="1.0" encoding="UTF-8" ?>
- <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="urn:sap-com:document:sap:rfc:functions" xmlns:tns="urn:sap-com:document:sap:rfc:functions">
- <SOAP-ENV:Body>
- <wn4:Z_APPOINTMENT_GET_JCO_ORG>
<wn4:DATE_FROM>2007.01.01</wn4:DATE_FROM>
<wn4:DATE_TO>2008-02-02</wn4:DATE_TO>
<wn4:USERID>EGREO</wn4:USERID>
</wn4:Z_APPOINTMENT_GET_JCO_ORG>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
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.
I am using portal server 2004s
Many thanks for any advice/help
Reza

I find out how should I do that.
/Reza

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

Namespace prefix: Using Anonymizer

Hi guys,
I'm having some difficulties using XMLAnonymizer for placing some namespace prefix's in my message.
After sending the message, I can check on RWB that the module Anonymizer is loaded, but results in the following:
2007-06-21 16:55:45 Success MP: processing local module localejbs/AF_Modules/XMLAnonymizerBean
2007-06-21 16:55:45 Warning Anonimizer: message is empty or has no payload
2007-06-21 16:55:45 Success MP: leaving
Well, why do I have message empty? to what message is he referring to?
Why do I need Anonymizer? Well, the thing is, some namespace prefixes are not being place on the sent message. Without this prefixes the actual mapping fails and no fields are mapped....
Can you give me a hand?

Hi Stefan,
Thanks for your reply! It works, well, the anonymizer gets the message, but now I've another question....
2007-06-22 11:04:41 Success New JMS message with JMS message ID ID:f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f1f8404040404040 received. The XI message ID for this message is fe826d20-20a7-11dc-8363-00145e1855ec
2007-06-22 11:04:41 Success JMS message converted to XI message format successfully
2007-06-22 11:04:41 Success Anonimizer: anonymizing XML ...
2007-06-22 11:04:42 Success Anonimizer: successfully anonymized
2007-06-22 11:04:42 Success Application attempting to send an XI message asynchronously using connection AFW.
2007-06-22 11:04:42 Success Trying to put the message into the send queue.
2007-06-22 11:04:42 Success Message successfully put into the queue.
I've checked my message but a strange thing happened, maybe I've misunderstood the anonymizer function....
The original message was:
So the namespaces introduced were deleted. But What I thought it was going to happen was that the Anonymizer would introduce the prefix ns0 and ns1 on the tags that had the namespace declaration.... Is this possible with the anonymizer?
Problem solved.... it was a wrong namespace :S
Thanks for the help Anonymizer does wonders and saves a hell lot of time
Message was edited by:
Gonçalo Mouro Vaz

Register namespace prefixes in JDeveloper?

Similar Messages

Maybe you are looking for