Hi reshmi,
That s right. To use the grid am not using JSTL. Am
using EL. For now its ok. But am sure the problem will arise in the
future.
You can create multiple projects with the same instance of Tomcat.
Each project can have it's own web.xml with separate Servlet
I just wanted to be clear, this is the web.xml located under your project---
/WEB-INF/web.xml
-Rashmi
On 4/29/07, Rashmi Rubdi [EMAIL PROTECTED] wrote:
Since you are using Tomcat 5.5.x please make sure the web-app node
web.xml is exactly as follows:
?xml version=1.0
web-app version=2.4
Rashmi Rubdi wrote:
On 4/29/07, Martin Cooper [EMAIL PROTECTED] wrote:
Like I said before, make sure your web.xml file is referencing
Servlets 2.4or later. You can have all the latest software, but if
your
web.xml file is referencing an earlier version of the spec, it won't
make
any
On 4/29/07, venu madhav [EMAIL PROTECTED] wrote:
Rashmi,
I understood what you are saying. I want to make clear
that there is no wrong in my web.xml .
Hi Venu,
Just to be clear, please elaborate on what you mean by there is no
wrong in my web.xml , it would be helpful if you
Rashmi Rubdi wrote:
On 4/29/07, venu madhav [EMAIL PROTECTED] wrote:
Rashmi,
I understood what you are saying. I want to make clear
that there is no wrong in my web.xml .
Hi Venu,
Just to be clear, please elaborate on what you mean by there is no
wrong in my web.xml , it
Hi Venu,
I was able to solve this error, please see the explanation below.
I too got this error:
org.apache.jasper.JasperException: /p/datagrid/index.jsp(475,0)
According to TLD or attribute directive in tag file, attribute items
does not accept any expressions
when I tried example1.jsp from
Rashmi Rubdi wrote:
Hi Venu,
I was able to solve this error, please see the explanation below.
I too got this error:
org.apache.jasper.JasperException: /p/datagrid/index.jsp(475,0)
According to TLD or attribute directive in tag file, attribute items
does not accept any expressions
when I
On 4/29/07, venu madhav [EMAIL PROTECTED] wrote:
Hi Rashmi,
Thank you very much for providing me the solution.
So , we can conclude that the taglib was written using old spec and it
was not updated isn't it.
Any way thanks once again for solving my problem. Have a nice day.
Rashmi Rubdi wrote:
On 4/29/07, venu madhav [EMAIL PROTECTED] wrote:
Hi Rashmi,
Thank you very much for providing me the solution.
So , we can conclude that the taglib was written using old spec and it
was not updated isn't it.
Any way thanks once again for solving my
Hi,
I tried to use the datagrid tags provided by apache. I found a code
segment
like ui:dataGrid items=${alist}. But this is not working for me. bcoz the
items attribute in gridtaglib is not accepting runtime expressions. please
provide the correct usage of your grid taglibs. ?
--
Regards,
Rashmi Rubdi wrote:
Hi Venu,
What version of JSTL are you using?
This might be a configuration issue, according to the documentation here:
http://jakarta.apache.org/taglibs/sandbox/doc/datagrid-doc/index.html#requirements
This custom tag library requires a servlet container that supports
Rashmi Rubdi wrote:
Again, what version of JSTL ?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Am using JSTL1.1
--
Regards,
Venu madhav.Yelamanchili
Software Trainee
It appears to me that Datagrid requires JSTL 1.0 and JSP 1.2 from
reading the thread below. This means that unless you can patch
Datagrid yourself or wait for the bug to be patched , you'll have to
downgrade a few things like JSTL jar file, Web Container that supports
JSP 1.2.
http://mail
On 4/28/07, Venu Madhav.Yelamanchili [EMAIL PROTECTED] wrote:
Rashmi Rubdi wrote:
Hi Venu,
What version of JSTL are you using?
This might be a configuration issue, according to the documentation
here:
http://jakarta.apache.org/taglibs/sandbox/doc/datagrid-doc/index.html#requirements
I'm sorry for mentioning a conflicting configuration of JSP, JSTL in
my post above.
The latest nightly release of DataGrid was on 20060829, which is much
more recent than the thread I referred to above which was dated on
2004. So, please ignore my replies above.
With very limited information of
Like I said before, make sure your web.xml file is referencing
Servlets 2.4or later. You can have all the latest software, but if
your
web.xml file is referencing an earlier version of the spec, it won't make
any difference.
--
Martin Cooper
On 4/28/07, Venu Madhav.Yelamanchili [EMAIL
Please see bug:
http://issues.apache.org/bugzilla/show_bug.cgi?id=36586
for more details. This definitely is affecting JSTL
and Session tag libs. I have not looked through the
source for the others.
Thanks,
Wade
Your crusade would do better to advocate fixing the issue in Tomcat, IMO,
and therefore voting for the Tomcat bug instead (or in addition).
--
Martin Cooper
On 9/13/05, Wade Chandler [EMAIL PROTECTED] wrote:
Please see bug:
http://issues.apache.org/bugzilla/show_bug.cgi?id=36586
--- Martin Cooper [EMAIL PROTECTED] wrote:
Your crusade would do better to advocate fixing the
issue in Tomcat, IMO,
and therefore voting for the Tomcat bug instead (or
in addition).
--
Martin Cooper
On 9/13/05, Wade Chandler
[EMAIL PROTECTED] wrote:
Please see bug:
http
, but essentially stupid wrt the
jsp spec and tag pooling. So it turns out that tags that extend
BodyTagSupport and make use of bodyContent are likely to suffer from
bodyContent objects that have old body content in their buffers.
Realising that I'm not going to patch tomcat (yes that bug claims
to to be in 100% compliance with
an external interface specification, but the interface works without
the CDATA wrapper, so I'm in the clear for now.
Is this a real bug, or have I missed something obvious?
Regards,
Malcolm
Can now confirm (after some small dependency hell) that the bug exists
with the older version of dom4j. Upgrading to 1.5.2 has fixed the
problem.
The upgrade introduced some new dependencies (new to me anyway!). In
addition to dom4j-1.5.2.jar, I also needed:
jaxen-core.jar
jaxen-dom4j.jar
to remove these
CDATA wrappers in order to work around the problem. The reason for
their inclusion in the first place to to be in 100% compliance with
an external interface specification, but the interface works without
the CDATA wrapper, so I'm in the clear for now.
Is this a real bug
Hi,
I am used to accessing form and URL parameters from JSTL using
${param.something}.
However, I've found if a form is enctype=multipart/form-data then the
parameters defined within the form tags are not accessible.
Say if I had a form field that was type=text (or hidden) then the value is
-Original Message-
From: Andrew Stevens [mailto:[EMAIL PROTECTED]
Sent: Sunday, April 18, 2004 11:13 PM
To: '[EMAIL PROTECTED]'
Subject: ${param.something} ... feature or bug?
Hi,
I am used to accessing form and URL parameters from JSTL using
${param.something}.
However
But would this work?
fmt_rt:formatDate value=${row.TIME}
timeZone=%= Constants.TIMEZONE %
pattern=dd-MM- 'at' HH:mm/
I'm using both rt and EL in the same tag ?
No. It is one or the other. Cannot mix within the same action.
However, you can mix both EL-
PROTECTED]
Sent: woensdag 25 februari 2004 8:18
To: Tag Libraries Users List
Subject: RE: JSTL fmt:formatDate bug ???
Could you post the code to manually format the date?
I can easily compare that to what is being done by
the JSTL implementation and give you some feedback
fmt:formatDate bug ???
Could you post the code to manually format the
date?
I can easily compare that to what is being done
by
the JSTL implementation and give you some
feedback
on that.
Something to the extend of:
static
{
SimpleDateFormatter sdf = new
confusing and illogical to work with, but
that's just my personal frustration.
Martin
-Original Message-
From: Riaan Oberholzer [mailto:[EMAIL PROTECTED]
Sent: woensdag 25 februari 2004 10:48
To: Tag Libraries Users List
Subject: RE: JSTL fmt:formatDate bug ???
I'm a bit lost here
List
Subject: RE: JSTL fmt:formatDate bug ???
I'm a bit lost here can you give me an example
of
what I should give to jstl to print the time as
Europe/London ?
Thanks
Charl
--- Martin van Dijken [EMAIL PROTECTED]
wrote:
Hey Riaan,
Try fiddling around
...
please help me to resolve the above problem with some Examples.
R.Sreekant
-Original Message-
From: Martin van Dijken [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 25, 2004 4:39 PM
To: 'Tag Libraries Users List'
Subject: RE: JSTL fmt:formatDate bug ???
Try
12:17
To: Tag Libraries Users List
Subject: RE: JSTL fmt:formatDate bug ???
fmt:setLocale value=nl_NL/
fmt:formatDate value=${obj}
timeZone=Europe/London type=time/
I want to keep the language english... possible? IE,
say that we are in The Netherlands, but work in
English
On 02/25/2004 12:16 PM Riaan Oberholzer wrote:
fmt:setLocale value=nl_NL/
fmt:formatDate value=${obj}
timeZone=Europe/London type=time/
I want to keep the language english... possible? IE,
say that we are in The Netherlands, but work in
English ... otherwise it will try to locate Dutch
resource
I know that in fmt:message there is a deficiency
which means that date
formatting of parameters to the message does not
happen.
I'm using the latest version, 1.0.5, released on
January 27 pretty much up to date.
Don't worry about not having Dutch resource bundles.
OK, good to hear
[mailto:[EMAIL PROTECTED]
Sent: woensdag 25 februari 2004 10:48
To: Tag Libraries Users List
Subject: RE: JSTL fmt:formatDate bug ???
I'm a bit lost here can you give me an example
of
what I should give to jstl to print the time as
Europe/London ?
Thanks
Charl
fmt:formatDate bug ???
I'm a bit lost here can you give me an example
of
what I should give to jstl to print the time as
Europe/London ?
Thanks
Charl
--- Martin van Dijken [EMAIL PROTECTED]
wrote:
Hey Riaan,
Try fiddling around with setting the locale in
JSTL
PROTECTED]
Sent: woensdag 25 februari 2004 10:48
To: Tag Libraries Users List
Subject: RE: JSTL fmt:formatDate bug ???
I'm a bit lost here can you give me an example
of
what I should give to jstl to print the time as
Europe/London ?
Thanks
Charl
--- Martin
Aadi,
Which version of Tomcat 5 are you running it? I just ran the code below
on Tomcat 5.0.16 (and JSTL 1.1.0) and it worked fine:
%@ taglib prefix=c uri=http://java.sun.com/jsp/jstl/core; %
% request.setAttribute( pqParams, new java.util.HashMap(3) ); %
c:set target=${requestScope.pqParams}
List
Subject: RE: JSTL fmt:formatDate bug ???
I'm a bit lost here can you give me an example
of
what I should give to jstl to print the time as
Europe/London ?
Thanks
Charl
--- Martin van Dijken [EMAIL PROTECTED]
wrote:
Hey Riaan,
Try fiddling around with setting the locale in
JSTL
Thanks Felipe,
It turned out to be a timing issue between 2 machines and code never
recompiled. I blew away the work directory and started anew and it was
all good.
-a
Felipe Leme wrote:
Aadi,
Which version of Tomcat 5 are you running it? I just ran the code below
on Tomcat 5.0.16 (and JSTL
-Original Message-
From: Riaan Oberholzer
[mailto:[EMAIL PROTECTED]
Sent: woensdag 25 februari 2004 10:48
To: Tag Libraries Users List
Subject: RE: JSTL fmt:formatDate bug ???
I'm a bit lost here can you give me an
example
of
what I should give to jstl to print
, it is correct again. Ie, I
enter a time as 15:00, it shows in the DB as
16:00, but JSTL shows it as 14:00. Formatting
'manually' shows the correct 15:00 time.
Is this a bug? Or is there something else I need to do
to get this right?
Thanks
__
Do you Yahoo!?
Yahoo! Mail
: Riaan Oberholzer [mailto:[EMAIL PROTECTED]
Sent: dinsdag 24 februari 2004 22:18
To: [EMAIL PROTECTED]
Subject: JSTL fmt:formatDate bug ???
I have an application that runs in The Netherlands,
but is operated from England. Date/times are thus
stored and converted with a dateformatter set
Could you post the code to manually format the date?
I can easily compare that to what is being done by
the JSTL implementation and give you some feedback
on that.
Something to the extend of:
static
{
SimpleDateFormatter sdf = new
SimpleDateFormatter(-MM-dd HH:mm);
. Is this a known bug, or am I using the tag
incorrectly?
- Jim
__
James Watkin
ACIS Software Development
The Anderson School at UCLA
[EMAIL PROTECTED]
Voice: 1-310-825-5030
Fax: 1-310-825-4835
}someDefaultValue/c:out/td
I get weird results. The default value appears in all of the tds, not
just the one I've specified. Is this a known bug, or am I using the tag
incorrectly?
- Jim
__
James Watkin
ACIS Software Development
The Anderson School at UCLA
[EMAIL
I've been working with the transform tag and may have possibly
encountered a bug, shouldn't it be possible to do the following?
x:transform xml=${xml} xslt=${xslt}
c:forEach var=current items=${param}
x:param name=${current.key} value=${current.value}/
/c:forEach
/x:transform
-Mark
Has anyone addressed this bug yet?
robert
-Original Message-
From: Robert Taylor [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 12, 2002 11:58 AM
To: Tag Libraries Users List
Subject: RE: String TagLib 1.0 wordWrap
StringIndexArrayOutOfBoundsException
Okay. I entered it as a bug
No worries. Thanks for a very useful tag library!
robert
-Original Message-
From: Henri Yandell [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 28, 2003 5:41 PM
To: Tag Libraries Users List
Subject: Re: FW: String TagLib 1.0 wordWrap
StringIndexArrayOutOfBoundsException (Bug#15321
Nope. I'll get on it now. Sorry about that.
Hen
On Tue, 28 Jan 2003, Robert Taylor wrote:
Has anyone addressed this bug yet?
robert
-Original Message-
From: Robert Taylor [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 12, 2002 11:58 AM
To: Tag Libraries Users List
Subject
Okay, was an odd bug :) It occured on the 80th, 155th, 259th, 497th,
591st... element. Which might just be dependent on the random string i was
throwing into it.
Anyways, I've protected against it, and after I commit it'll go into
tonight's nightly build. I've only tested the underlying Java
-examples webapp that ships
with the release.
-- Pierre
Pier Fumagalli wrote:
Not acked.
Pier
-- Forwarded Message
From: [EMAIL PROTECTED]
Date: Thu, 23 Jan 2003 12:36:05 +0530
To: [EMAIL PROTECTED] [EMAIL PROTECTED]
Subject: BUg in forEach tag of JSTL
Hi,
i am using
Is there a bug in Tomcat 4.1 when working with taglibs?
First the good news: I have JSP pages using Jakarta taglibs (input, dbtags
and application) in a web application webAppA (running on Tomcat 4.1). It
works fine. So http://servername:port/webAppA/jspWithTags.jsp in a browser
works fine.
Bad
Oops .. correction
In second para, the URL is http://servername:port/webAppB/jspWithTags.jsp
-Original Message-
From: Rajendra Paul [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 19, 2002 12:50 PM
To: '[EMAIL PROTECTED]'
Subject: Taglib bug in Tomcat 4.1?
Is there a bug
Hi,
I'd like to post this to the mailing list to see if
I'm making a mistake or it's a know problem before I
add it to the bug database.
Ref: DBTAGS taglib displaying request SQL when second
request on the same page returns no results.
Please consider the following section of JSP
attribute value. I looked in the JSTL spec and it looks
like the first should work.
Is this a bug?
No, the behavior is as expected.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto
value=${requestScope[value]}/
and
%= request.getAttribute(value) %
The first is returning null and the second is returning the appropriate
attribute value. I looked in the JSTL spec and it looks like the first
should work.
Is this a bug?
Thanks.
Scott
--
To unsubscribe, e-mail
attribute value. I looked in the JSTL spec and it looks like the first
should work.
Is this a bug?
Thanks.
Scott
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL
.
If you added
pageContext.setAttribute(foo, foo);
to the upper scriptlet, then the code would be identical.
The first is returning null and the second is returning the
appropriate attribute value. I looked in the JSTL spec
and it looks
like the first should work.
Is this a bug
attribute value. I looked in the JSTL spec and it looks like the first
should work.
Is this a bug?
Thanks.
Scott
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
On Thu, 21 Nov 2002, Scott Goldstein wrote:
I'm not sure that I follow. How about these two snippets:
%
String value = foo;
%
c:out value=${requestScope[value]}/
and
c:out value=${requestScope[foo]}/
The second one works, while the first doesn't.
Yes. Again, this is
Johann Uhrmann wrote:
Is that a known bug, am I doing something stupid, is there any solution?
Hi!
Are you using Tomcat 4.1.x? Then disable tagpooling in
$CATALINA_HOME/conf/web.xml, by setting tagPooling to false. That worked
for me, but unfortunally it doesn't solves the issue only
Hello,
is there anything known about a bug in the fmt-part of jstl?
The following code causes the strange behaviour:
% page language=java %
% taglib prefix=c uri=http://java.sun.com/jstl/core; %
% taglib prefix=fmt uri=http://java.sun.com/jstl/fmt; %
fmt:setBundle basename=WebResource
i've got an utf-8 encoded xml file (test.xml) with several versions of an
umlaut character, like
this:
?xml version=1.0 encoding=UTF-8?
aü #x00FC;/a !-- this should both be equivalent to uuml; --
i want to apply a simple xsl transformation (test.xml) to html, like this:
?xml version=1.0
It shouldn't work; a.get(b) is not supported in any form by the JSTL
1.0 expression language, whether in c:out or elsewhere. JSP 2.0
will introduce functions that could conceivably be mapped to such a
method, though only through a static wrapper that would cause the
expression to look more
So you're telling us that referencing ${item.a_nomefile} in a
c:out tag, where item is an instance of DynaActionForm
no, I'm using struts 1.02, I don't know anything about DynaActionForm but I use
DynaBeans
to store resultsets output, I was able to iterate the collection with JSTL and display
On Tue, 29 Oct 2002, flare wrote:
My only point was that if an expression works in c:param, it will
also work in c:out. You made a claim otherwise, and I wanted you to
confirm it since it sounded wrong.
I was able to use dynabeans in out and fmt tags but not in param,
that's strange I
On Tue, 29 Oct 2002, flare wrote:
I was able to use dynabeans in out and fmt tags but not in param,
that's strange I know .. since I should to use the code in production
I hope next releases of JSTL won't break the compatibility with the
clean but (now I guess) unsupported format I'm using !
On Tue, 29 Oct 2002, flare wrote:
I'm using latest stable Apache JSTL Implementation on Resin 2.1.5
Are you sure you're not using Resin's JSTL implementation? See
http://www.caucho.com/news/2002-06-12.xtp
for more information.
--
Shawn Bayern
JSTL in Action http://www.jstlbook.com
--
their
implementation because I removed the jars and the page worked fine ;)
So that's a Resin bug of feature.. sorry about the confusion I've to read the release
notes
next time
--
To unsubscribe, e-mail: mailto:taglibs-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail
No, it shouldn't. One possible difference is that you're using
c:out from Resin's implementation of JSTL and c:param from the
Standard Taglib.
Exactly, It seems the Resin jstl support is partial, if such a tag is available Resin
is used, if
not the container searches in the classpath and
On Sun, 27 Oct 2002, flare wrote:
Irrespective of whether you're using DynaBeans or not, if it works in
the latter case, it should work in the former one. That is, the two
expressions you've shown are identical, and both tags evaluate their
attributes as String objects.
c:forEach var=item
On Mon, 28 Oct 2002, flare wrote:
c:forEach var=item items=${requestScope.asteAllegati} varStatus=status
c:url value=/showAllegati.do var=show
c:param name=id value=${requestScope.id}/
c:param name=tipo value=${requestScope.tipo} /
c:param name=key value=${item.a_nomefile} /
/c:url
I'm not really familiar with DynaBeans and how they work. My point is
just that if
dynabeans are not javabeans , since they've dynamic properties you should access them
using bean.get(property) instead of bean.getProperty()
The jstl out tag supports this method of invocation, perhaps
.
-Original Message-
From: flare [mailto:flare;flare.it]
Sent: Monday, October 28, 2002 1:05 PM
To: Tag Libraries Users List
Subject: Re: JSTL BUG? Url problem
On Sun, 27 Oct 2002, flare wrote:
Irrespective of whether you're using DynaBeans or not, if
it works in
the latter case
=${requestScope.tipo}/key=c:out value=${item.a_nomefile} /'
is that a bug or simply dynabens cannot be used that way?
Thanx
--
To unsubscribe, e-mail: mailto:taglibs-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:taglibs-user-help;jakarta.apache.org
On Sun, 27 Oct 2002, flare wrote:
c:param name=key value=${item.a_nomefile} /
[...]
a href='showAllegati.do?id=c:out value=${requestScope.id}/tipo=c:out
value=${requestScope.tipo}/key=c:out value=${item.a_nomefile} /'
is that a bug or simply dynabens cannot be used that way
On Thu, 17 Oct 2002, peter lin wrote:
we did verify acookie exists. I should have been more clear in my
original email.
That's not really the issue; the question is what's causing the error
logs that you're suggesting are indicative of a bug. Since the Standard
Taglib simply results
suggesting are indicative of a bug. Since the Standard
Taglib simply results 'acookie.value' into a call to getValue() of your
Cookie, it seems unlikely that the problem lies with the Standard Taglib,
unless I'm misunderstanding your report.
shouldn't JSTL throw an exception, since acookie
I wrote a basic test page and this is the result I get.
output
print out the classname
java.util.HashMap$Entry
java.util.HashMap$Entry
java.util.HashMap$Entry
print out the cookie
id1=value_for_id1
JSESSIONID=1B6A8CE1F51A31E335719420A239BEB2
to Cookie instances.
So, in the context of the test page, where does the bug come up?
--
Shawn Bayern
JSTL in Action http://www.jstlbook.com
--
To unsubscribe, e-mail: mailto:taglibs-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:taglibs-user-help;jakarta.apache.org
. with is why the subject says maybe
:)
if you think it's a jasper bug, I will consult tomcat-dev and
investigate further. thanks.
peter
Shawn Bayern wrote:
On Thu, 17 Oct 2002, peter lin wrote:
It looks like using c:out value=${acookie.name}/ won't retrieve
the value, since acookie is a hashentry
or wrong, I expect the EL to realize duh,
that's the wrong syntax silly pete. I'm throwing an exception.
when I have time, I'll try to verify jstl 1.0.2 with 4.0.6 and see if
has the same effect. If it doesn't cause continuous logging, it's
probably a bug in tomcat. The funny thing is the page compiles
On Fri, 18 Oct 2002, peter lin wrote:
it's only when the syntax is incorrect that it doesn't throw an
exception like symbol cannot be resolved, clascastexception or
some other exception. Right or wrong, I expect the EL to realize
duh, that's the wrong syntax silly pete. I'm throwing an
I'm glad your just as confused as I am, since I honestly don't know
either :)
I was hoping you'd have the magic answer, but looks like I'll have to
dig around this weekend to figure what the exact cause is. thanks for
responding to my obtuse questions, since I'm confused as to why this
behavior
On Tue, 14 May 2002, Liam wrote:
this is out code snippet
%
ArrayList classifiers = Classifier.DA.getAll();
%
c:forEach var=classifier items=$classifiers varStatus=status
Two problems:
- The syntax for expressions is now ${expr}, not $expr. You need to
write ${classifiers}.
-
Hello,
Why is the address variable not reset to null in the doAfterBody() function
? (as is done in the doStartTag() in AddReceipientTag )
The problem I had was when I was doing:
mt:addrecipient type=toc:out
value=${param.friendsEmail1}//mt:addrecipient
mt:addrecipient type=toc:out
has anyone tried the nightly 3-18 xml tags in jstl? I'm experiencing a
problem accessing request parameters and http headers. Here is the test
page I used.
%@ taglib prefix=x uri=http://java.sun.com/jstl/ea/xml; %
br$header:host = x:out select=$header:host/br
brS param = x:out
reading over my last paragraph, it's not clear what I meant, so here's a
second attempt. The current 3-19 nightly of XPathUtil.valueOf is below:
public String valueOf(Node n, String xpath) throws SAXPathException
{
staticInit();
XPath xp = new XPath(xpath);
return
Peter,
Thanks for the bug report. There's actually no problem with the plumbing
of the XPathUtil class itself. It's correctly establishing the context
and passes it to our XPath engine. The problem was just that this XPath
engine wasn't resolving namespaces correctly.
I've fixed the problem
?
Thank you very much!
Cindy
-Original Message-
From: Jan Luehe [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 17, 2001 10:28 PM
To: [EMAIL PROTECTED]
Subject: Re: I18N: bundle Bug?
Hi Cindy:
Thanks again for your detailed response.
I'm having trouble grasping the exception tag
91 matches
Mail list logo
