----- Original Message ----- From: "Danny Angus" <[EMAIL PROTECTED]>
> there could be two kinds of mailet, Mailet's and DataMailet's the latter, by > implementing DataMailet, declare their requirement for database connections. > > Then the container implementors can choose and declare in their > specifications whether the container is a DataMailet container > > DataMailet would extend Mailet but DataMailetContext > (getDataMailetContext()) would have to provide > getConnection(datasourceName). > > Or.. using IOC the container could supply a mailetDatasource on > initialisation which would have a single method.. getConnection(). > > The last would make it harder for a single mailet to access more than one > datasource, so I prefer the MailetContext().getConnection(datasourceName) > route. I should have responded to this email with my last comment, but again I don't think we should tie db connections to the mailet API. While database connections are significantly less contentious than logging, I feel the same argument applies that the mailet API doesn't need to create dependencies with these related libraries to address these issues. Serge Knystautas Loki Technologies http://www.lokitech.com/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
