On Tue, 16 Dec 2003, Kris Schneider wrote:
Thanks for looking into it. To be honest, I'm surprised it took this
long to surface ;-). As for whether Result should actually extend
Serializable, I'm usually of the mind that an interface shouldn't extend
Serializable and that it's an
case, you'll need to use a flag.
--
Shawn Bayern
JSTL in Action http://www.jstlbook.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi there (from law school)! :)
As I take a break from reading about civil rights in California, I just
wanted to point out that I just found out JSTL in Action is back in
stock at Amazon.com. (Some people here had pointed out that it was sold
out for a while, but Amazon's stock is now
, and adding other classes, won't help. Just refer to
the property as ${foo.crazy}.
--
Shawn Bayern
JSTL in Action http://www.jstlbook.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
On Thu, 7 Aug 2003, Rick Roberts wrote:
Dude!
Amazon and BarnesAndNobel are out of JSTL in Action.
They must be selling like hot-cakes :)
Ha. I just noticed too, and I've talked with the publisher; I hear
they'll be restocking them soon.
--
Shawn Bayern
JSTL in Action http
greater flexibility to implementations and future
versions of JSTL.)
To retrieve the data, you'll want to use the Config class itself, which
abstracts the variables for programmers. I can't think of any way to
retrieve the information in a standard fashion using just the 'el' tags.
--
Shawn Bayern
On Fri, 25 Jul 2003, Thomas Martin wrote:
Reading tech books is a good way to ruin a good cigar.
Hey! Parts of my book should go quite well with a cigar (though I can't
honestly say that was the design goal). :-)
On Fri, 25 Jul 2003 [EMAIL PROTECTED] wrote:
I much prefer Shawn's new book,
for it to work. Note that
it's mandatory for the container to support it; it's not mandatory for a
taglib author to deploy his or her libraries in this fashion (though it's
probably a good idea in all cases).
--
Shawn Bayern
JSTL in Action http://www.jstlbook.com
On Sun, 29 Jun 2003, Michael Duffy wrote:
Actually, step 3. is unnecessary. When you create the JAR file for
your handler, the TLD file goes inside it. It's already got the URI
string you should use in your JSP. When the JSP compiler goes looking
for your TLD, it'll find it in the JAR
On Mon, 30 Jun 2003, [gb2312] guo yingshou wrote:
Are you sure it works on all j2ee complaint servlet engine?
The behavior is mandated by sections 7.2.1 and 7.3.1 of the JSP 1.2
specification, so all compliant containers support it; if a product
claiming compliance doesn't support it, then it's
Ah - I just realized you were using DBTags, not JSTL. If you're using a
JSP 1.2 container, you'll probably want to switch to JSTL anyway.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
On Mon, 16 Jun 2003, Roland Dong wrote:
I have some programs which uses pre-jstl
or
something similar) with an EL expression. In other words, if you've
called it 'xmldoc_string' in one of the scopes, then
x:parse xml=${xmldoc_string} var=document/
should work.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
don't need to use the
sql:setDataSource tag at all; this tag is useful only in cases where you
haven't established (or want to override) the default.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
it). Instead, the goal is to
simplify things for page authors.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
to a better design anyway, where output stays the
responsibility of JSP pages.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
presence in the page.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
On Fri, 21 Mar 2003, Tim Kettering wrote:
If I understand correctly, a JSP 2.0 container will let you use EL 2.0 expressions
anywhere in the jsp body without having to use the JSTL tags. I also believe
changed. In other words, instead of
%= pageContext.findAttribute(foo) %
you'd simply write
${foo}
in JSP 2.0.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
-
To unsubscribe, e-mail: [EMAIL PROTECTED
} to %= foo % is that it can be used in
the middle of otherwise well-formed XML documents; JSP continues to
provide an XML syntax. In fact, ${foo} is more compatible with XML than
c:out value=${foo} / in cases where you want to use the variable in
another tag.
--
Shawn Bayern
JSTL in Action
; they are only
used to retrieve values from a handful of specific locations, not
to call open-ended Java code.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
-
To unsubscribe, e-mail: [EMAIL PROTECTED
/products/jstl.
That page also has an appendix from my book that lists tags and attributes
in a concise form.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
-
To unsubscribe, e-mail: [EMAIL PROTECTED
On Thu, 20 Mar 2003, Peter Giesin wrote:
c:set var=foo value=/a/b[1]/
x:parse xml=some-xml-source var=xml/
x:out select=$xml/a/b[1]/
I would like to define the x:out statement to use the foo variable
instead of the hard-coded xpath. Something like this: x:out
select=$xml/$foo/
I have
On Mon, 10 Mar 2003, Hanasaki JiJi wrote:
The JSTL taglibs (c:out) re-write html tags into GT so the actual
text prints out. Is there any way to disable this?
Yes, the escapeXml=false attribute of the c:out tag disables this
behavior.
--
Shawn Bayern
JSTL in Action http://www.manning.com
by c:set to do this, as in
c:set var=safeStringWithNoBrackets
c:out value=${mayContainHtmlOrMayNot} /
/c:set
%-- modify string --%
c:out value=${safeStringWithNoBrackets} escapeXml=false /
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
the escapeXml=false attribute to get around your
problem. (The problem would show up more clearly if you looked at the raw
HTML source of the page that's giving you this error message.)
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
and that got the same. Presumably it is
looking for a get method, how do I access an is method?
${result.limitedByMaxRows} is correct; are you sure it produced an error?
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
On Wed, 26 Feb 2003, Hunter Hillegas wrote:
Any place where there is a list of changes?
Sure. It's linked (as Release Notes) off of the Standard Taglib
Documentation on the main page for the Standard Taglib at Jakarta Taglibs.
The direct URL for the revision history is
it's run.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
of information for people in your situation; I had sort
of hoped there would be more people like you. :-)
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e
compiled only when they change.)
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
. They stretch JSTL as far as it
can go in this respect; any larger applications would probably require
Java.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands
by a number of other things
-- I expect to have it posted tonight or tomorrow.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
Just as interesting historical background...
The terms model 1 and model 2 actually come from an old version of the
JSP specification that describes two models of web-application
development: the first model (model 1) sends requests directly to JSP
pages, whereas the second (model 2) sends
of functions that JSTL 1.1 will expose is still being
debated, but it will likely include a limited set of string-manipulation
functions and a handful of targeted solutions (such as a 'size' function).
Future versions of JSTL can expose more functions as necessary.
--
Shawn Bayern
JSTL in Action
to work with java.util.List and
java.util.Map (as well as arrays and strings), not java.util.Collection in
general.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
-
To unsubscribe, e-mail: [EMAIL PROTECTED
other situation.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Tue, 11 Feb 2003, Fredrik Westermarck wrote:
Will there be a 1.0.3 of the Standard Taglib soon, or are there still
issues that needs to be resolved before a release can be made?
Our plan is to release Standard Taglib 1.0.3 within a few days -- most
likely by 2/17.
Shawn
On Wed, 12 Feb 2003, Eddie Barna wrote:
I am working through the JSTL in Action book by Shawn Bayern. Great
book by the way.
Cool! Great to hear.
I have finaly ran into a situation that brought me here. The variable
exposed by the sql:query tag has certain properties
and
then call getTypeB().
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
understanding the request right, the following would work:
${requestScope[requestScope['org.apache.struts.Globals.LOCALE_KEY']]}
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
-
To unsubscribe, e-mail: [EMAIL PROTECTED
No, but that's only because 'org.apache.struts.Globals' isn't a scoped
variable; the expression language can't be used to retrieve static fields
in a class. The expression language is designed to access only certain
kinds of data.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
an identical problem (or at least a very similar
one) and came to the same conclusions.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
several
books on JSTL; more info on mine is available at the URL below.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
like the following:
c:out value=${requestScope['javax.servlet.error.message']} /
The [] syntax works wherever . works, but it lets you avoid problems when
the property name itself contains a period.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
You don't seem to mind using scriptlets, so
c:if test=...
% if (1==1) return; %
/c:if
would work. Your own my:return would indeed probably be cleaner,
though.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
are coerced to Double, but the result of a division with
/ is, by spec.
If you're concerned simply about display, you can use fmt:formatNumber
to process the number according to your needs.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
my question.
Thanks for all the help!
You'll want to build up the string first and then use it as a dynamic
property of 'param':
c:set var=x value=thing_${count} /
c:out value=${param[x]} /
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
- but a collection
of all keys
... is just ${param}, a Map of all request parameters (with single
values).
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
tag.
You might want to read through the JSTL standard or pick up a book on
JSTL; it'll help with basic features like this. Best,
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL
On Mon, 20 Jan 2003, Jerome Jacobsen wrote:
I was looking at the JSTL code and noticed that the Tags attributes
which accept EL are of type String. Then the Tag handler does the EL
evaluation. However with JSP 2.0 wouldn't the attribute be the actual
Object expected (post evaluation)? In
tags disappear in near future ?
That's how it will look, but in terms of the actual implementation, the
EL-based tags (i.e., tags that interpret the EL themselves) will go away,
and the RT-based tags, which will allow either rtexprvalues or JSP 2.0
EL expressions, will be used.
--
Shawn Bayern
time. Just mail [EMAIL PROTECTED], or post to the
regular Bugzilla archive at nagoya.apache.org, if you've got any questions
or bugs to report.
Thanks for all the feedback, reports, and questions. The implementation
benefits immeasurably from your feedback.
Shawn Bayern
JSTL RI lead
situation.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
wrap the XPath expression in
the string() function and continue to use x:set.
Hope that helps,
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
understanding is that
z gets put in page scope, but I don't know how to
access it from there.
JSTL tags don't expose scripting variables. You'd need either to insert a
jsp:useBean tag or to refer to the scoped attribute, as in
% String a = ((MyClass) pageContext.getAttribute(x)).getName(); %
--
Shawn
in setXxx(). That is, in
TYPE getXxx()
and
void setXxx(TYPE x)
'TYPE' must be the same.
- No more than one setXxx() method may exist.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e
with something like
/version/@mimetype
This means the attribute 'mimetype' of the tag 'version.'
Hope that helps,
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
=${myMap} property=boolean${c.count} value=${true} /
/c:if
/c:forEach
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
isn't part of JSTL but
does exactly what you're looking for.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
]}
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
tried but cannot
find how to combine varReader with XML parsing, can somebody give me a
demonstration ?
x:parse accepts a Reader, so you can simply write
c:import url=/xxx.xml var=xml /
x:parse var=doc xml=${xml} /
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
}/
/c:forEach
is this possible? or do i have to do something else first
Yes, it's possible just as you've written it.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
On Sat, 23 Nov 2002, Wendy Smoak wrote:
Can you nest c:forEach tags? I can't find an example of it, and
it's not working for me.
Sure.
c:forEach items=${itemList} var=item
hr
c:out value=${item.id}/. c:out value=${item.text}/br
c:forEach items=${item.options}
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
On Thu, 21 Nov 2002, Henri Yandell wrote:
I wonder if Sun will ever get around to dumping the acronym-rule bit
from their coding standard. Or is it already gone?
[as in, URL is wrong by the Java Coding Standard, but Url is right]
No, it's still there, but it's not universally followed. To
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
, ResultSupport.toResult(rs)); %
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
On Fri, 15 Nov 2002, Zaretzke, Peter wrote:
public void setList( String value ) {
list.add ( value );
}
does not work because it does not meet the parameter expectations (
List vs. String ) for beans. I know that I can write more setZZZ()
methods to add something
needed.
x:xmlns prefix=... uri=... scope=.../
Names that begin with xml are reserved by the XML specification.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
--
To unsubscribe, e-mail: mailto:taglibs-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail
you're using has come from x:parse or from a
servlet. But either way, you must refer to it using XPath variables, not
the JSTL EL inside the 'select' attribute. Thus, you'd write
x:out select=$MyDOM//* /
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
--
To unsubscribe, e-mail
(resultSet);
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
--
To unsubscribe, e-mail: mailto:taglibs-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:taglibs-user-help;jakarta.apache.org
On Thu, 14 Nov 2002 [EMAIL PROTECTED] wrote:
Am I just being stupid or are the WAR files missing from the binary
distribution of JSTL 1.0.2?
Indeed, I think the latest distribution doesn't have the sample and 'doc'
WARs. The problem was on my end; I've been meaning to correct it but
haven't
that creates a scripting
variable, you can use jsp:useBean instead. (Don't be fooled by the name
bean; you can use it to create a scripting variable of any type.)
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
--
To unsubscribe, e-mail: mailto:taglibs-user-unsubscribe
On Mon, 11 Nov 2002, Manfred Riem wrote:
Does anyone have DTD modules for the standard taglibs? I need to have
those to do document validation offline ;)
DTDs won't help you; JSP tags use namespaces, which are beyond the
capabilities of DTDs.
Shawn
--
To unsubscribe, e-mail:
in JSTL 1.0
won't let you access that method unless you provide a wrapper class. In
JSP 2.0, you'll be able to associate that method with a function.
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
--
To unsubscribe, e-mail: mailto:taglibs-user-unsubscribe;jakarta.apache.org
On Fri, 8 Nov 2002, Henri Yandell wrote:
Apologies if this is in one of the books on JSTL, I've only got
Shawn's and it's not in there afaik.
Heh - the snippet is actually almost identical to Listing 9.1 in JSTL in
Action. :-) (It actually uses a slightly different approach, but the
are always appropriate, it's not clear what's supposed to happen when
you introduce a custom one. Any comments?)
--
Shawn Bayern
JSTL in Action http://www.manning.com/bayern
On Wed, 6 Nov 2002, Alberto Tomas wrote:
Hy all,
I posted this question 3 weeks ago and nobody has answered it. I post again
question, you'd write
%= pageContext.findAttribute(elenco) %
This is better than out.print(), and it retrieves the scoped attribute via
the PageContext object, which is necessary, for it's not a scripting
variable (just a scoped attribute).
--
Shawn Bayern
JSTL in Action http://www.jstlbook.com
I hate to pass the blame, but this looks, if anything, like a
JSP-container bug. What JSP container are you using?
--
Shawn Bayern
JSTL in Action http://www.jstlbook.com
On Wed, 30 Oct 2002, Þorgils Völundarson wrote:
hi,
I just noticed that the jstl x tag writes out /x:if tags when
, you wrote:
I hate to pass the blame, but this looks, if anything, like a
JSP-container bug. What JSP container are you using?
--
Shawn Bayern
JSTL in Action http://www.jstlbook.com
On Wed, 30 Oct 2002, Þorgils Völundarson wrote:
hi,
I just noticed that the jstl x tag writes
statement and end up hijacking
it to produce unintended results.
--
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
read-only access to your data.
--
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
, are questions dependent on your application's overall design.
--
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
is
simply template text.
--
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
of ResultSupport.
--
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
the JSTL tags
instead. The issue you noted with line breaks will affect you with
scriptlets as much as it will with JSTL tags.
--
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
is nonstandard; I'm suggesting it's not happening
the way you're describing if you're using our implementation.
--
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
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
in a servlet. If you think it would be particularly
convenient for a future version of JSTL to offer this feature, you could
send a comment to the official JSTL feedback address at
[EMAIL PROTECTED]
--
Shawn Bayern
JSTL in Action http://www.jstlbook.com
--
To unsubscribe, e-mail
be offered in the future if it's not
problematic and if there's a compelling reason to.
--
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
=${item.a_nomefile} /
works, then a c:param tag that uses the same expression ought to work as
well. Your previous message indicated that there was some difference
between the two in the same JSP page, and I wanted to confirm that that
was what you meant.
--
Shawn Bayern
JSTL in Action http
?
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.
--
Shawn Bayern
JSTL in Action http://www.jstlbook.com
='${boundaryStart}'/
[c:out value=${boundaryStart}/ - c:out value=${boundaryStart +
perPage -1}/]/anbsp; /c:forEach
Simply use the c:url and c:param tags.
--
Shawn Bayern
JSTL in Action http://www.jstlbook.com
--
To unsubscribe, e-mail: mailto:taglibs-user-unsubscribe;jakarta.apache.org
:
c:out value=${user.userName} /
and the following yields an error:
c:out value=${user.userName} /
I'm using 1.0.2, but nothing in 1.0.2 should differ from 1.0.1 or 1.0 in
this regard.
Please post more information if you can reproduce the bug. Thanks,
--
Shawn Bayern
JSTL in Action http
, and it will be garbage collected as necessary. The goal was to
prevent the exposure of hard resources (like database connections) to JSP
page authors -- and thus let page authors avoid having to worry about
resource deallocation.
--
Shawn Bayern
JSTL in Action http://www.jstlbook.com
--
To unsubscribe, e
from a form, then you'll want
${param[user.name]}
--
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
way.
--
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
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
backing Java code. :-)
--
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
'. If you want to refer to this node,
you'll probably want to use the name() and namespace-uri() functions in
XPath. See the XPath standard or chapter 8 of JSTL in Action.
--
Shawn Bayern
JSTL in Action http://www.jstlbook.com
--
To unsubscribe, e-mail: mailto:taglibs-user-unsubscribe
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
1 - 100 of 416 matches
Mail list logo
