You are viewing a plain text version of this content. The canonical link for it is here.
Posted to taglibs-user@tomcat.apache.org by Shawn Bayern <ba...@essentially.net> on 2001/12/13 18:17:56 UTC
JSTL (standard taglib) Early Access 3
Once again, I'm happy to announce a new Early Access release of the JSP
Standard Tag Library (JSTL).
Early Access Release 3 introduces tags for database access and
incorporates some changes to the internationalization and XML-manipulation
libraries.
The reference implementation is available from Jakarta Taglibs as the
'standard' taglib.
Intro page:
http://jakarta.apache.org/taglibs/doc/standard-doc/intro.html
Documentation:
http://jakarta.apache.org/taglibs/doc/standard-doc/index.html
Binary dist:
http://jakarta.apache.org/builds/jakarta-taglibs/releases/standard/
As before, an EA3 milestone "snapshot" as well as the usual nightly builds
will be available.
Community support has been great so far; we're eager to get more feedback
as we come closer to a feature-complete release. Please send all comments
to jsr052-comments@sun.com. Many thanks!
Happy holidays!
Shawn Bayern
JSTL reference-implementation lead
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: JSTL doc inconsistency, and a question
Posted by horwat <Ju...@Sun.com>.
Good catch! The documentation has changed recently and the context init
parameters should be:
* javax.servlet.jsp.jstl.sql.driver
* javax.servlet.jsp.jstl.sql.url
* javax.servlet.jsp.jstl.sql.user
* javax.servlet.jsp.jstl.sql.password
I've updated the implementation and the documentation to reflect the latest
context init params. Here's an example of how you can set the params:
<context-param>
<param-name>javax.servlet.jsp.jstl.sql.user</param-name>
<param-value>someusername</param-value>
</context-param>
<context-param>
<param-name>javax.servlet.jsp.jstl.sql.password</param-name>
<param-value>someuserpassword</param-value>
</context-param>
Justy
----- Original Message -----
From: "Paul DuBois" <pa...@snake.net>
To: "Tag Libraries Users List" <ta...@jakarta.apache.org>
Sent: Sunday, December 16, 2001 5:51 PM
Subject: JSTL doc inconsistency, and a question
> The inconsistency:
>
> The JSTL docs for the sql tags seem to be inconsistent about the
> specification of attributes for the <sql:driver> tag. In some cases
> the URL attribute is called "url", in other places it's call "jdbcURL".
> (The latter appears to be correct.)
>
> Also, a question. The SQL tag documentation says:
>
> >All parameters, except for "password", can be specified via an action
> >attribute or a context init parameter (see below). Action attributes
> >take precedence over context init parameters. The password configuration
> >parameter can only be specified via a context init parameter to prevent
> >situations where sensitive information would be hard coded in a JSP
> >page.
> >
> >The context init parameters are:
> >
> >* javax.servlet.jsp.jstl.sql.driver.driver
> >* javax.servlet.jsp.jstl.sql.driver.url
> >* javax.servlet.jsp.jstl.sql.driver.user
> >* javax.servlet.jsp.jstl.sql.driver.password
>
> I wouldn't mind seeing an example of how you set up and reference these
> context init params from within a JSP page/JSTL tags. I'm assuming
> you set them up as <context-param> entries in WEB-INF/web.xml
> but after grepping through the standard-examples application it's
> not clear to me from the docs whether that's really so or the intended
> syntax for accessing them.
> Thanks.
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
JSTL doc inconsistency, and a question
Posted by Paul DuBois <pa...@snake.net>.
The inconsistency:
The JSTL docs for the sql tags seem to be inconsistent about the
specification of attributes for the <sql:driver> tag. In some cases
the URL attribute is called "url", in other places it's call "jdbcURL".
(The latter appears to be correct.)
Also, a question. The SQL tag documentation says:
>All parameters, except for "password", can be specified via an action
>attribute or a context init parameter (see below). Action attributes
>take precedence over context init parameters. The password configuration
>parameter can only be specified via a context init parameter to prevent
>situations where sensitive information would be hard coded in a JSP
>page.
>
>The context init parameters are:
>
>* javax.servlet.jsp.jstl.sql.driver.driver
>* javax.servlet.jsp.jstl.sql.driver.url
>* javax.servlet.jsp.jstl.sql.driver.user
>* javax.servlet.jsp.jstl.sql.driver.password
I wouldn't mind seeing an example of how you set up and reference these
context init params from within a JSP page/JSTL tags. I'm assuming
you set them up as <context-param> entries in WEB-INF/web.xml
but after grepping through the standard-examples application it's
not clear to me from the docs whether that's really so or the intended
syntax for accessing them.
Thanks.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: JSTL (standard taglib) Early Access 3
Posted by Shawn Bayern <ba...@essentially.net>.
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 clarified the docs (which will
be included in the next nighly distribution) and, as a convenience,
included 'js.jar' in the binary 'milestone' EA3 distribution (just
updated).
'js.jar' is necessary for any uses of the ECMAScript expression language.
Sorry for the lack of information,
Shawn
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: JSTL (standard taglib) Early Access 3
Posted by Shawn Bayern <ba...@essentially.net>.
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 clarified the docs (which will
be included in the next nighly distribution) and, as a convenience,
included 'js.jar' in the binary 'milestone' EA3 distribution (just
updated).
'js.jar' is necessary for any uses of the ECMAScript expression language.
Sorry for the lack of information,
Shawn
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: JSTL (standard taglib) Early Access 3
Posted by Paul DuBois <pa...@snake.net>.
>Once again, I'm happy to announce a new Early Access release of the JSP
>Standard Tag Library (JSTL).
I downloaded this release and installed it. Tried out some of the
examples. They worked.
Tried to write some of my own pages with this tag library. Failed
every time. Finally after a lot of comparison between my own setup
and that used in the standard-examples webapp, I discovered that the
JSTL distribution appears to be incomplete. Specifically, the
standard-examples/WEB-INF/lib directory includes a js.jar file, which,
when I copied into my own WEB-INF/lib directory and restarted Tomcat,
caused my pages to start working.
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 :-)
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: JSTL (standard taglib) Early Access 3
Posted by Vic Cekvenich <vi...@basebeans.com>.
We should not do DB access in JSP (or anything much in JSP). Clear MVC
is more productive.
Vic
Shawn Bayern wrote:
> Once again, I'm happy to announce a new Early Access release of the JSP
> Standard Tag Library (JSTL).
>
> Early Access Release 3 introduces tags for database access and
> incorporates some changes to the internationalization and XML-manipulation
> libraries.
>
> The reference implementation is available from Jakarta Taglibs as the
> 'standard' taglib.
>
> Intro page:
> http://jakarta.apache.org/taglibs/doc/standard-doc/intro.html
>
> Documentation:
> http://jakarta.apache.org/taglibs/doc/standard-doc/index.html
>
> Binary dist:
> http://jakarta.apache.org/builds/jakarta-taglibs/releases/standard/
>
> As before, an EA3 milestone "snapshot" as well as the usual nightly builds
> will be available.
>
> Community support has been great so far; we're eager to get more feedback
> as we come closer to a feature-complete release. Please send all comments
> to jsr052-comments@sun.com. Many thanks!
>
> Happy holidays!
>
> Shawn Bayern
> JSTL reference-implementation lead
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: JSTL (standard taglib) Early Access 3
Posted by Shawn Bayern <ba...@essentially.net>.
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,
both from Jakarta Taglibs and from specific vendors. In the case of the
SQL tags, I think it's accurate to say that JSTL's database tags were
influenced more by Jakarta Taglibs than any commercial source. Still, as
a standard, JSTL doesn't have as much flexibility to experiment as does
Jakarta Taglibs: in some cases, this can lead to better defined, but
perhaps fewer, "features."
To answer your question about what'll happen, that's mostly up to Jakarta
Taglibs committers, who will likely decide how to proceed based on what's
best for the Taglibs user community. (Input from taglibs-user would be
very valuable, in this respect!) This decision can certainly be made on a
case-by-case basis. Ideally (from my personal viewpoint), all Jakarta
Taglibs packages would take JSTL into account in some respect... either by
integrating explicitly; offering "add-ons" for specific, nonstandard
cases; offering an alternative interface -- e.g., higher- or lower-level
abstractions -- for the subset of users that prefer it; etc.
Shawn
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: JSTL (standard taglib) Early Access 3
Posted by Lavandowska <fl...@yahoo.com>.
--- Shawn Bayern <ba...@essentially.net> wrote:
> Once again, I'm happy to announce a new Early Access release of the
> JSP
> Standard Tag Library (JSTL).
>
> Early Access Release 3 introduces tags for database access and
> incorporates some changes to the internationalization and
> XML-manipulation
> libraries.
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?
Lance
__________________________________________________
Do You Yahoo!?
Check out Yahoo! Shopping and Yahoo! Auctions for all of
your unique holiday gifts! Buy at http://shopping.yahoo.com
or bid at http://auctions.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>