gnodet wrote: > > Of course the drawback is that you have to know which value in the > xbean.xml > can change and design the configuration around them. >
Exactly; on an ideal world, where users come up with perfect lists of requirements, this would not be a problem, we would know exactly which parameters may be subject to change. But we're not there yet... gnodet wrote: > > A better way would be to use a BeanFactoryPostProcessor like the > PropertyPlaceholderConfigurer, but one which would look the actual value > from the database. > > <beans xmlns:quartz="http://servicemix.apache.org/quartz/1.0"; > xmlns:foo="http://foo.org/foo";> > <quartz:endpoint service="foo:scheduler" endpoint="endpoint" > targetService="foo:quartzFilter"> > <quartz:trigger> > <quartz:cron cronExpression="0 0/30 * * * ?" /> > </quartz:trigger> > </quartz:endpoint> > > <bean class="com.foo.DataBasePostProcessor"> > <property name="service" value="foo:scheduler" /> > <property name="endpoint" value="endpoint" /> > <property name="dataSource" ref="dataSource" /> > </bean> > <bean id="dataSource" ... /> > </beans> > > This surely could be refined, but what about the idea ? > Both ideas are great, but lack the "future-proof" feature we would like to have; btw, we also thought of jmx, exposing methods to change the parameters, but this would also be an "a priori" effort gnodet wrote: > > As I said in another thread, I think a dup remover could be a good > fit for a new EIP pattern. You would still need an expression to > find a unique key for an exchange, but it would be more clean imho. > Agreed gnodet wrote: > > What kind of problems did you had ? I haven't tried to cluster quartz, > but I don't see why it would not be possible. > I only had one problem: I typed "quartz clustering" in google, clicked "feeling lucky" and gave up on the first yellow box with the hazard sign -- View this message in context: http://www.nabble.com/listeners-in-container-and-MessageExchange-tf2815007s12049.html#a7872265 Sent from the ServiceMix - User mailing list archive at Nabble.com.
