I’m sorry Guillaume, but I don’t see the similarity, although you may know something I don’t. In any case do you know of a workaround?, basically I need to be able to enable tracing of exchange headers (in Blueprint) for troubleshooting, but I have not yet found how.
Best regards, Alex soto > On Feb 5, 2020, at 11:59 AM, Guillaume Nodet <gno...@apache.org> wrote: > > Looks similar to > https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-14462 > I need to investigate it asap. > > Le mer. 5 févr. 2020 à 17:48, Alex Soto <alex.s...@envieta.com> a écrit : > >> This used to work with Camel 2.X, now it seems it is ignoring the >> settings >> >> >> <!--Enable logging of Exchange properties when tracing--> >> <bean id="traceFormatter" >> class="org.apache.camel.support.processor.DefaultExchangeFormatter"> >> <property name="showProperties" >> value="#{camel.trace.showProperties}"/> >> <property name="showExchangePattern" >> value="#{camel.trace.showExchangePattern}"/> >> <property name="showExchangeId" >> value="#{camel.trace.showExchangeId}"/> >> <property name="showBody" value="#{camel.trace.showBody}"/> >> <property name="showHeaders" value="#{camel.trace.showHeaders}"/> >> </bean> >> >> <camelContext xmlns="http://camel.apache.org/schema/blueprint"; >> id="admin" trace=“true”> >> >> Specifically, when I set the showHeaders property to true the exchange >> headers are still not logged. Any idea? >> >> >> Best regards, >> Alex soto >> >> >> >> >> > > -- > ------------------------ > Guillaume Nodet
