|
From: Michael A. <mic...@ze...> - 2003-12-02 10:37:34
|
Hi, I've also committed changes to the jmx scanner, including a jar rule which creates a jboss service archive, which can simply be copied into the jboss deploy directory. Hot deploy works. Not sure the hot undeploy works quite as well. I seem to get stray documents being placed into the pipeline after restarting from a hot undeploy. Anyway, after running the jboss rule, copy your pipeline/, scanner/, resource/, feeder/ and journal/ directories into the jboss conf directory, and then copy the .sar file to the jboss deploy directory. If necessary, start jboss. You scanners should be active. It's still not as stable as I would like. I have added a property so that the babeldoc_home and babeldoc_user properties can be set in the jmx-console. I have defaulted them both to the conf directory, although I'm sure it's not quite right. Seems to work though. Also, I've only tested this with the SqlQuery, DirectoryScanner, JFreeReport and FileWriter stages/scanners. There may be classpath issues with other stages. This stuff is available (until I merge it into the HEAD) on the TEMP_MIKEA branch (cvs update babeldoc -r TEMP_MIKEA). PLEASE NOTE: this is development code, and should not yet be used in production systems. Have fun, bug reports readily accepted... MikeA |