JSTL database access

[Raj Puri]

I am reading on JSTL datbase access. Seems to use example one needs to type on top everytime:
uri="http://java.sun.com/jstl/ea/core"
uri="http://java.sun.com/jstl/ea/sql " etc.

I was windering why it should be like this? I should be able to install
jar files and work with JSTL tags. What is better? I guess if tomorrow sun moves above links then applications will crash.

How to get rid of these external dependents/

[Mcgill Smith]

Indirect access.Decalare it in the web.xml in the <taglib> tag
<taglib-uri>/-----------</taglib-uri>use this in the jsp
<taglib-location>/WEB-INF/--------------</taglib-location>physical location
[ June 02, 2005: Message edited by: Mcgill Smith ]

[Bear Bibeault]

I would not define these in web.xml.

Those are URI's not actual URL's. They don't actually point to anything, so there's nothing that can be moved to "break" the pages.

The JSTL URI's are just strings, that happen to have been defined to look like URL's, that uniquely identify the tag libraries.

Btw, those are not the standard JSTL URI's. I'd be sure to use those defined by the standard.

[Raj Puri]

Thanks. I was looking at down loading jar files from sun that has code covered by these URI's and including them in our web server lib.What is more standard way for production applications to use URI point to http:// given in books or installing them on webserver??? In my past I have not used them but read about them and am not sure which way to use them.To me
include them as URI is still a round trip outside our intranet so definetly not so good.

[Bear Bibeault]

To me include them as URI is still a round trip outside our intranet so definetly not so good.

No no no. There is no round trip. The URI is not a URL that accesses anything. It's just a string that is used to match up the prefix you specify in the taglib directive with a tld file (probably in a jar file) on your server.