TO parse XML having namspace using an XSLT

[jothish chokkalingam]

i m having an xml with name space

<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="process.xsl"?>
<pd :-P	 rocess 
xmlns="http://www.w3schools.com"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns :-P	 d="http://xmlns.tibco.com/bw/process/2003">

<pd:starter>
<pd:type>com.tibco.plugin.jms.JMSQueueEventSource</pd:type>
<pd:resourceType>ae.activities.JMSQueueEventSource</pd:resourceType>
<config>
<PermittedMessageType>XML Text</PermittedMessageType>
<SessionAttributes>
<maxSessions>1</maxSessions>
<destination>sample</destination>
</SessionAttributes>
<ConnectionReference>/Shared Resources/Connections/JMS/CDSEMSConnection.sharedjmscon</ConnectionReference>
<OutDataxsdString ref="pfx4:MSG_Container"/>
</config>
</pd:starter>
</pd :-P	 rocess>

and i m parsing "PermittedMessageType" using xsl

<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- Edited with XML Spy v2006 (http://www.altova.com) -->
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
 
<xsl:template match="/">
 
    <xsl:value-of select="starter/config/PermittedMessageType"/>
    
</xsl:template>
</xsl:stylesheet>

My question is how to parse xml having namespace by XSLT
Please help me regarding urgent

[Paul Clapham]

Two things you need to change: First, declare and use the http://xmlns.tibco.com/bw/process/2003 namespace in your XSLT code.

<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- Edited with XML Spy v2006 (http://www.altova.com) -->
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:pd="http://xmlns.tibco.com/bw/process/2003">
 
<xsl:template match="/">
 
    <xsl:value-of select="pd:starter/config/PermittedMessageType"/>
    
</xsl:template>
</xsl:stylesheet>

Second, remove the default namespace declaration (xmlns="http://www.w3schools.com") from your source XML, because XPath 1.0 interprets "/config/" in your example as "a config element not in a namespace" instead of as "a config element in the default namespace", which leads to its not finding any of your config elements.

I can't believe there's any point to the default namespace declaration in your example. But if there's a real business requirement for it, there are ugly ways to work around it.