Not sure if I totally get the requirement.
But, generally as for as I have used, the work flow is:
1. Decide on all the things that can be configured by users
2. Externalize them into properties
3. Use those properties in your routes
4. Can access them in resolve method as you are aware of these special
properties
5. Can be changed externally
You can also use custom PropertiesFuction to may be get these values from
database that are changed by User from some UI.
Or is your user inputting the route itself from UI with any possible
properties? If this is the case I recommend to restrict what users can
input/use as properties or validate that they add those into some DB and your
custom function can read from there.
-Shreyas
----------------------------------------
> Date: Wed, 11 Mar 2015 11:23:02 -0700
> From: derek.abd...@gmail.com
> To: dev@camel.apache.org
> Subject: RE: Pulling property placeholders out of camel route definitions
>
> Hey Shreyas, thanks for the reply.
>
> In this case, I want to pull out all variables from a compiled
> RouteDefinition, be it that route was provided by the Java DSL or XML DSL.
>
> CamelContext#resolvePropertyPlaceholders(String) to my knowledge, works by
> passing in a string template with variables in it, such as:
>
> context.resolvePropertyPlaceholders("{{foo}}");
>
> In this case, consider the string passed in to resolvePropertyPlaceholders
> out of my control. I want to take an aribtrary string that *may* have
> property placeholders in it, pull out those properties and ask the user / a
> system component for them to set them on the camel context so that I may
> then call resolvePropertyPlaceholders on that string with those properties
> fulfilled.
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Pulling-property-placeholders-out-of-camel-route-definitions-tp5763960p5764017.html
> Sent from the Camel Development mailing list archive at Nabble.com.
