Stefano B. wrote in JIRA "Please comment on this bug if you agree on this change now that we have derby configured by default or if you would like to still distribute org.gjt.mm.mysql driver (I tested it doesn't work with Mysql 4.1+ and the "upgrade to connector/j" has already been a solution for at least 2 users having problems with mysql on the mailing list)."
I do not know enough about JAVA to know whether your suggested change will impact my operation. I have no experience with Derby. I am using James 2.2.1-RC1 on an XP box using MySQL 4.1.11 for all stores. I am using the 'org.apache.james.util.dbcp.JdbcDataSource' and downloaded the MySQL connector 'mysql-connector-java-3.1.8-bin.jar' from http://dev.mysql.com/downloads/connector/j/3.1.html. I have been using the db stores since starting with James four plus years ago and I am now supporting 5 domains. I could not be more pleased and would hope that future releases remain compatible with MySQL with little additional effort. I understand the licensing issues as far as packaging the MySQL supplied connector goes but again, would hope that James plans does not prevent me from doing what I did on future releases. I wish I knew more about "building" mailets and matchers from a Win32 platform. I expect to have a need to deploy some custom, but universally appreciable, mailets in the near future as I am using James with db stores as the communication backbone of a comprehensive and integrated web application. Regards, Tony Freeman TEAMXL 678.344.2305 Office 509.693.2598 eFax [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
