Hi Jerry, Are you speaking of JDBC mailets (whiteList for instance)
These mailets are currently deprecated (or will be) as they hard code their database, are not standard, not tested and not documented. Note that they are considered as 'experimental' ( cf http://james.apache.org/server/dev-provided-mailets.html ). I would discourage their use (unless you really need these features) and call for contribution: - Write a generic storage API for them - Rewrite these mailets on top of this storage API - Provide JPA storage for these storage APIs - Bind stuff in Guice/Spring A bit of work, but if you really need it, I would be pleased to provide such guidance. On 17/09/2019 09:39, Jerry Malcolm wrote: > A couple of my mailets need to access a different database other than > the base james db. I've got the main db set up in the > james-database.properties file. Currently I'm just hardcoding the > database connection to the other db in the mailet. Just curious if > there's a better architected process where I can define two datasources > in james-database.properties and reference the alternate datasource when > needed. Couldn't see anything as to how to do that. Not a big deal. > Just trying to clean up a few things as I migrate to the new version. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org > For additional commands, e-mail: server-user-h...@james.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
