You could (depending on how urgent this is):
a) Dig into the Taglibs JSTL (standard) impl, file an enhancement request
if you're convinced enough
b) Wait for one of the jstl spec public's owners (Dhiru, Justyna, Pierre)
to respond
c) Author custom tag(s) with Java impls that suit your needs (we k
Thanks for your help, but jstl doesn't seem to work like that. Don't
know why, but you can't put namespaceprefixes in the xpath.
Rahul P Akolkar wrote:
news <[EMAIL PROTECTED]> wrote on 05/31/2005 05:52:18 AM:
I guess this is a namespace-uri issue, after lots of digging around.
Please cou
news <[EMAIL PROTECTED]> wrote on 05/31/2005 05:52:18 AM:
> I guess this is a namespace-uri issue, after lots of digging around.
>
> Please could someone explain what my xpath should be to output the
> version number of the following (atom) xml (either in JSTL or plain old
> xpath? I just can't
I guess this is a namespace-uri issue, after lots of digging around.
Please could someone explain what my xpath should be to output the
version number of the following (atom) xml (either in JSTL or plain old
xpath? I just can't get it.
http://purl.org/atom/ns#";>
Many thanks.
Digby
Digb
Hi all,
I've narrowed down the problem I had before with atom feeds not working,
and it all seems to be due to the namespace declaration in the root element:
http://purl.org/atom/ns#";>
This fails, and any x:out cannot see any elements (e.g.
$doc/feed/@version) - presumably because xpath is
