Thanks, Claus. All right, I guess I will construct the deserializer with the component so that it has access to the context and can operate as intended. I was thinking more about how the dynamic router subscribers should not have any dependency on the router, so if they could create their subscription messages in JSON format, then that would be another way to remove that dependency (along with the URI method that you suggested when I was writing this EIP component). Is there some reason why the static method was bad? Specifically, what makes the Simple language dependent on a context for parsing? For evaluation, I can easily see the need.
On Sun, Nov 13, 2022 at 12:27 PM Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > All of Camel generally requires CamelContext, either in constructor or to > be set via setter. > Especially, simple language as its Camels own language. > > > > On Sun, Nov 13, 2022 at 5:19 PM Steve973 <steve...@gmail.com> wrote: > > > Hello. Is there some non-deprecated equivalent > > to SimpleLanguage.predicate(simpleExpressionString) to use when we do not > > have a reference to the CamelContext? I am using it for JSON > > deserialization, where I don't have the context. > > > > Thanks, > > Steve > > > > > -- > Claus Ibsen > ----------------- > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
