|
Following examples posted here, I got a pooled
connection to Oracle working. Having done that, it seems odd to me that I
have to reconfigure JBoss to do so. It seems like JBoss should be able to
keep running regardless of what I need to drop on it, and any configuration
required by a particular bean should be completely described by that
bean. Is there any way to use DB connection pools using only
entries supplied with the bean deployment descriptor? I'm willing to live
with the fact that only that one bean will be able to use that particular
pool. Of course, accomplishing that, I'd want to be able to control it
using other JBoss settings, so that people can't drop in random EJBs that access
corporate databases I don't want them looking at.
|
