[ 
https://issues.apache.org/jira/browse/CAMEL-25466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18126965#comment-18126965
 ] 

Claus Ibsen commented on CAMEL-25466:
-------------------------------------

Done in 
https://github.com/apache/camel/commit/d167b11e673837a71f6a116be7a7152952dabcc0 
(the work of CAMEL-25466 and CAMEL-25467 is squashed into one commit):
* The architecture view of the monitor gets {{x}}: the routes reached only on 
error move out of Utility into an Error handling box, with a dashed arrow from 
each group whose failures go there. With {{x}} on, the topology, the route view 
and the Info panel name that group too.
* {{camel cmd route-topology --errors}} and {{camel cmd route-diagram 
--errors}} draw the error handling in a frame below the routes or the steps, as 
the monitor does. With {{--external}}, the external systems only those routes 
use are drawn in the frame as well.
* A route diagram now draws only the steps of a route: the CLI, the 
{{route-diagram}} dev console and its web components, and the dumped diagrams. 
To draw the error handling, use {{errors=true}} in the dev console, the 
{{errors}} attribute of the web components, or the {{errors}} option of 
{{DumpRoutesStrategy}} ({{@EnableRouteDiagramDump}}, {{@CamelMainTest}}). A 
highlighted path that steps into an onException clause draws the frame too. The 
topology web component no longer draws the error paths as calls.
* route-structure leaves out the onException clauses of a route with 
{{noErrorHandler}}, as they never run there.
* The monitor draws the frames with the camel-diagram classes, and a send in an 
error frame is no longer counted as a call.

Notes are in the 4.24 upgrade guide. Related: CAMEL-25631 (deprecate 
{{Route.clearRouteModel}}), CAMEL-25636 (the label of marshal and unmarshal), 
and the example: https://github.com/apache/camel-jbang-examples/pull/112

_Claude Code on behalf of Claus Ibsen_

> camel-jbang - error handling in the diagram exports and the monitor's 
> architecture view
> ---------------------------------------------------------------------------------------
>
>                 Key: CAMEL-25466
>                 URL: https://issues.apache.org/jira/browse/CAMEL-25466
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jbang
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 4.24.0
>
>
> Follow-up of CAMEL-25429, which made the route topology tell calls from error 
> paths (kind, via, handling) and gave the camel-jbang monitor's topology and 
> route view an error-handling frame (x).
> Still to do:
> * *Diagram exports*: camel-diagram (PNG, SVG, ASCII) and camel cmd 
> route-diagram draw the happy path only. An option (e.g. errors=true) to 
> include the error handling as in the monitor: the routes reached only on 
> error in a frame of their own, under each where its failures come from and 
> how they are handled, so a picture in docs or a PR can show it. 
> TopologyHelper.parseEdges(jo, true) already gives the error paths.
> * *Architecture view* of the monitor: with x on, an "Error handling" box next 
> to the groups, holding the routes reached only on error (today in Utility), 
> with the groups that send failures to them. Today x only applies to the 
> topology and the route view.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to