right now we have access to the CamelToEndpoint exchange property, immediately following the direct/seda/vm consumer. The URI value of exchange.CamelToEndpoint can be preserved in a header and accessed later in the route to retrieve the custom/dynamic parameters from the querystring.
It is not too pretty, but it would work. There could also be a new boolean option "allowCustomOptions" that would in effect turn syntax checking on/off for the direct/seda/vm producer endpoint. As it currently stands, attempting to add a custom option on the direct/seda/vm producer endpoint results in a "Failed to resolve endpoint" error when deploying the bundle. Another idea would be to check the producer endpoint for a matching consumer endpoint i.e. custom options on the producer endpoint URI querystring must match an option on an existing consumer endpoint URI querystring. It would act the same way as it currently acts when you misspell a valid option. BTW - thanks for the fast reply! best regards, ala -- View this message in context: http://camel.465427.n5.nabble.com/Passing-parameters-to-a-direct-seda-vm-endpoint-tp5742567p5742621.html Sent from the Camel - Users mailing list archive at Nabble.com.