|
From: Patrick Y. <kc...@ce...> - 2004-06-26 07:32:36
|
Ronald van Kuijk wrote: > Yes, sounds obvious, I'm looking into one new 'hook' now. My > JMSMonitor should not be included in the core since it makes it j2ee > dependend. What I'm doing now is make a 'Monitors' object that reads > something like this from the general config: > > <Monitors> > <MonitorItem> > <Class>tld.mycompany.monitor.MyMonitorImpl</Class> > <ConfigFile>/my/configFile.xml</ConfigFile> > </MonitorItem> > <MonitorItem> > ..... > </MonitorItem> > </Monitors> > > Even the MailMonitor that you provide by default could be included > this way, and instead of the ConfigFile reference the properties could > in the default configfile e.g. with a <Properties> tag instead of > <ConfigFile> This currently works great for me and keeps the default > distribution clean of j2ee dependend things. > Is the proposed JMS Monitor for dispatching received message (like what Philipp proposed)? Or it's for getting incoming message from the internet (like what MailMonitor is doing)? I am a bit confused. I like the concept of keeping the distribution clean and making the configuration independent. > This is exactely what I've been banging my brains on as well. > Especially in relation to clustering. I have some Ideas on how to make > it pluggable as well so a 'simple' servlet based version uses the > implementation like it is now, and for clustered versions there is > maybe a dependency on j2ee things. > Please share more on this. Thanks. :-) > Is there any reason not to call the current HEAD in cvs version 1.0? > We have to wait for the completion of internal testing here. Another team in our center will use Hermes to do consultancy projects. Therefore, we are doing some quality assurance testing now. Regards, -Patrick |