>> Hi again, >> >> The next thing I'm stuck on is database connections. >> Now currently there are a squad of mailets using avalon to get database >> connections, however we want to remove avalon dependancies from mailets, >> so... >> >> do we either make db connections available through the MailetAPI >> or do we force mailets to make other arrangements. > > My vote is to expose db connections via javax.sql.DataSource, and lookup > this object via JNDI.
I agree with Serge on this as it is a defacto standard pattern nowadays for finding and utilizing databases. I don't know if James has a mini-JNDI service provider or not, but there must be a few floating around, I know tomcat has a small one that could probably be used. I know I don't like the DataMailet approach; doesn't really help anyone as the user is going to set up their database anyways, they might as well do what they normally do in app deployment, which is declare their JNDI data sources. Mailets probably aren't going to be agents that float around to other servers, they will be explicitly deployed, just like a webapp. Matt Bishop The conventional view serves to protect us from the painful job of thinking. --John Kenneth Galbraith -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
