Thanks, Claus. I have it working with the entire URL in "toD", but the endpoint element has better aesthetics, so I was hoping that would be a viable option. It's not a big deal, though. I finally have everything working, and a little bit more testing to do. It's a shame to have to copy so much code that the Reifier does, though! It's all a lot cleaner except for the duplicated code.
On Mon, Dec 4, 2023 at 12:24 AM Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > That is just an endpoint, its not something evaluated for a given > exchange/message when being defined. > > So you need to just configure them as string literals as-is. > So they have special meaning for your component. But what you do is wrong. > > If you need dynamic uris in Camel then you use toD for example. > > What a component often do, is to have known headers that can override > configuration options, like JMS has for some of its values. > > https://camel.apache.org/components/4.0.x/jms-component.html#_message_headers > > > On Sun, Dec 3, 2023 at 10:19 PM Steve973 <steve...@gmail.com> wrote: > > > Hello. I am writing tests for my component with Spring, and configuring > in > > xml. How can I specify these values so that it looks in the header, > > instead of interpreting these as literal string values? > > > > <endpoint id="subscribe-no-url-predicate" > > uri="dynamic-router-control://subscribe"> > > <property key="subscribeChannel" > value="${headers.subscribeChannel}"/> > > <property key="subscriptionId" value="${headers.subscriptionId}"/> > > <property key="destinationUri" value="${headers.destinationUri}"/> > > <property key="priority" value="${headers.priority}"/> > > </endpoint> > > > > Thanks, > > Steve > > > > > -- > Claus Ibsen > ----------------- > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
