Morgan Delagrange wrote:
> Here's a specific example of the dilemna caused by
> wrapping all our functionality in big projects.  I
> have a little JDBC tag library that we're about to
> release in Taglibs.  However, it's ridiculous for me
> to implement my own database pooling for the tag,
> because that's way out of scope for the project.
> Therefore, I'd like to point to somebody else's
> database pool.  The question is, whose?

Incidentally, I plugged Morgan's JDBC tags into my current Struts
project last night. His tag supports a connection through a standard
Javax datasource, and the Struts pool exposes itself that way via the
application context. They hooked up smooth as silk, and I'm a very happy
camper right now! 

-Ted.

Reply via email to