Problem evaluating xpath with muliple prefix with different namespace

Subjects

•	Home
•	Xalan extension functions
•	Fomatting question serializing DOM with pretty print
•	xalan with pull parser
•	Cannot find the declaration
•	Apache Xalan drop support to run on JRE 1 1 x
•	Why does Doctype change processing of a document
•	Node set to XML string via Java extensions in Xalan J: possible?
•	Templates/Transformers + thread safety???
•	Problem evaluating xpath with muliple prefix with different namespace
•	remove an arbitrary attribute from xsl output
•	Xalan3 XSLT 2 0 XPath 2 0 support?
•	Problem using compiled translets with Xalan !!
•	Xalan and jstl 1 1 problem with transform tag
•	NullPointer in DOM2DTM getLocalName
•	URIResolvers base parameter with xsltc and cascaded imports
•	Performance problem for Xalan J on intel dual core
•	Standard libraries in JAXP?
•	Serializing a DOM tree to XML file, customize entities replacement
•	Library Conflict Involving BCEL Library
•	A question on how users are using <xsl:message >
•	Kevin Cormier as a new Apache Xalan J committer
•	Struggling to iterate over tokenized string
•	Xalan count() trouble
•	Problem with recursive xpath
•	Error when switching to java 1 5
•	document( ' ')
•	Problem with Xalan2 7 0 transformation
•	cr/lf options
•	entity encoded XML
•	can xalan transform 2 xml using one xslt?
•	Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
•	xsl transform with cdata section elements
•	xslt parameters not expanded
•	Weird behavior of XPath evaluate()
•	How to avoid <xsl:message > instruction prints stylesheet file informations ?
•	Cannot find SimpleTransform subdirectory after installing Xalan J
•	recover from document not found exceptions
•	jdk1 5 and Xalan jar differences?
•	Performance Issue
•	Error/Bug adding floating point numbers
•	XPathAPI: eval exp using nodes with default namespace
•	modifying xalan to output invalid XML
•	NullPointerException
•	mege two separate xml nodes into one
•	Is this a XALAN document identification bug?
•	is StylesheetRoot really java io Serializable ?
•	transform() fails for DOMSource but succeeds for StreamSource
•	Thoughts on Transformer parameter passing
•	HELP, Xalan and jstl 1 1 problem with transformer
•	Problem with XPath namespace axis?
•	string utils:replace deleting search string if replacement string is an HTML
•	help with enumeration values pls
•	xalan 2 5 1 vs 2 7 performance question
•	How to insert/update in XML document
•	HTML Serialization and Handling of Ampersands in HREF Attributes
•	XHTML link tag stripping
•	SystemId Unknown; Line #24; Column #49; java lang NullPointerException
•	xpath text() help
•	Apostrophe problem with xalan 2 7 0
•	How to set variables in XML document?

Links

Home

Oracle database error code ...

Problem evaluating xpath with muliple prefix with different namespace

Problem evaluating xpath with muliple prefix with different namespace

2007-07-09 - By Erin Harris

Reply: 1 2 3 4 5 6

Hi,

I found two problems in the stylesheet.

The first is with the following line:

<xsl:element name="buybiz:postBuy" namespace="{$bizServiceNameSpace}"
xmlns:mod="{$intModelNameSpace}">

In the XSLT 1.0 Specification, 7.6.2 Attribute Value Templates (
http://www.w3.org/TR/xslt#attribute-value-templates) it says:

NOTE:Not all attributes are interpreted as attribute value templates.
Attributes whose value is an expression or pattern, attributes of
top-level elements and attributes that refer to named XSLT objects are not
interpreted as attribute value templates. In addition, xmlns attributes
are not interpreted as attribute value templates; it would not be
conformant with the XML Namespaces Recommendation to do this.

So xmlns:mod="{$intModelNameSpace}" is just treated as a string value and
is not evaluated as an AVT.

Since there is a variable declaration: <xsl:variable
name="intModelNameSpace">http://schemas.xxx.com/model</xsl:variable>, I
tried replacing xmlns:mod="{$intModelNameSpace}" with
xmlns:mod="http://schemas.xxx.com/model" but that did not work either
because now in the stylesheet the prefix mod is bound to the namespace
http://schemas.xxx.com/model, but in the xml input document the prefix mod
is bound to http://ws.xxx.com/2007/06/model so there is no match. So I
tried just removing that namespace declaration so that:

<xsl:element name="buybiz:postBuy" namespace="{$bizServiceNameSpace}"
xmlns:mod="{$intModelNameSpace}">

becomes:

<xsl:element name="buybiz:postBuy" namespace="{$bizServiceNameSpace}">

and then everything works.

If you need that namespace declaration for some reason (though it didn't
look like it was being used) then you can do something like this:

<xsl:element name="buybiz:postBuy" namespace="{$bizServiceNameSpace}"
xmlns:mod="http://schemas.xxx.com/model" xmlns:modtarget="
http://ws.xxx.com/2007/06/model">

...

<xsl:with-param name="cat"
select="serviceBusMessage/payload/buytypes:postLiveBuyRequest/buytypes:liveBuy
/buytypes:category/modtarget:catName"/>

....

<xsl:with-param name="subcat"
select="serviceBusMessage/payload/buytypes:postLiveBuyRequest/buytypes:liveBuy
/buytypes:category/modtarget:subCatName"/>

Note that the XSLT processor uses the namespace bound to the prefix to
match nodes in the xml input document and not the prefix name itself.

Thanks.

Erin Harris

laxman <lchandramouli@(protected)>
06/07/2007 03:59 PM

To
xalan-j-users@(protected)
cc

Subject
Re: Problem evaluating xpath with muliple prefix with different namespace

Hi,

I edited the xml and renamed the xsl for convinence.

Thanks

laxman wrote:
>
> Hi Erin,
>
> Thanks for the reply I am working with Xalan Java 2.7.0 and jdk
> 1.4.2_08
>
> I am attaching the xsl and the input xml. Not sure what the exact
> problem is.
>
> Thanks
>
> http://www.nabble.com/file/p11470588/P1.xsl P1.xsl
>
> http://www.nabble.com/file/p11470588/2.xml 2.xml
>

--
View this message in context:
http://www.nabble.com/Problem-evaluating-xpath-with-muliple-prefix-with
-different-namespace-tf4036498.html#a11471552

Sent from the Xalan - J - Users mailing list archive at Nabble.com.

 Hi,
 
 I found two problems in the stylesheet.
 
 The first is with the following line:
 
 <xsl:element name="buybiz:postBuy
"
namespace="{$bizServiceNameSpace}" xmlns:mod="{
$intModelNameSpace}">
 
 In the XSLT 1.0 Specification, 7.6.2
Attribute Value Templates (<a href="http://www.w3.org/TR/xslt#attribute
-value-templates">http://www.w3.org/TR
/xslt#attribute-value-templates</a>)
it says:
 
 NOTE:Not all attributes are interpreted as attribute
value templates. Attributes whose value is an expression or pattern, attributes
of <a href="http://www.w3.org/TR/xslt#dt-top-level">top-level</a>
elements and attributes that refer to named XSLT objects are not interpreted
as attribute value templates. In addition, <tt>xmlns
</tt>
attributes are not interpreted as attribute value templates; it would not
be conformant with the XML Namespaces Recommendation to do this. 
 
 So xmlns:mod="{$intModelNameSpace}
"
is just treated as a string value and is not evaluated as an AVT.
 
 Since there is a variable declaration:
<xsl:variable name="intModelNameSpace">http://schemas.xxx
.com/model</xsl:variable>,
I tried replacing xmlns:mod="{$intModelNameSpace}" with
xmlns:mod="http://schemas.xxx.com/model" but that did
not work either because now in the stylesheet the prefix mod is
bound to the namespace http://schemas.xxx.com/model, but in the
xml input document the prefix mod is bound to http://ws.xxx.com/2007
/06/model
so there is no match.  So I tried just removing that namespace declaration
so that:
 
     <xsl:element name=&quot
;buybiz:postBuy"
namespace="{$bizServiceNameSpace}" xmlns:mod="{
$intModelNameSpace}">
 
 becomes:
 
     <xsl:element name=&quot
;buybiz:postBuy"
namespace="{$bizServiceNameSpace}">
 
 and then everything works.
 
 If you need that namespace declaration
for some reason (though it didn't look like it was being used) then you
can do something like this:
 
     <xsl:element name=&quot
;buybiz:postBuy"
namespace="{$bizServiceNameSpace}" xmlns:mod="http://schemas.xxx
.com/model"
xmlns:modtarget="http://ws.xxx.com/2007/06/model">
 
     ...
 
     <xsl:with-param name=&quot
;cat"
select="serviceBusMessage/payload/buytypes:postLiveBuyRequest/buytypes
:liveBuy/buytypes:category/modtarget:catName"/>
 
     ....
 
     <xsl:with-param name=&quot
;subcat"
select="serviceBusMessage/payload/buytypes:postLiveBuyRequest/buytypes
:liveBuy/buytypes:category/modtarget:subCatName"/>
 
 
 Note that the XSLT processor uses the
namespace bound to the prefix to match nodes in the xml input document
and not the prefix name itself.
 
 
 Thanks. 
 
Erin Harris 
 

 
 
 
<table width=100%>
<tr valign=top>
<td width=40%>laxman <lchandramouli@(protected)
.com>

06/07/2007 03:59 PM
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right>To</div>
<td>xalan-j-users@(protected)
<tr valign=top>
<td>
<div align=right>cc</div>
<td>
<tr valign=top>
<td>
<div align=right>Subject</div>
<td>Re: Problem evaluating xpath with muliple
prefix with different namespace</table>
 
<table>
<tr valign=top>
<td>
<td></table>
 </table>
 
 
 <tt> 
Hi, 
 
  I edited the xml and renamed the xsl for convinence. 
 
Thanks 
 
 
 
laxman wrote: 
> 
> Hi Erin, 
> 
>     Thanks for the reply I am working with Xalan Java 2.7.0
and jdk 
> 1.4.2_08 
> 
>    I am attaching the xsl and the input xml. Not sure what
the exact 
> problem is. 
> 
> Thanks 
> 
>  http://www.nabble.com/file/p11470588/P1.xsl P1.xsl 
> 
>  http://www.nabble.com/file/p11470588/2.xml 2.xml 
> 
 
-- 
View this message in context: http://www.nabble.com/Problem-evaluating-xpath
-with-muliple-prefix-with-different-namespace-tf4036498.html#a11471552 
Sent from the Xalan - J - Users mailing list archive at Nabble.com. 
 
</tt>