Changing / Setting Namespace Prefix in SAX

I am using sax to parse a document and I was wondering how I could change an existing namespace prefix or add one to the front of every element. I am using an XML standard called PIDX which requires each element to look like this "<pidx:ELEMENTNAME>". I know this should not be required but the standard requires it. I am familiar with using the startElement and endElment methods but I am not sure how to set a prefix. Any help or examples would be appreciated.

I recognize all of the words in the item you posted, but when I tried to parse the whole message, I got nothing.
If you are using SAX to parse a document, it is just telling you what it sees by calling the various SAX methods like startElement, etc. If the XML document should have namespaces for all elements and it doesn't, it is not the fault of SAX, but of the program that created the XML data. So, you cannot set a prefix in SAX. You can be told by SAX that it saw a prefix, and by not seeing a call, you can tell that there was no prefix.
How is the XML data generated? That is where you should first be concerned.
In this case, SAX is just the messenger telling you what is in the XML data.
Dave Patterson

Similar Messages

Changing the namespace prefix in OSB body content

I would like to change the namespace prefix of the namespace in the content of the Body in OSB (Replacing g: with dg:)
For example:
<g:Information>
<g:firtName>John<g:firstName>
<nc:date>1970-01-01<nc:date>
</g:Information>
should become
<dg:Information>
<dg:firtName>John<dg:firstName>
<nc:date>1970-01-01<nc:date>
</dg:Information>
Any idea how can I do this?

Re: Namespace replace/rename issue in ALSB
Regards,
Anuj

Setting namespace prefix with JAXB

I'm trying to build and use a JAXB application.
1. Generate the Java source files by submitting the XML Schema with Namespace to the binding compiler.
2. Compile the Java source code.
3. Marshal the data to new XML documents(valid XML document).
But namespace prefix of XML Schema doesn't equal namespace prefix of new XML document.
The prefix of new XML Schema is "heo". But, the prefix of new XML document set as "ns1" at discretion.
Is there any way to solve namespace prefix setting?
Thank you for your help.

Why is java the only one doing this?
I know prefixes are arbitrary, but when groups/individuals design XML docs, the instinct is to specify unique prefixes and to expect them coming in and out of other systems.
When joe-developer emails an API to a buddy, she's got to include a lot more info every time, not just "cool:news" vs. "bad:news" but "cool:news" and "xmlns:cool=uri-foobar-smyte" and ...
Sooo much simpler to handle the xml when its not only declared correctly, but you can expect specific prefixes. Less lines in writing tests, less lines in parsing out namespace declarations in order to expand them to uris and then map those to the random prefixes... blah.
If you are concerned about dropping uri's then THAT should be the exception to the rule, then you write tests to lookup the namespace-uri.
I suppose sun's xml stack is kind of a lesson to teach us developers to handle xml the orthodox way, using random prefixes, thanks for that.
Classic: look at the amount of code it takes to parse xml in java. Then add on complexity (weirdness) in terms of random prefixes .... then compare that to .net/python/ruby/php/perl/c/c++ ... sun is all alone on this one and about 10x more verbose.
At least honor the xml prefixes declared and developers round the world will appreciate the boost in productivity.
Word!
-jhn

How to change the Namespace of the payload

Hi,
I have 2 questions about the namespace of the XML Payload.
1. How can I change the Namespace Prefix?
Since we have SP13 the prefix is p2 with the previous Versions the prefix was p1 or p0 . Is there a possibility to change this prefix (without an external XSLT or Java Mapping)?
2. How can I change the whole Namespace?
I know the function of the Message-Type to change the namespace of the Message. But in one scenario I have to implement 3 namespace statements and 1 schema location
<ns0:ZMCFAUF1 xmlns:ns0="TDB" xmlns:xdb="http://xmlns.oracle.com/xdb" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="TDB zmcfauf1.xsd">
Is there a possibility to implement this without an external Mapping?
Thank you for your help
Thomas

Hi Thomas,
according to your first question: Why does this matter to you? As I already wrote in another thread:
According to the XML namespace declaration the prefixes are just internal aliases with no external meaning.
E.g. <ns1:abc xmlns:ns1="http://www.sap.com" /> and
<iLikeLongPrefixes:abc xmlns:iLikeLongPrefixes ="http://www.sap.com" /> are totally equivalent according to the XML namespace specification.
Therefore, everyone (human or machine) who produces a program can choose the prefixes as he wants. Moreover, he may change the rules for creating these prefixes without being incompatible.
Consequently, the namespace prefixes should not be important for you.
Greetings
Stephan

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.

How can I change namespace prefix for JAX-RPC client request?

I'm creating a JAX-RPC client to invoke a RPC/encoded web service. The service was generated from a ColdFusion program and for some reason when the SOAP namespace prefix is anything but "soapenv" it returns text/html instead of text/xml. Currently the client is sending requests with the prefix "env" and I'd like to change it to "soapenv".
I created a type of javax.xml.rpc.handler.GenericHandler and attempted to do the follow:
@Override public boolean handleRequest(MessageContext p1) {
 SOAPMessage msg = ((SOAPMessageContext) p1).getMessage();
 try {
 SOAPPart part = msg.getSOAPPart();
 SOAPEnvelope envelope = part.getEnvelope();
 envelope.setPrefix("soapenv");
 msg.saveChanges();
 } catch(SOAPException ex) {
 // TODO
 return false;
 return true;
However I get the following exception:
java.rmi.RemoteException: SOAPFaultException - FaultCode [{http://schemas.xmlsoap.org/soap/envelope/}Server] FaultString [UNIMPLEMENTED ] FaultActor [null] Detail [<detail><bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">java.lang.AssertionError: UNIMPLEMENTED
at weblogic.xml.domimpl.NodeImpl.setPrefix(NodeImpl.java:173)
at test.MyHandler.handleRequest(MyHandler.java:33)
at weblogic.wsee.handler.JaxrpcHandlerChain.handleRequest(JaxrpcHandlerChain.java:58)
at weblogic.wsee.ws.dispatch.server.JaxrpcChainHandler.handleRequest(JaxrpcChainHandler.java:102)
at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:141)
at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:107)
at weblogic.wsee.ws.dispatch.client.ClientDispatcher.dispatch(ClientDispatcher.java:132)
at weblogic.wsee.ws.WsStub.invoke(WsStub.java:87)
at weblogic.wsee.jaxrpc.StubImpl._invoke(StubImpl.java:341)
at test.Approvedsuppliers_Wrap_Stub.echo(Approvedsuppliers_Wrap_Stub.java:31)
at test.Approvedsuppliers_WrapPortClient.echo(Approvedsuppliers_WrapPortClient.java:130)
at test.Approvedsuppliers_WrapPortClient.main(Approvedsuppliers_WrapPortClient.java:43)
Is there any workaround? I appreciate any feedback.
Thanks, Bill

What I ended up doing is converting the SOAP message to a string, replacing the namespace prefix and converting it back to a SOAP message.
@Override
 public boolean handleRequest(MessageContext messageContext) {
 SOAPMessageContext soapMessageContext = (SOAPMessageContext) messageContext;
 SOAPMessage soapMessage = soapMessageContext.getMessage();
 String soapString = convertSOAPToString(soapMessage);
 soapString = soapString.replaceAll("env:", "soapenv:");
 soapString = soapString.replaceAll("xmlns:env", "xmlns:soapenv");
 SOAPMessage newSoapMessage = convertStringToSOAP(soapString);
 MimeHeaders mimeHeader = newSoapMessage.getMimeHeaders();
 mimeHeader.setHeader("SOAPAction", "");
 soapMessageContext.setMessage(newSoapMessage);
 return true;
 private String convertSOAPToString(SOAPMessage soapMessage) {
 StringWriter stringWriter = null;
 try {
 stringWriter = new StringWriter();
 StreamResult streamResult = new StreamResult(stringWriter);
 TransformerFactory transformFactory = TransformerFactory.newInstance();
 Transformer transformer = transformFactory.newTransformer();
 transformer.transform(new DOMSource(soapMessage.getSOAPPart()), streamResult);
 } catch (TransformerException e) {
 throw new RuntimeException(e);
 } finally {
 close(stringWriter);
 return stringWriter.toString();
 private SOAPMessage convertStringToSOAP(String soapString) {
 SOAPMessage soapMessage = null;
 ByteArrayInputStream byteInputStream = null;
 try {
 MessageFactory msgFactory = MessageFactory.newInstance();
 soapMessage = msgFactory.createMessage();
 SOAPPart soapPart = soapMessage.getSOAPPart();
 // Load the SOAP text into a stream source
 byte[] buffer = soapString.getBytes();
 byteInputStream = new ByteArrayInputStream(buffer);
 StreamSource source = new StreamSource(byteInputStream);
 // Set contents of message
 soapPart.setContent(source);
 } catch (SOAPException e) {
 throw new RuntimeException(e);
 } finally {
 close(byteInputStream);
 return soapMessage;
 private void close(Closeable closeable) {
 if(closeable != null) {
 try {
 closeable.close();
 } catch (IOException e) {
 // TODO

Setting Namespace for Xalan

I'm using JAXP 1.2
I have a custom sax parser (implements XMLReader) that reads csv files then sends SAX events to a stylesheet for translation. My problem is that Xalan requires a namespace-aware SAX parser. The SAXParserFactory has a method (setNamespaceAware()) which allows you to change this to "true", since the default is "false". Since I'm not using the SAXParserFactory to create my reader, I'm not sure how to set this using my custom parser. I have implemented the setFeature and getFeature by storing the values in a HashMap. See code below. I then execute the setFeature for my parser before I use the translator to set namespace to true.
csvReader.setFeature("http://xml.org/sax/features/namespace-prefixes",true);
csvReader.setFeature("http://xml.org/sax/features/namespace",true);
I'm not sure how to get Xalan to recognize these Features without creating a parser from the Factory. Any ideas?
/***************** CODE SAMPLE *****************/
private Map featureMap = new HashMap();
public boolean getFeature(String name)
throws SAXNotRecognizedException, SAXNotSupportedException {
Boolean featureValue = (Boolean) this.featureMap.get(name);
return (featureValue == null) ? false
: featureValue.booleanValue();
public void setFeature(String name, boolean value)
throws SAXNotRecognizedException, SAXNotSupportedException {
this.featureMap.put(name, new Boolean(value));
}

Here's some code I have in production:SAXParserFactory spf = SAXParserFactory.newInstance();
XMLReader reader = spf.newSAXParser().getXMLReader();
reader.setContentHandler(handler);
reader.setProperty("http://xml.org/sax/properties/lexical-handler", handler);
reader.setFeature("http://xml.org/sax/features/namespaces", true);
reader.setFeature("http://xml.org/sax/features/namespace-prefixes", false);And here's the method that produces the "handler" object:private synchronized TransformerHandler getHandler(String xslFile) throws TransformerConfigurationException {
SAXTransformerFactory factory = (SAXTransformerFactory)TransformerFactory.newInstance();
Templates t = (Templates)templates.get(xslFile);
if (t == null) {
t = factory.newTemplates(new StreamSource(new File(getServletContext().getRealPath(xslFile))));
templates.put(xslFile, t);
return factory.newTransformerHandler(t);
}This works for me. The difference is that I am using Saxon instead of Xalan to do the transformation, and possibly that is a significant difference.

BPEL SCA: XML-20129: (Error) Namespace prefix 'ui' used but not declared.

SOASuite 11g
Oracle Weblogic Server 10.3.3
Oracle Solaris on SPARC (64-bit) 10
Database: Oracle Server - Enterprise Edition 10.2.0.5
When I start the SOA domain server, I find the following in the log file:
<Feb 25, 2011 10:41:23 AM CET> <Error> <org.apache.commons.digester.Digester> <BEA-000000> <Parse Error at line 9 column 79: <Line 9,
Column 79>: XML-20129: (Error) Namespace prefix 'ui' used but not declared.
org.xml.sax.SAXParseException: <Line 9, Column 79>: XML-20129: (Error) Namespace prefix 'ui' used but not declared.
at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:422)
at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:287)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:342)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
at org.apache.commons.digester.Digester.parse(Digester.java:1785)
at oracle.fabric.composite.Parser.parseComposite(Parser.java:132)
at oracle.integration.platform.kernel.WLSFabricKernelInitializer.deployComposite(WLSFabricKernelInitializer.java:493)
at oracle.integration.platform.kernel.WLSFabricKernelInitializer.prepareCompositeDeployments(WLSFabricKernelInitializer.java:
239)
at oracle.integration.platform.kernel.WLSFabricKernelInitializer.init(WLSFabricKernelInitializer.java:127)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1976)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1950)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1869)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
My composite.xml is:
<composite name="JIPSYHandleRTOTaskEBF" revision="1.0" mode="active" state="on"
xmlns="http://xmlns.oracle.com/sca/1.0"
xmlns:ui="http://xmlns.oracle.com/soa/designer/"^M
xmlns:xs="http://www.w3.org/2001/XMLSchema">^M
<import location="GetTimeoutPeriod.wsdl" namespace="http://xmlns.oracle.com/pcbpel/adapter/db/GetTimeoutPeriod/"/>
<service ui:wsdlLocation="JIPSYHandleRTOTaskEBF.wsdl" name="client">
</composite>
But when it has been deployed, I see that this has been changed into:
<composite name="JIPSYHandleRTOTaskEBF" revision="1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<import location="GetTimeoutPeriod.wsdl" namespace="http://xmlns.oracle.com/pcbpel/adapter/db/GetTimeoutPeriod/"/>
<service ui:wsdlLocation="JIPSYHandleRTOTaskEBF.wsdl" name="client">
</composite>
(I exported this from MDS).
Apparently, some namespaces are stripped.
This appears to happen during the deploy (using ant), because the version in the generated jar file is already missing the namespaces.
The BPEL processes appear to work fine though.
Why is this happening and how can I prevent these errors?

I've fiddled around with the file composite.xml and found the following workaround:
If I change the start of the file to:
<?xml version="1.0" encoding="UTF-8"?>
<composite name="JIPSYUpdateWorkflowReqABCSImpl"
xmlns="http://xmlns.oracle.com/sca/1.0"
xmlns:ui="http://xmlns.oracle.com/soa/designer/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
revision="1.0"
mode="active"
state="on">
it remains unchanged and the errors during deployment are gone.

Changing SOAP-ENV prefix in SAAJ?

I'm using the latest webservices pack from Sun and have hit a roadblock.
We have some external clients that are relying on the SOAP messages we send them to have the prefix namespace <SOAP>. The SAAJ implementation seems to be hardcoding <SOAP-ENV>.
Is there anyway to specify/override the default SOAP namespace prefix?
i.e.
<SOAP-ENV:Envelope> --> <SOAP:Envelope>
Thanks,
- Tim

I managed to change my SOAP-ENV but the problem then is that unless you declare the namespace in every tag it add a xmlns="" to the first non specified tag.
how I changed the SOAP-ENV is as follows
SOAPPart part = msg.getSOAPPart();
//get the envelope
SOAPEnvelope envelope = part.getEnvelope();
//add the soap declaration
envelope.addNamespaceDeclaration("soap","http://schemas.xmlsoap.org/soap/envelope/");
//remove the default SOAP-ENV
envelope.removeNamespaceDeclaration("SOAP-ENV");
//Set the prefix to soap instead of SOAP-ENV
envelope.setPrefix("soap");
Mike

What is the best way to change a namespace in an xml document

Hi,
I need to change an xml namespaces. The xml has about 200 elements and every element may have a namespace attribute (namespaces are all the same).
Is there any better solution then the following function?
SQL> create or replace function change_namespace(p_xml xmltype, p_namespace varchar2) return xmltype is
2 l_doc dbms_xmldom.DOMDocument;
3 l_nodes dbms_xmldom.DOMNodelist;
4 l_node dbms_xmldom.DOMNode;
5 begin
6 l_doc:=dbms_xmldom.NewDOMDocument(p_xml);
7 l_nodes:=dbms_xmldom.getElementsByTagName(l_doc,'*');
8 for i in 0..dbms_xmldom.getlength(l_nodes)-1 loop
9 l_node:=dbms_xmldom.item(l_nodes,i);
10 if i=0 then
11 --set namespace only for the root node
12 dbms_xmldom.setattribute(dbms_xmldom.makeElement(l_node),'xmlns',p_namespace);
13 else
14 --remove all the other namespaces
15 dbms_xmldom.removeattribute(dbms_xmldom.makeElement(l_node),'xmlns');
16 end if;
17 end loop;
18
19 return dbms_xmldom.getxmltype(l_doc);
20 end;
21 /
Function created.
SQL> select change_namespace(xmltype('<a xmlns="aaa">4<c>44</c></a>'),'newnamespace')
2 from dual;
CHANGE_NAMESPACE(XMLTYPE('<AXMLNS="AAA"><BXMLNS="AAA">4<C>44</C></A>'),'NEWN
<a xmlns="newnamespace">
4
<c>44</c>
</a> Ants

Hi,
I found a better and almost 10x faster way to remove the namespaces, using xsl.
here's the original xsl with a little modifications http://bytes.com/forum/thread448445.html
SQL> with t as (select xmltype('<a xmlns="aaa">4<c>44</c></a>') xcol from dual)
2 select xmltransform(xcol
3 ,xmltype('<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" >
4 <xsl:template match="*">
5 <xsl:element name="{local-name()}" namespace="">
6 <xsl:apply-templates select="@* | node()" />
7 </xsl:element>
8 </xsl:template>
9 </xsl:stylesheet>'))
10 from t;
XMLTRANSFORM(XCOL,XMLTYPE('<XSL:STYLESHEETVERSION="1.0"XMLNS:XSL="HTTP://WWW.W3.
<a>4<c>44</c></a>+but check Laurents Schneider's blog website+
I didn't find any posts about namespace on Schneider's blog.
Ants

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?

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

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.

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

Changing / Setting Namespace Prefix in SAX

Similar Messages

Maybe you are looking for