Thanks for the response. The way I am using properties file is I am using an incoming request's parameter as a key to look up the properties file to find the correct route to use. But for an invalid request parameter, I want to check for its existence in the properties file before using it.
So, it's not a design time check but a runtime check. One possible solution I could think of was to create a separate bean using Java Properties class and use that to check for it. But, it seemed natural from Camel PropertiesComponent to expect a null or an empty string if the key didn't exist. I also tried catching the java.lang.IllegalArgumentException in that route, but that did not seem to work. But I will try that again. Thanks. -- View this message in context: http://camel.465427.n5.nabble.com/Using-Camel-properties-tp5748299p5748339.html Sent from the Camel - Users mailing list archive at Nabble.com.
