Ok cool. So to be clear - if I want Camel to spin up an instance of a processor dynamically from a classname I have to use "to()" and not "process()".
Ty!! 😊 On Fri, Jan 22, 2021, 7:40 AM Claus Ibsen <claus.ib...@gmail.com> wrote: > Yes that is correct. > > For FQN classnames and the required work to initailize and instance of > it (if needed) et all - is what the bean component is needed for > > The process is for basic java where it requires an object instance. > > On Fri, Jan 22, 2021 at 3:14 PM David Holiday <david.holi...@holitek.io> > wrote: > > > > Hello fellow camel riders! > > > > Whenever I make a processor I have to access it i. DSL using "to()". > When I > > attempt to access it using "process()" i get an error message telling me > > the class could not be found in the registry. > > > > I did some experimentation and it seems as though I can use "process()" > if > > I supply a lambda. In my application I am supplying class names as > > parameters to the DSL calls. > > > > Is it the case that "process()" isn't ok with taking a classname and > > instead requires a processor object supplied either by lambda or by there > > being an object already present in the registry? > > > > Thx!! > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
