Ad 1)
Its the new endpoint-dsl. Those expressions will be like that. Using
getUri is a workaround but not ideal.
We can see if we can improve this in camel-management. You are welcome
to create a JIRA about this.
Ad 2)
Yeah that too is a little bug. You can do a PR to implement and
return true in ManagedPollEnricher like ManagedEnricher does.
On Mon, Dec 14, 2020 at 7:24 PM CASAUX Nicolas
<nicolas.cas...@soprasteria.com> wrote:
>
> Hello !
>
> I may have found two minor bugs with data available from processors through
> JMX.
>
> 1)
> When I use processors like :
> .enrich().constant(direct("myEndpoint").failIfNoConsumers(false))
> in JMX data, the exposed "ExpressionLanguage" is empty, and the "Expression"
> is something like
> "org.apache.camel.builder.ExpressionClause@7c098bb3<mailto:org.apache.camel.builder.ExpressionClause@7c098bb3>"
>
> Similar issue happens with pollEnrich, and probably other processors.
> Workaround for that was to add a ".getUri()" :
>
>
> .enrich().constant(direct("enrichConstant").failIfNoConsumers(false).getUri())
>
> 2)
> Processor "pollEnrich" says it does not support extended information
> (SupportExtendedInformation=false), however, it does support it.
> There are indeed some data available with the "extendedInformation" operation.
> Maybe some other processors have the same problem.
>
> I can of course create jira(s) if it makes sense.
>
> Regards,
> Nicolas
>
>
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
