Peter Durcansky - [25/Jul/06 10:30 AM ] I actually liked sample quartz-service.xml in the quartz-jboss-xxx.jar - it gave me a head start to set up the configuration; but that's just my preference. I understand you do not want to pollute the JAR file. It would be nice to have a link or the config file location mentioned in the manifest.mf in the archive (if possible). ============= Another comment: The file contains:   <classpath codebase="." archives="quartz.jar"/> I do not think it is hurting (JBoss 3.2.x seems to silently ignore incorrect classpath settings) but the archive parameter is wrong - it will be either quartz-jboss-1.6.0.jar or quartz-all-1.6.0.jar. Perhaps the safe option would be to leave out the <classpath> element in the service definition example (JBoss uses flat classloaders and so just dropping the library in server/<configName>/lib or deploy directory is sufficient). Peter

Jasper Rosenberg - [25/Jul/06 10:46 AM ] The quartz-service.xml in the jar was actually causing me problems because JBoss 4 was picking it up (and for example I had had a different name for my quartz datasource). It was never actually intended to be in the jar, and for 1.6 the file is now correctly being included in the javadocs, so it should still be easy to find and use as a starting point. With regards to the classpath element, I agree it seems unnecessary, and I will remove it.