Chapter 20 of the Developing Applications guide (specifically, printed pp.
207-ff) shows how to connect to a data source in a servlet. JRun's custom JSP
tags also allow you to access and query data sources extremely easily.
I agree, especially on the connection pooling, that more details should be added
to the docs.
Scott
-----Original Message-----
From: Lynn Walton [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 17, 2000 9:51 PM
To: [EMAIL PROTECTED]
Subject: Re: jrun3 connection pooling ..
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Scott,
<br>In the servlet's examples of the Developer's App's it doesn't mention
the connection pooling and just shows the normal JDBC way to instantiate
your Driver's class, then use DriverManager.getConnection( ).
That makes it look to me like that would not take advantage of the pooling
in that sample? Unless jrun does some magic to intercept and use their
own DriverManager class (using the same name as the built in jdbc seems
a little strange). That's what I'd like to see more documentation
on?
That example also show's passing url's, usernames, passwords etc in the
standard JDBC way ... but jrun's feature of setting up JDBC
DataStore's
so that those items don't have to be placed in the code, is not shown in
any example I have found so far. The closest I've found seems to be in
the EJB sections which wouldn't apply to those of us not using that yet..
So how is one supposed to make use of a JDBC DataStore object once it is
set up?
<p>Thanks for the info about mirroring the active threads pool. That's
a start. But I definitely think some of these things need to be added to
the docs.
<p>Thanks,
<br>Lynn
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.
