Namespace Issue

Hi All,
I am facing a strange problem while using SAX Parser to parse XML file.
My root element looks something like this
<ns:Root xmlns:ns="http://demo">
For this element in the startElement menthod at times i am getting the attributes in attributes parameter of the method. But when i run it again i am not getting anything in the attributes parameter.
This thing is totally at random. At times i get the namespace in the attributes parameter and other time i dont.
Please let me know your suggestions.
Regards

There are no attributes in that element.

Similar Messages

Java mapping & namespace issue

Hello,
I am doing a java mapping from a flat file to an IDOC. After the document is mapped succesfully I call an RFC via the Adapter. When monitoring the adapter I get the error:
com.sap.aii.af.rfc.RfcAdapterException: failed to read funtionname from XML document: missing namespace declara
so I added the namespace reference to my java mapping to look like this :
<ns0:IDOC_INBOUND_ASYNCHRONOUS xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
But when I test my java mapping in the builder (interface mapping) the namespace xmlns="urn:sap-com:document:sap:rfc:functions" is added to my above ns0:IDOC_INBOUND_ASYNCHRONOUS tag. The consequence is that while mapping in the integration engine the "ns0" prefix is then removed and I get the error:
Delivery of the message to the application using connection AFW failed, due to: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was.
Any help or sample code resolving the namespace issue is welcome.
Frank

Hi Frank,
I am getting the same error message. You fixed yours. Can you help me with mine. The error message is
" Delivery of the message to the application using connection AFW failed, due to: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was ."
I am trying to send data to SAP SRM4.0 from SAP R/3 using SAP XI. XI content is delivered by SAP.
The message is sent from R/3 to XI successfully and the XML monitor does not show any errors in XI . But the messages does not show up in SRM.
Thanks
Kishore.

Namespace issue--No target namespace in the xsd

Hi All,
Currently facing error at the time of deploying composites because of namespace issues
I have two source system XSD's without targetnamespace and both schemas are defaulted to the same namespace as xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
i am using these xsd's in bpel process as below
My Bpel processA (Using XSD-A) invoking source system with Operation A and source returns the XML content in string format and i am parsing the XML content using XSD-A. After parsing based on the business logic i am invoking Bpel process C.
After Invoking bpel process C , Bpel process A invokes Bpel process B with 3 input parameters. Now my Bpel process B invokes source system with Operation B and source returns the XML content in string format and i am parsing the XML content using XSD-B.
Now at the time of deployment i am facing issue in deploying Bpel Process-A and getting errors as *"element names are duplicated"*. In Both XSD most of the element are named as same including root element.
I am sure this happens because there is no qualifier namespace in the xsd to avoid ambiguous.
Could some one please help me in solving this issue by using same xsd without namespace
Regards,
Tarak.

Hi,
Thanks for the response
No simple solution... You will have to work this around... In your case you have the xml as string, so may you can inject a namespace there and change the XSD's accordingly...
Yes.. Its difficult to get the solution for this and more over i am not using both xsd's but using wsdl file of sever address side in reference panel which as the second XSD with same namespaces.
I tried injecting custom namespace to solve the issue but at run time i am not able to get the node values because source system giving with default namespace and in SOA i am accepting with custom targetnamespace.Because of this my xpath is not working.
Separate into two composites would be another way, but that doesn't seem to be an option...
This can be done but again one composite should reference the other one which in turn coming back to the same problem.
For Work around i have create one more service which can break the dependency between two services using xsd's of same default namespace. But i feel this is not an effective solution for designing the process.
Let me know if you strike with some work around on this.
Regards,
Tarak.

Namespace issue after updating to AIR 3.9

I am using Flash Builder 4.6. I just downloaded the new AIR SDK 3.9 and copied the files in it over a copy of Flex SDK 4.6.0 After doing this, when I create a new Flex Mobile Project, I see multiple namespace issues. Any idea what might be the issue?

Any help on this? I tried both on Mac and PC, both have same issues. When I create a new Flex Mobile project, the parent tag of the main application is Application while it should have been a ViewNavigatorApplication. The default HomeView screen created starts as:
<fx: xmlns:fx="http://ns.adobe.com/mxml/2009"
Any help on this?

Very Frustrated Namespace Issues Again !

Ok, This is crazy, I have created a freakin schema with simple string element. I then import to project. I then change message type to use this schema. I then create my bpel stuff. I then verify the wsdl and continue to get a Qname error stating it can't find the element.
Validating C:\OraBPELPM_1\integration\jdev\jdev\mywork\PreQual_Workspace1\USPSII\USPSII.wsdl
Schema element not found: QName(http://www.tnsi.com/ReadFileIn/, BatchID)
Validate WSDL: has errors.
I have no idea how to use namespace, the namespace will never be valid anywhere but internal to this application. Can someone please refer or show me what you should use as a namespace (project location or ????)
It will compile and deploy fine, its just when I use SoapScope or something to check the syntax it barfs, or if I simply ask J-Dev to verify WSDL.

Is there an address I can send you the project file so you can see... basically I have created a schema file, imported it, defined the target namespace in the schema. Then I set the input message type to use the imported schema file element. Once I verify the wsdl the imported the schema is can never find the element. This is just one of many issues with the namespacing.
I tried to keep my namespace consistent across the application but now I am getting duplicate namespace issues.
Any help would be much appreciated.

Dreamweaver Namespace issue on my web server

I am hosting my site on GoDaddy.com. I have created a site
using Dreamweaver CS3 and SQL2005. Everything works great on my
local machine, but when I upload it to the remote web server, the
aspx pages do not work. GoDaddy support says it is due to the
second line in every one of my aspx pages, specifically the
namespace attribute. From what I've read, this is automatically put
into every page created by Dreamweaver that contains an asp/asp.net
control. GoDaddy's response is to remove this line from my page and
everything will work great, which obviously it will not. I really
would not like to have to rebuild 32 + aspx pages after already
developing them in Dreamweaver. The actual line they say is causing
the problem is below:
<%@ Register TagPrefix="MM" Namespace="DreamweaverCtrls"
Assembly="DreamweaverCtrls,version=1.0.0.0,publicKeyToken=836f606ede05d46a,culture=neutra l"
%>
Does anyone have any suggestions as to how to get around this
issue?

"carrb69" <[email protected]> wrote in
message
news:[email protected]...
> Joris,
>
> I did have the dll located in a subfolder of the root
directory. I also
> put it
> in the root directory as well after receiving your
previous response and
> got
> the same results. Unfortunately, I would need to go to
GoDaddy to get the
> exact
> error because all I see when I try to access my aspx
pages is a very
> generic
> error. I had to go to GoDaddy previously to figure out
that it was the
> Namespace attribute that was causing the issue. I'll try
this evening to
> get
> them to send me the actual error message and post it
then. Thanks for the
> quick
> responses.
>
> Brian
Hi Brian,
maybe it's your browser that's hiding the error message, if
using MSIE then
please disable the "Show friendly HTTP error messages" option
in Internet
Options.
If that doesn't reveal the error message, try editing the
web.config that
dreamweaver generated for you with the following settings,
(add any missing
settings, and leave the connectionstrings that dreamweaver
has setup intact)
<configuration>
<system.web>
<compilation debug="true"/>
<customErrors mode="Off"/>
<trace
enabled="true"
traceMode="SortByCategory"
requestLimit="10"
pageOutput="false"
localOnly="false"
/>
</system.web>
</configuration>
Debug Compilation should give more insight inrto compilation
errors, which
can allso be done at the page level via<% @ Page
debug=true" %>
Custom Errors Off will disable any error pages that may be
shown in case of
an error, seting it to "emoteOnly" will only thow these page
to external
visitors, but since you are not working on the server that
actually makes
little sense.
The trace setting should enable a HTTP Handler that allows
you to view trace
information from /trace.axd in the root of your website,
enabling pageOutput
will inject the tracing information into every page, which
can allso be done
at the page level via <% @ Page trace=true" %>
There settings do have a performance impact because they are
enabled for
every request in the application, once you've got the errors
out disable
them at the application level and enable them per-page.
Hope this helps
Joris

Namespace issue while generating XML based on xsd

Hi All,
I am using Jdeveloper-11.1.1.6
SOA:- 11.1.1.6
WLS:- 11.3.6
When i am publishing xml message i am getting name space issue.
My process design as i am getting a message from AQ JMS and doing a transformation with out any logic and writing into a file based on the xsd.
Here is the my target xsd structure
<xs:schema id="RelieveIntransitSchema"
targetNamespace="http://tempuri.org/RelieveIntransitSchema.xsd"
elementFormDefault="qualified"
xmlns="http://tempuri.org/RelieveIntransitSchema.xsd"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="RelieveIntransits">
<xs:complexType>
<xs:sequence>
<xs:element name="RelieveIntransit" minOccurs="1" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="RelieveStore" minOccurs="1" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence></xs:sequence>
<xs:attribute name="StoreID" type="xs:string"/>
<xs:attribute name="Units" type="xs:double"/>
<xs:attribute name="RelieveAllStores" type="xs:boolean"/>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="HeaderID" type="xs:string" use="optional"/>
<xs:attribute name="ProductID" type="xs:string" use="required"/>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
My actual target xml should be of
<?xml version="1.0"?>
<RelieveIntransits xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://tempuri.org/RelieveIntransitSchema.xsd">
<RelieveIntransit HeaderID="DA41198901491301" ProductID="D037-63-1270S">
<RelieveStore StoreID="D001" Units="0002092 " />
<RelieveStore StoreID="D003" Units="0000022 " />
</RelieveIntransit>
</RelieveIntransits>
But the out xml generating as below which is not accepted by target system
<?xml version="1.0" encoding="UTF-8"?>
<RelieveIntransits xmlns="http://tempuri.org/RelieveIntransitSchema.xsd" xmlns:ns5="http://tempuri.org/RelieveIntransitSchema.xsd"> <ns5:RelieveIntransit ProductID="6534562" HeaderID="10R7771-6534562001-109"> <ns5:RelieveStore Units="5" StoreID="118"/>
<ns5:RelieveStore Units="5" StoreID="118"/>
</ns5:RelieveIntransit>
</RelieveIntransits>
Could some one please help me how to generate actual one as shown above with out namespace prefix "ns". I tried xsl code for removing name space prefix using https://forums.oracle.com/forums/thread.jspa?threadID=1122673 but it is removing url also.
Regards,
Tarak
Edited by: Tarak on Jul 26, 2012 11:39 AM

Hi,
Sorry for my delay response.
Both xmls are valid and equivalent for me... should be equivalent to <ns1:a xmlns:ns1="namespace"/>...
I agree to your point.
What is your target system? If that makes difference for your target system I would say it is not fully XML compliant...
Target system is an old one called as MID. Yes i agree it is not fully XML Compliant. I am publishing the message through file adapter and it is reading the file.
But anyway... The trick in the other thread should work... What do you mean by "removing url also" ???
Using the Namespaces remove xsl code i am getting structure as below. In this alone with prefix name space url also getting removed.
<RelieveIntransits>
<RelieveIntransit HeaderID="DA41198901491301" ProductID="D037-63-1270S">
<RelieveStore StoreID="D001" Units="0002092 " />
</RelieveIntransit>
</RelieveIntransits>
I am expecting like this
<?xml version="1.0"?>
<RelieveIntransits xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://tempuri.org/RelieveIntransitSchema.xsd">
<RelieveIntransit HeaderID="DA41198901491301" ProductID="D037-63-1270S">
<RelieveStore StoreID="D001" Units="0002092 " />
</RelieveIntransit>
</RelieveIntransits>

XML NameSpace Issue Confused whether it is a bug

Hi,
The issue is that the generated XML and Actual XML vary as the following: -
The namespace which is used in the Actual XML is globally used and whereas In the generated XML It is used locally wherever the corresponding element or type is used in the XML Actually, which should not happen.
I am confused whether it is a bug or an issue if this is an issue can somebody please suggest me a solution
Generated XML
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<namespace1:utilAuthenticate xmlns:namespace1="http://NAMESPACE1Services.com">
    <namespace2:ccInfo xmlns:namespace2="http://Namespace2CompanionElements.com">
        <namespace2:UKCreditCard>visa</namespace2:UKCreditCard>
        <namespace2:ccAttributes houseNo="koramangala" cardIssueNumber="321" postCode="533201" cardExpDate="01/01/2006" cardNumber="999999999999998" cardIssueDate="01/01/2005" cv2="123" cardHolderName="murali"/>
    </namespace2:ccInfo>
    <namespace2:ourReference xmlns:namespace2="http://Namespace2CompanionElements.com">reference3</namespace2:ourReference>
</namespace1:utilAuthenticate>
Actual XML
<?xml version="1.0" encoding="UTF-8"?>
<namespace1:utilAuthenticate xmlns:namespace1="http://NAMESPACE1Services.com"
    xmlns:namespace2="http://Namespace2CompanionElements.com">
    <namespace2:ccInfo>
        <namespace2:UKCreditCard>VISA</namespace2:UKCreditCard>
        <namespace2:ccAttributes cardNumber="4627851535817358"
            cardExpDate="05/08" cardHolderName="testnamecard" cv2="482"
            houseNo="75" postCode="NW1 2PL"/>
    </namespace2:ccInfo>
    <namespace2:ourReference>gm-002025004</namespace2:ourReference>
</namespace1:utilAuthenticate>The code to give the namespaces is the following line: -
schemaMarshaller.setProperty("com.sun.xml.bind.namespacePrefixMapper",new NamespacePrefixMapperImpl());
The complete code to Generate the XML is :-
Marshaller schemaMarshaller = jaxbContext.createMarshaller();
schemaMarshaller.setProperty("com.sun.xml.bind.namespacePrefixMapper",new NamespacePrefixMapperImpl());
schemaMarshaller.setProperty(Marshaller.JAXB_FORMATTED_OUTPUT, Boolean.TRUE);
schemaMarshaller.marshal(bizObj, baos);
NamespacePrefixMapperImpl is the class written by me which should implement the interface NameSpacePrefix (A JAXB Runtime Class)
And the code for the class is : -
import com.sun.xml.bind.marshaller.NamespacePrefixMapper;
class NamespacePrefixMapperImpl extends NamespacePrefixMapper {
     * This method returns prefix for a given namespace uri.
    public String getPreferredPrefix(String namespaceUri, String suggestion,
            boolean requirePrefix) {
        if ("http://gshop.eai.o2c.ibm.com".equals(namespaceUri))
            return "gshop";
        if ("http://Namespace2CompanionElements.com"
                .equals(namespaceUri))
            return "namespace2";
        if ("http://NAMESPACE1Services.com".equals(namespaceUri))
            return "namespace1";
        if ("http://www.w3.org/2001/XMLSchema".equals(namespaceUri))
            return "xs";
        return suggestion;
    public String[] getPreDeclaredNamespaceUris() {
        return new String[] {};
}Thanks in Advance for any suggestion.
Thanks
Manjith Kumar A.

Hi Suren7669,
Welcome to the Support Communities!
To resolve this issue, I would suggest updating your iOS to the latest, which is 7.0.3.
iOS 7.0.3
http://support.apple.com/kb/DL1691
iOS: How to update your iPhone, iPad, or iPod touch
http://support.apple.com/kb/HT4623
Cheers,
- Judy

Remedy Connector namespace issue

Priority of Inquiry (H/M/L): H
SR (number + severity):6457438.993+2
Product (component + version):1370+10.2.0.3.0
OS (vendor + version):46/Linux x86+2.6.9-22.ELs
Type of Assistance (Technical/Escalation/Corroboration):Technical
Details: [Well-formed details of the customer problem/inquiry; reproducible test cases; uploads of trace/log files; troubleshooting details, etc.]
Problem statement: Customer getting SOAP message error for namespace while trying to generate a ticket through remedy connector.Email notification for the same UDM is working fine but for remedy connector it throws the following errors:
2007-09-24 18:43:37,375 [DeliveryThread-JAVA1] ERROR common.intg delegateRequest.66 - [SOAPException: faultCode=SOAP-ENV:Client; msg=Root element of a SOAP message must be: 'http://schemas.xmlsoap.org/soap/envelope/:Envelope'.; targetException=java.lang.IllegalArgumentException: Root element of a SOAP message must be: 'http://schemas.xmlsoap.org/soap/envelope/:Envelope'.]

Following is the description of the process
Customer has used Remedy_DefaultCategory_LowPriority.xsl and created notification rule for the same.
Now whenever an alert is generated by our UDM, in the ?Alert_History? no details are displayed and in OMS_HOME/sysman/log/emoms.log file following error message is displayed
2007-09-24 18:43:37,375 [DeliveryThread-JAVA1] ERROR common.intg delegateRequest.66 - [SOAPException: faultCode=SOAP-ENV:Client; msg=Root element of a SOAP message must be: 'http://schemas.xmlsoap.org/soap/envelope/:Envelope'.; targetException=java.lang.IllegalArgumentException: Root element of a SOAP message must be: 'http://schemas.xmlsoap.org/soap/envelope/:Envelope'.]
Any help provided would be appreciated and would be helpful in proceeding with the mentioned issue.

BPEL namespace issues - XML inharitance

Well this time more complex issue.
I have two independent nemaspaces xmlns="FOO" and xmlns="BAR". In namespace BAR I've declared complexType BAR:B which extends FOO:A by adding new simple element xs:string. When im sending SOAP request internal error occurs form remote service, the error states that message dosen't conform XSD. And intact this is true because BPEL PM sends body of BAR:B as BAR:A (should get FOO:A).
This may sound confusing but, forces me to do nasty hack, collapsing namespaces :(.
Any ideas ?

Hi Garango,
OWS-04005 Error Returned when Generated Client and Service Classes Appear in the Same EAR File
If you generate client and Web service classes into the same directory, WebServicesAssembler might package client classes in the Web service EAR file. When you deploy the EAR file to the server, the deployment will fail with an OWS-04005 error from OracleAS Web Services:
OWS-04005 An error occurred for port: ...
For example, using Application Server Control to deploy an EAR file that contains generated client classes might return an error similar to the following:
ERROR OWS-04005 An error occurred for port: {http://ws.myservice.org/}HttpSoap11: no serializer is registered for (class org.myservice.ws.MyWebService_sayHello_ResponseStruct, {http://ws.myservice.org/}sayHelloResponse)
If an attempt to invoke this service in the Web Services Test Page, the page will respond with a diagnostic message. For example, a response message similar to the following can be displayed on the Test Page:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>env:Server</faultcode>
<faultstring>no serializer is registered for (class org.rajkovic.ws.MyWebService_sayHello_ResponseStruct, {http://ws.myService.org/}sayHelloResponse)</faultstring>
<faultactor/>
</env:Fault>
</env:Body>
</env:Envelope>
To work around this problem, generate your client and Web service classes into separate directories.
NOTE:
I request you to have a look at post on BPEL forum:
Re: BPEL Clustering
You can find more information us discussing more on BPEL clustering.
Cheers
Pucha Anirudh

CS4 namespace issues

I'm getting strange compiler errors, that seem to be CS4
getting instance variables confused with class packages.
- 'Call to a possibly undefined method addEventListener' on
var update
- 'Access of undefined property keyEquivalent in package
update.
- 'void used where a Boolean value was expected on bool =
!bool;
I'm guessing the first two issues are to do with the
classpath's being somehow screwed up...I'm not entirely sure, if my
package classpath path from CS3 is a source path, library, or
external library path in CS4. The second error sounds as if my
variable 'update:NativeMenuItem' is somehow being confused for an
'update' package I have.....which is odd.

Yeah, so if I change the variable name from update to upd, it
compiles properly in CS4. Is something broken with CS4 namespaces?
The same .fla document worked in CS3, and I'm only importing a
class within the update package. It worries me how many similar
issues I may bump into with other existing projects, as I've never
had the Document class reference package names, in a way that
conflicts with variables using the same name.
import update.UpdateManager;
var update:Object = {test:'namespace conflict'};
trace(update.test);
//1202: Access of undefined property test in package
update.

Namespace issues

I'm curious if there are known bugs in the way namespaces are handled in the current (2.1.0) beta of XSDBuilder.
For example, I have two schema, a.xsd and b.xsd.
a.xsd has no namespace. b.xsd has the namespace 'foo', and <include>s a.xsd (thus coercing the elements in a into the 'foo' namespace).
However, when trying to build() b.xsd from the Oracle XSDBuilder I will get error messages that 'Element ':bar' is not defined', where bar is defined in a.xsd and accessed in b.xsd as 'foo:bar'. It seems to be stripping off the 'foo' namespace.
This same example works with the current (1.3.0) version of the Xerces parser, so I believe that the schemas created are in fact correct and valid. (XMLSpy also validates these schemas).

Yeah, so if I change the variable name from update to upd, it
compiles properly in CS4. Is something broken with CS4 namespaces?
The same .fla document worked in CS3, and I'm only importing a
class within the update package. It worries me how many similar
issues I may bump into with other existing projects, as I've never
had the Document class reference package names, in a way that
conflicts with variables using the same name.
import update.UpdateManager;
var update:Object = {test:'namespace conflict'};
trace(update.test);
//1202: Access of undefined property test in package
update.

Namespace issue while modifying request object

Hi,
This question is about task flow created from BPM worklist. I am updating the request using iterator binding and adding new nodes in the list. I need to get this updated request object back to BPEL. When the object is returned back to BPEL, the new nodes added from ADF don't have the namespace prefixed with the tags. This is creating issue in BPEL. Jdev version 11.1.1.4.0
Is there any way in BPEL while copying / transforming the data, force to keep target variable's namespace? There is another issue where in source namespace is getting copied to target list.
Thanks
Ashwini

Hi,
You can use a xslt transformation in bpel to get the data from adf back to your namespace before you add the nodes in the list...
There's a xslt sample here...
http://stackoverflow.com/questions/3463943/changing-namespace-for-xml-file-in-xsl-translation
Cheers,
Vlad

Namespace issue in Sender JDBC message

Hi All,
My scenario is pulling data from Oracle DB(3rd party) and pushing it to SAP ECC system. Here I am using the table metadata in the form of an External Definition.I am directly using this ED in my message mapping and service interface. I am able to test the mapping locally, when I run the scenario the target message type is generated but the main element node inside is automatically suppressed. The structure examples are given as below(been taken from message mapping test tab):
Source
<?xml version="1.0" encoding="UTF-8"?>
<ns0:TABLE_NAME.resultSet xmlns:ns0="urn:sap.com:jdbcAdapter">
   <row>
      <A/>
      <BV/>
    </row>
</ns0:TABLE_NAME.resultSet>
Target:
<?xml version="1.0" encoding="UTF-8"?>
<MT_Inbound>
   <Main_Node>
      <X/>
      <Y/>
   </Main_Node>
</MT_Inbound>
I guess the problem is with the namespace and prefix which is coming along with the table metadata(ns0). I tried removing it by XML AnonymizerBean module in my sender JDBC channel but this did not solve the purpose.
Request you all to help in solving this.
Thanks in Advance
Lalitkumar.

As you should have already noticed, the structure of sender JDBC adapter does not match the meta data.
The structure of the ED imported is :
TABLE_NAME.resultSet
      TABLE_NAME.resultSet
            row
                A
                BV
The structure getting generated after polling the JDBC adapter is as given below(structure from moni inbound payload):
<?xml version="1.0" encoding="utf-8" ?>
- <TABLE_NAME.resultSet>
- <row>
<A>20110206</A>
<BV>06:38:56</BV>
</row>
I am not able to make out the difference here. I am able to also see the namespace when i check the same in the message mapping test tab.
I am also a little lost now as abhishek is on a different track.
Please comment.

XSLT namespace issue (ns0 & ns1 tags to be removed without affectng Nmespc)

Hi Friends ,
I need some help in XSLT programming.
My requirement is something like this:
<b>Input XML:</b>
<?xml version="1.0" encoding="UTF-8"?>
<ns0:GovTalkMessage xmlns:ns0="http://www.govtalk.gov.uk/CM/envelope">
     <ns0:EnvelopeVersion>2.0</ns0:EnvelopeVersion>
     <ns0:Header>
          <ns0:MessageDetails>
               <ns0:Class>IR-PAYE-EOY</ns0:Class>
               <ns0:Transformation>XML</ns0:Transformation>
               <ns0:GatewayTest>1</ns0:GatewayTest>
          </ns0:MessageDetails>
     </ns0:Header>
     <ns0:Body>
          <ns1:IRenvelope xmlns:ns1="http://www.govtalk.gov.uk/taxation/EOY/06-07/1">
               <ns1:IRheader>
                    <ns1:DefaultCurrency>GBP</ns1:DefaultCurrency>
                    <ns1:Sender>Company</ns1:Sender>
               </ns1:IRheader>
           </ns1:IRenvelope>
     </ns0:Body>
</ns0:GovTalkMessage>
<b>I want the OUTPUT xml in the following format:</b>
<?xml version="1.0" encoding="UTF-8"?>
<GovTalkMessage xmlns="http://www.govtalk.gov.uk/CM/envelope">
     <EnvelopeVersion>2.0</EnvelopeVersion>
     <Header>
          <MessageDetails>
               <Class>IR-PAYE-EOY</Class>
               <Qualifier>request</Qualifier>
               <Function>submit</Function>
               <CorrelationID/>
               <Transformation>XML</Transformation>
               <GatewayTest>1</GatewayTest>
          </MessageDetails>
     </Header>
     <Body>
          <IRenvelope xmlns="http://www.govtalk.gov.uk/taxation/EOY/06-07/1">
               <IRheader>
                    <DefaultCurrency>GBP</DefaultCurrency>
                    <Sender>Company</Sender>
               </IRheader>
           </IRenvelope>
     </Body>
</GovTalkMessage>
That is basically I need the ns0 and ns1 tags to be removed without affecting the Namespaces
Looking forward for you reply.
Best regards,
Chandan
Message was edited by:
        Chandan A C

Try this stylesheet.....and let me know if this is OK
<b><i>
<?xml version='1.0' ?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:a="http://www.govtalk.gov.uk/CM/envelope" xmlns:b="http://www.govtalk.gov.uk/taxation/EOY/06-07/1">
     <xsl:template match="/">
          <GovTalkMessage>
               <EnvelopeVersion>
                    <xsl:value-of select="a:GovTalkMessage/a:EnvelopeVersion"/>
               </EnvelopeVersion>
               <Header>
                    <MessageDetails>
                         <Class>
                              <xsl:value-of select="a:GovTalkMessage/a:Header/a:MessageDetails/a:Class"/>
                         </Class>
                         <Transformation>
                              <xsl:value-of select="a:GovTalkMessage/a:Header/a:MessageDetails/a:Transformation"/>
                         </Transformation>
                         <GatewayTest>
                              <xsl:value-of select="a:GovTalkMessage/a:Header/a:MessageDetails/a:GatewayTest"/>
                         </GatewayTest>
                    </MessageDetails>
               </Header>
               <Body>
                    <IRenvelope>
                         <IRheader>
                              <DefaultCurrency>
                                   <xsl:value-of select="a:GovTalkMessage/a:Body/b:IRenvelope/b:IRheader/b:DefaultCurrency"/>
                              </DefaultCurrency>
                              <Sender>
                                   <xsl:value-of select="a:GovTalkMessage/a:Body/b:IRenvelope/b:IRheader/b:Sender"/>
                              </Sender>
                         </IRheader>
                    </IRenvelope>
               </Body>
          </GovTalkMessage>
     </xsl:template>
</xsl:stylesheet></i></b>

Namespace Issue

Similar Messages

Maybe you are looking for