On Tue, 24 Jul 2001, Casazza, Robert wrote:
Maybe this is more related to Struts but I'm curious as to whether
Jakarta Tags allow:
[1] looping, in particular to be able to dynamically
populate a table based on a collection of
objects with attributes
The JSPTL will supports
On Mon, 30 Jul 2001, Florian Brunner wrote:
I'm currently using the jakarta taglib input in my JSP. With
input:select you have to specify the options as a Map. But I want the
list to display the values in the same order I added them to the Map!
How can I do that? Can I use TreeMap? But then
On Tue, 31 Jul 2001, Kevin Duffey wrote:
Is there any provision in the JSPTL to provide this ability to add
javascript handlers (and not just a single one) to each tag?
JSPTL isn't currently focusing on graphical elements (such as JSP tags
that produce HTML tags); that has become more the
Hi Robin. I'm away on vacation for the rest of the week, but if nobody
gets a chance to look at this issue before then, I'd be happy to take a
look at it early next week.
Thanks for the message,
Shawn
On Thu, 9 Aug 2001, Robin Mannering wrote:
I've been using the input library for some time
since
I can't replicate the problem.)
Shawn Bayern
JSPTL Reference-implementation Lead
is that the
jx:expressionLanguage tag and the whole idea of switching between
expression languages is most likely going to be a temporary one.
Of course, that's just an excuse. But my point is that the ugliness will
probably go away soon anyway.
Shawn Bayern
JSPTL Reference-implementation Lead
closely in line
with what's seen as a more typical JSP pattern: JSP, being used mostly
for presentation, needs less intricate control flow than the Java language
itself provides.
Shawn Bayern
JSPTL reference-implementation lead
There's a standard, easier way to handle it: you can use a
TagLibraryValidator to ensure that the page contains no scriptlets.
JSTL's (early-access) reference implementation comes with a
'scriptfree.tld' library that you can import using the %@ taglib %
directive. This library ensures that
the JSP pages a compilation time. So all
pages will be scriptlet-free ?
--- Shawn Bayern [EMAIL PROTECTED] wrote:
There's a standard, easier way to handle it: you
can use a
TagLibraryValidator to ensure that the page contains
no scriptlets.
JSTL's (early-access) reference
On Fri, 23 Nov 2001, James Strachan wrote:
Shawn, do you want to apply a similar patch to the XML tags in JSTL,
to allow a parameter value to be an Object? I'll do it if you like?
Basically Transformer.setParameter(String name, Object value) can take
a value of Object rather than just a
On Wed, 5 Dec 2001, bo wrote:
I wonder if I can determine the relationship among tags, such as tag A
should be within tag B etc. Is that possible? Thanks!
You can use a TagLibraryValidator class to enforce arbitrary
characteristics of the XML view of a JSP page, including specific
Hi there.
Looks to me, offhand, just like a problem with your container's XML
parser. (Perhaps you have conflicting versions of JAXP in your
environment.) As far as I can tell, it doesn't look like the problem's
related to any specific code in the Standard Taglib (JSTL RI).
Shawn
On Sat, 8
On Thu, 13 Dec 2001, Lavandowska wrote:
What do you expect to happen to the current taglibs that handle these
functions in the Jakarta-Taglibs project? Are these new JSTL tags
related in any way to the existing taglibs?
In general, JSTL's tags have been informed by best-of-breed products,
On Thu, 13 Dec 2001, Paul DuBois wrote:
I haven't seen this in the docs that I've read so far. Is this:
- something I should just know
- an oversight in the docs or the distribution
- complete coincidence that installing js.jar fixed my pages :-)
It's definitely not the latter. :-) I've
On Tue, 25 Dec 2001, Alice K wrote:
The newly built seems fixed the Null problems in Resin. However, the
iterator (forEach) examples do NOT work correctly in Resin. It only
shows on record only.
Interesting. This is the second such report of this behavior in Resin.
I'll take a look as
Achim,
It looks like the problem may just be caused by two conflicting versions
of JAXP:
java.lang.ClassCastException:
org.apache.crimson.jaxp.DocumentBuilderFactoryImpl
Since your stack trace doesn't run through any code in the JSTL RI, my
guess is that this is just a minor configuration
On Wed, 2 Jan 2002, Paul DuBois wrote:
What are the constraints on the type of expressions that may be used
with c:if?
The short answer is 'boolean' or 'Boolean.'
The somewhat longer answer is that for the rtexprvalue library, the only
permissible type is 'boolean'. For the EL library, the
Thanks for the problem report, Paul. This was an error in the TLDs; the
relevant tag handlers look okay. I've fixed the problem, and the change
should show up in tonight's nightly build.
Shawn
On Wed, 2 Jan 2002, Paul DuBois wrote:
The documentation for sql:param states that it can be used
On Thu, 3 Jan 2002, Maciej Ko³odziej wrote:
Where can I get sources of standard jsp tags, like jsp:forward?
Standard JSP actions are implemented by code owned by the container;
they are not imported from external code (at least not using a public
standard mechanism), as custom actions can be.
As other users have pointed out, Resin seems to fail on the JSTL RI's
iteration tag; I haven't yet had a chance to look into whether this is a
Resin bug or not.
If anyone who already has Resin set up would be interested in testing
whether this bug occurs with any IterationTag or just with the
On Thu, 3 Jan 2002, Paul DuBois wrote:
The documentation for sql:update indicates that the var attribute is
optional, but I find that without it I get an error message that the
TLD requires it. Adding var=dummy cures the problem, but should
that be necessary?
Hmm. The TLD doesn't show it
}
// here, 'foo' is declared from before, but has value from
// inner block
Hope that helps!
--
Shawn Bayern
Author, The JSP Standard Tag Library: http://www.jstlbook.com (upcoming)
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto
On Wed, 9 Jan 2002 [EMAIL PROTECTED] wrote:
- it fails to deploy on WLS 6.1 SP1 (obscure Error deploying application .
\config\mydomain\applications\standard-examples.war:
java.lang.reflect.UndeclaredThrowableException)
- it seems to work on WLS 6.1 SP2 (not tried every example, but the ones
On Sun, 13 Jan 2002, Alice K wrote:
The EA3 does not work on Resin 2.0 and over. The EA1 is working
correctly.
Okay -
I finally got a chance to look at this problem closely. The issue is, as
I suspected all along, a bug in Resin. However, I didn't, in my wildest
dreams, guess what the
On Tue, 15 Jan 2002, Vianen, Jeroen van wrote:
I downloaded the 14 January snapshot and saw that this problem has
been fixed in current sources after Shawn Bayern's bug report.
Thanks for pointing this out. According to Resin's bug tracker, Scott
Ferguson responded almost immediately with
Are you sure that html:html is producing a well-formed XML document
(i.e., with a single root element)?
Shawn
On Mon, 14 Jan 2002, Matt Raible wrote:
I am trying to use the x:transform tag to render the following page (code
pasted below). The transformation works (displayed in browser
What JSP container are you using? From what you say, it sounds as if the
container is mis-diagnosing the problem and returning a simple 404 instead
of any useful information.
I believe that a JSP container can, when no errorPage is defined, handle
errors and exceptions in an
On Sun, 27 Jan 2002 [EMAIL PROTECTED] wrote:
How do I put the result of the tag into the method? Without having to
create a tag for Language. My suggested solution would be a tag which
places its body into a named variable. So:
standard:eval var=namestore:get jdo=person.name//standard:eval
standard. Don't get too used
to clever tricks and workarounds that are EA3-specific!)
--
Shawn Bayern
JSTL reference-implementation lead
Author, JSP Standard Tag Library (Manning,upcoming) http://jstlbook.com
On Mon, 28 Jan 2002, Pedro Diaz wrote:
Hi all.
After executing the next two lines
are accessed using the
same syntax: $name.
EA3 also comes with a language called SPEL that lets you access scopes
specifically:
$session:foo
$request:foo
and so on.
--
Shawn Bayern
JSTL reference-implementation lead
Author, JSP Standard Tag Library (Manning,upcoming) http://jstlbook.com
with
x:transform? And if you're going to transform it with x:transform,
what mechanism is in place for the server to learn of the browser's
stylesheet?
--
Shawn Bayern
JSTL reference-implementation lead
Author, JSP Standard Tag Library (Manning, upcoming) http://jstlbook.com
indeed equal 1, interestingly enough
/crt:if
If you're still having trouble with it, let us know; please show the
entire JSP page and include info about what container you're using.
Best,
--
Shawn Bayern
Author, JSP Standard Tag Library (Manning, upcoming) http://jstlbook.com
--
To unsubscribe, e
implementation is distributed through the Jakarta
Taglibs project.
For more information on JSTL, I've posted an article at Manning's web site
describing its role and future:
http://www.manning.com
Best,
--
Shawn Bayern
Author, JSP Standard Tag Library (Manning, upcoming) http://jstlbook.com
.
(I note that the final line you added, while sufficient to expose a scoped
attribute to your JSP page and thus to JSP, doesn't end with a ;, which
might indicate you didn't recompile the class.)
Hope that helps,
--
Shawn Bayern
Author of JSP Standard Tag Libary (Manning, upcoming) http
at
http://www.manning.com
Hope that helps explain things,
--
Shawn Bayern
Author, JSP Standard Tag Library (upcoming, Manning) http://jstlbook.com
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
is described in chapter 13 (Deployment Descriptor) of
the Servlet 2.3 specification, available from java.sun.com. The
listener tag represents a concept introduced with version 2.3 of the
Servlet specification.
Hope that helps,
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this spring from Manning Publications)
On Thu, 14 Feb 2002, August Gresens wrote:
The solution from the spec worked for the use with the input taglib.
I'm now having a problem with standard HTML tags, when I want
--
that is, receive it via a BodyContent object and interpret it (e.g., check
it against some value, trim it, make it uppercase, or whatever else it
wants to to) or it can simply pass it through.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this spring
container's
job is (currently) to interpret the text that occurs in a JSP page, not to
interpret JSP-like fragments that occur as data.
(JSP 1.3 may have provisions to make something like this easier, but
that's just a possibility.)
--
Shawn Bayern
Author, JSP Standard Tag Library http
The final version of JSTL will most likely be substantially more lenient
with respect to values that don't exist. Unfortunately, there's not much
I can advise other than, Wait for the upcoming version! :-) (Such is
the nature of early-access releases.)
--
Shawn Bayern
Author, JSP Standard Tag
() 0.5 %foo/c_rt:if
% } %
/benchmark:duration
Even the optimizations that some containers make, pooling tag handlers,
probably won't be particularly noticeable except in extremely tight loops
(like do this 1 times) when tag handlers are written properly.
--
Shawn Bayern
Author, JSP
of unnecessary whitespace.
To help you further, I think we'd need more information about exactly what
problem you're experiencing.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this spring from Manning Publications)
On Wed, 27 Feb 2002, Lomvardias, Christopher wrote
attributes than their predecessors.
The practical answer is, thus, You don't need to worry about it.
Initializing the instance variable as
boolean attr1 = false;
is fine.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this spring from Manning Publications
exposes
contains a getSize() method, which translates to a 'size' property.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this spring from Manning Publications)
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL
approach, and
also unnecessary. You can use jsp:useBean to declare a scripting
variable, so we didn't need to provide support in JSTL -- especially given
that JSTL is de-emphasizing them.
Best,
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this spring from Manning
that refer to
such interchangeability. 8(
JSTL doesn't particularly encourage this usage, but it's perfectly
possible using older, scriptlet-oriented mechanisms like jsp:useBean.
Just use a jsp:useBean tag after c:set to declare your scripting
variable.
--
Shawn Bayern
Author, JSP Standard Tag
think 5
because you replaced the scripting variable 'four' with an Integer object
for the number 5. But the tag actually prints out 4, because changing a
scripting variable doesn't change the scoped variable that it was
originally tied to.
--
Shawn Bayern
Author, JSP Standard Tag Library http
if that counts as a pun or not...)
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this spring from Manning Publications)
On Mon, 11 Mar 2002, Steve Bang wrote:
Can anyone help me on this?
Thanks,
Steve
-Original Message-
From: Steve Bang
at one point was that J2EE technologies would be
covered more thoroughly in JSTL 1.1, the (presumably) next version of
JSTL. But again, that's just speculation.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this spring from Manning Publications)
--
To unsubscribe
stuff like
this in some detail.)
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this spring from Manning Publications)
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
On Tue, 12 Mar 2002, Agrawal, Anuj (Anuj)** CTR ** wrote:
Is there a way to display the source code for a particular JSP page?
I'd like to have a link at the bottom of the page which will display
the source (for the curious) when clicked on - very much like the way
the SourceForge site has
release.
Enjoy!
--
Shawn Bayern
JSTL reference-implementation lead
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this spring from Manning Publications)
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
On Wed, 13 Mar 2002, John Baker wrote:
Can you be more specific to what I should be looking for? The file I'm
including has a load of other jsp imports, etc that do not cause it to
screw up. I'm quite happy to look for the problem, if I know what I'm
looking for ;-)
Thanks for that quick
should now write
${param.action == 'Edit'}
Actually, 'request:action' would have never indicated a request
parameter; it would have indicated a request-scoped variable
(attribute). Now, you'd use ${request.action} to indicate the 'action'
variable in 'request' scope.
--
Shawn Bayern
Author, JSP
, you
can declare the scripting variables with a jsp:useBean tag:
c:forEach var=serial ...
jsp:useBean id=serial type=... /
option%= serial %/option
/c:forEach
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications
with the HttpServletResponse.encodeURL() method, which would also cause
problems for c:url. But I don't know offhand the version where it's
problematic.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
--
To unsubscribe, e-mail: mailto
just not sure
what to do about it.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
On Thu, 14 Mar 2002, Matt Raible wrote:
The following code was working before I updated to last night's build:
c:import url=/styles
of facilitating
integration of JSTL into older applications and methodologies. The 'rt'
versions won't be necessary once JSP itself supports the expression
language.
Section 1.3 of the JSTL Public Draft describes the situation more
completely.
--
Shawn Bayern
Author, JSP Standard Tag Library http
be subordinate to
rtexprvalue execution.
So, are you sorry you asked yet? :-)
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto
?
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
to be both the safest and the most general.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
this kind of indirection is
absolutely necessary?
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Interesting. The AbstractMethodError is apparently coming from a call to
the ResultSetMetaData object associated with your JDBC driver. The
underlying issue may result from either a bug or a version incompatibility
in the driver. But this issue raises a question of how JSTL should handle
whether or not JSTL has a tag that aborts the current
page, the answer is currently no.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto
= new Blob[100];
// fill blobs
request.setAttribute(blobs, blobs);
now can I do:
c:if test=${request.blobs[2].whatever ?
Cheers!
Yes, this should work.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications
is that Struts will eventually accommodate the standard
taglib (JSTL) and integrate well with it. The other taglibs in Jakarta
Taglibs are essentially just separate offerings from Struts, attempting to
address different needs (or similar needs from a different perspective).
--
Shawn Bayern
Author, JSP
recommended over the latter) if you want to
access arbitrary methods and pass arguments to them.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e
; it encourages good design when
unambiguous, but otherwise tries to avoid preaching about how you must
design your applications.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED
On Mon, 18 Mar 2002, John Baker wrote:
That's a real minus point for JSTL.
In defense of the way JSTL currently works, this isn't really its job.
The design standard for components is JavaBeans, which outlines what's a
property and what's not.
--
Shawn Bayern
Author, JSP Standard Tag
()
method for the class Integer, if that's what you're asking.
If you had an individual Integer I, then ${I.class} would correspond to
the Class object for Integer.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications
intended to work the same. If they were, we wouldn't have
needed an expression language! :-)
--
Shawn Bayern
Author, JSP Standard Tag Library
http://www.jstlbook.com (coming this summer from Manning Publications)
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e
the request-scoped variable named
'parameter'. To retrieve a parameter, use 'param.moo'.
Again, there isn't a one-to-one isomorphism between JSTL expressions and
rtexprvalues.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications
said, you can use an expression starting with 'param':
${param.moo == 'cows'}
I don't mind answering all your questions, but you might want to take an
hour and read through the entire JSTL draft spec! I think it'll answer a
lot of your questions. :-)
--
Shawn Bayern
Author, JSP Standard Tag
by adjusting the matching logic to work against
prefixes, not namespaces. I've also made error checking more aggressive;
a variable that doesn't match with a value now fails immediately during
resolution.
I've checked in changes to the CVS archive that should fix your problem.
Best,
--
Shawn
it works.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
/core; %
We'll need more information to help. It depends on the container you're
using and how it's configured. Are you using standard-examples.war, a
complete web-application archive for the JSTL examples?
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming
as JavaBean-like properties of the PageContext. But headers
aren't available this way, so they're going to be added as new top-level
implicit objects.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
--
To unsubscribe, e-mail
This actually doesn't look like a TransformerConfigurationException, but
(because of the slashes) a ClassNotFoundError pointing to
TransformerConfigurationException. You may need to update your
container's XML-support libraries.
--
Shawn Bayern
Author, JSP Standard Tag Library http
is in flux. But it'll settle down before JSTL 1.0 is released.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
On Wed, 20 Mar 2002, John Baker wrote:
Argh, this is driving me nuts.
Consider this:
c:forEach var
your tags.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
information on the way JSTL is supposed to work. There's
also a tutorial at Sun's site:
http://java.sun.com/webservices/docs/ea1/tutorial/doc/JSTL.html
I'm also writing a book on JSTL. It should hit stores this summer.
--
Shawn Bayern
JSTL reference-implementation lead
Author, JSP Standard Tag Library
to
resist database logic too and attempted to do everything in my own
programs, but it's often easier to get the database to manage your data
for you.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
--
To unsubscribe, e
abbreviation.
Whatever we choose would be somewhat arbitrary, so we ultimately opted to
ease the page author's burden of typing!
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED
as MORE cryptic than the current system.
Ultimately, I think that users will know they're looking at JSTL tags by
virtue of general familiarity. But I agree -- any solution is somewhat
arbitrary and imperfect.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming
=${cookie.value} /
/c:if
/c:forEach
I explain this in more detail in my book; interestingly enough, I just
wrote the section describing techniques like this.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
--
To unsubscribe, e
very much for the suggestion, though; I'd be curious if you have
any data that does implicate one part of the JSTL RI over another.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
--
To unsubscribe, e-mail: mailto:[EMAIL
On Fri, 22 Mar 2002, Shawn Bayern wrote:
The evaluator keeps a static cache of values, so literally the only
benefit of pooling our interpreter instances would be to save the
instantiation itself, which should take about ten low-level instructions
on a modern JIT. (That is, the evaluator
Bay's string taglib); hopefully, that'll come up in JSTL 1.1.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
On Mon, 25 Mar 2002, RAYMOND Romain wrote:
Specs indicate c:out value=${request:myparameter}/ to do an
equivalent to request.getParameter(myparameter) but it is not good
...
Have you the right syntax ?
The current specs don't say that. Are you reading documentation that's
out of date?
is critical.
Todd -- great question. This is currently in flux; we're discussing how
best to handle error conditions in c:import. It'll most likely be
decided before JSTL's public final draft (PFD).
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer
, set the
'escapeXml' attribute to 'false'.
Hope that helps,
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
not particularly
interesting). :-)
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
, currently writing
from a JavaOne kiosk). :-)
Thanks again,
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
On Thu, 28 Mar 2002, Andrea Grittini wrote:
I have the same problem using the sql jstl.
When I connect to a DB I got
debated.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
reasonably implementability. These issues will
probably be addressed before our Public Final Draft (and next RI beta).
Thanks again for raising the issue.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
--
To unsubscribe
.)
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
of the problem could show
that it's really our bug.)
Thanks for the report,
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
On Mon, 1 Apr 2002, Zvolensky, Thomas J {PDBI~Nutley} wrote:
I have a query that selects records from
: for instance, the JSTL EL
could print out a byte[] by converting it to a String using the default
character encoding. This is somewhat ugly, but it might fit nicely with
our other type conversions. I'll raise it to the expert group.
Thanks again for the report,
--
Shawn Bayern
Author, JSP Standard Tag
than printing
[B@x.
MySQL, alas, is common enough that we probably want to at least consider
this; in fairness, it's not really a case specific to MySQL, but a more
general question of how our EL deals with byte[].
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
On Mon, 1 Apr 2002, peter lin wrote:
Does anyone know if there are plans to improve jsp:include or create a
new include in jstl?
Yes, JSTL introduces c:import, which (as I think I say in my book) you
can think of as jsp:include: the next generation. :-)
--
Shawn Bayern
Author, JSP
1 - 100 of 416 matches
Mail list logo