yes… definitely agree on locking down the config file.
But I'm more worried about a regression at some future point. Unit tests
go a long way… but I can also put in guards in the code to prevent it from
even working with a broken broker by verifying that things are sane when it
connects to the br
it is a very general requirement.
one approach is to have some sort of ping test of broker functionality
that you require.
deploy a camel route in the xml config.
have it do jms request/reply after it has done some validation like
produce/consume an advisory.
Then to validate ping that route. Wit
