Follow up on my nightmare! It turns out the reason I couldn't get things to work is that MS JDBC driver doesn't support Blob's, hence the reason I am constantly getting errors everytime the Quartz code call's getBlob()!
I am patching that, and aside from that MS specific problem, quartz will rock. Now, my other question, and I am hoping some of the people with more experience with Turbine development will chime in. It seems that the SchedulerService interface is pretty rigid, mainly requiring Jobentry's which have very specific values, that don't really map well onto the Quartz model. So, I am trying to figure out, should I 1) try and continue to support the existinging interfaces (even if some of the code get's nasty) 2) Change the existing interfaces to be more generic so the old stuff and Quartz will work 3) Ignore the old scheduler, and just add my new one in parrale. In addition, I am looking at the T2.1 code base b/c that is what I am in production with. Should I try and submit this code against the T2.2 codebase or against Fulcrum? Also, if anyone else is interested in collaborating, please let me know.... Thanks, Eric -----Original Message----- From: Eric Pugh [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 01, 2002 3:09 PM To: Turbine Developers List (E-mail) Subject: Quartz Scheduler Hi all, I wanted to post my work with Quartz.. Quartz seems very powerful, and I didn't have much difficulty wrapping it up in a service. However, I am currently stuck because I can't seem to get MS's JDBC Driver to successfully work (inside of Turbine) with Quartz's use of BigInt's. However, Quartz has been developed extensively against MySql and Oracle.. So I am going to table my work for now until I get some more enthusiasm to wrestle with MS's JDBC driver. Good Luck, and I hope to see Quartz succesfully integrated in! Eric This is what you add to your TR.props: # Configure Main Scheduler Properties ====================================== scheduler.quartz.org.quartz.scheduler.instanceName = Sched1 scheduler.quartz.org.quartz.scheduler.logger = schedLogger # Configure Logger(s) ====================================================== scheduler.quartz.org.quartz.logger.schedLogger.class = org.quartz.impl.Log4jLogger scheduler.quartz.org.quartz.logger.schedLogger.categoryName = scheduler scheduler.quartz.org.quartz.logger.tpLogger.class = org.quartz.impl.Log4jLogger scheduler.quartz.org.quartz.logger.tpLogger.categoryName = scheduler.threadPool scheduler.quartz.org.quartz.logger.jsLogger.class = org.quartz.impl.Log4jLogger scheduler.quartz.org.quartz.logger.jsLogger.categoryName = scheduler.persistence # Configure ThreadPool ===================================================== scheduler.quartz.org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool scheduler.quartz.org.quartz.threadPool.threadCount = 3 scheduler.quartz.org.quartz.threadPool.threadPrio = 4 scheduler.quartz.org.quartz.threadPool.logger = tpLogger # Configure JobStore ======================================================= scheduler.quartz.org.quartz.jobStore.class = org.quartz.impl.JDBCJobStore scheduler.quartz.org.quartz.jobStore.dataSource = myDS scheduler.quartz.org.quartz.jobStore.tablePrefix = QRTZ_ scheduler.quartz.org.quartz.jobStore.logger = jsLogger # Configure Datasources ==================================================== scheduler.quartz.org.quartz.dataSource.myDS.driver = com.microsoft.jdbc.sqlserver.SQLServerDriver scheduler.quartz.org.quartz.dataSource.myDS.URL = jdbc:microsoft:sqlserver://myserver:1433;DatabaseName=kinaseprofiler scheduler.quartz.org.quartz.dataSource.myDS.user = myuser scheduler.quartz.org.quartz.dataSource.myDS.password = mypassword scheduler.quartz.org.quartz.dataSource.myDS.maxConnections = 13 Good luck, and I hope someone else can validate it's working. I can get it to run outside of Turbine, but not successfully inside of turbine. Eric -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
