Subject: Re: Unexpected behavior with tokenize function
From: Farrukh Najmi <farrukh@xxxxxxxxxxxxxxxxxxxxx>
Date: Sat, 22 Mar 2008 10:52:51 -0400
|
Glad I am not going crazy after all ;-)
I ended up using the following to tokenize a QName into prefix component
and local-name component:
<xsl:variable name='binding-prefix'
select="substring-before(@binding, ':')"/>
<xsl:variable name='binding-local-name'
select="substring-after(@binding, ':')"/>
Thanks again Mukul for your terrific help.
Mukul Gandhi wrote:
I suspect, you are using the Xalan bundled with JDK 5. It might have
some bug, if what you are reporting is true.
With Xalan-J 2.7.1, I get the result fine.
PS: For Xalan-J specific questions, I suggest, you can join the
mailing list, xalan-j-users@xxxxxxxxxxxxxxx The instructions to
subscribe to this list are available at,
http://xml.apache.org/xalan-j/contact_us.html
On Sat, Mar 22, 2008 at 6:01 PM, Farrukh Najmi
<farrukh@xxxxxxxxxxxxxxxxxxxxx> wrote:
In my style sheet I am using the following fragment that uses the xalan
extension function named tokenize:
<xsl:for-each select="xalan:tokenize('prefix:namespace', ':')">
<token>
<xsl:value-of select="."/>
</token>
</xsl:for-each>
What I expected is the following output:
<token>
prefix
</token>
<token>
namespace
</token>
Instead what I get is:
<token>
prefixnamespace
</token>
Can anyone please clue me in to why that is happening? Thanks.
ps: Many thanks Mukul for your helpful answer to the WSDL namespace map
question. I will report back on my experience with that later.
--
Regards,
Farrukh Najmi
Web: http://www.wellfleetsoftware.com
|
Cart
