검색

이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Chapter 14. Setting Breakpoints

download PDF

Overview

To set breakpoints, your project’s routing context .xml file must be open in the route editor’s Design tab.

The Camel debugger supports two types of breakpoints:

  • Unconditional breakpoints — triggered whenever one is encountered during a debugging session
  • Conditional breakpoints — triggered only when the breakpoint’s specified condition is met during a debugging session
Note

You cannot set breakpoints on consumer endpoints or on when or otherwise nodes.

Setting unconditional breakpoints

With your routing context displayed on the canvas in the Design tab:

  1. Select a node whose state you want to examine during the debugging session.
  2. Click its red dot icon to set an unconditional breakpoint.
  3. Repeat these steps for each node on which you want to set an unconditional breakpoint.

Setting conditional breakpoints

With your routing context displayed on the canvas in the Design tab:

  1. Select a node whose state you want to examine during the debugging session.
  2. Click its yellow dot icon to set a conditional breakpoint and to open the Edit the condition and language of your breakpoint…​ dialog:

    debug CondBPCnfg
  3. Click the Language drop-down menu and select the expression language to use to create the condition that will trigger the breakpoint.

    Fuse Tooling supports twenty-four expression languages. Some of these languages provide variables for creating conditional expressions, while others do not.

  4. Click Variables to display a list of the selected language’s supported variables.

    If a list appears, select in sequence one or more of the variables to create the condition for triggering the breakpoint. The variables you select appear in the Condition text box.

    If expressLangNoVars appears, enter the expression directly into the Condition text box.

  5. Repeat steps [condBpFirst] through [condBpLast] for each node on which you want to set a conditional breakpoint.

Disabling breakpoints

You can temporarily disable a breakpoint, leaving it in place, then enable it again later. The resume co button skips over disabled breakpoints during debugging sessions.

To disable a breakpoint, select the node on the canvas and click its gray dot icon. The breakpoint turns gray, indicating that it has been disabled.

To enable a disabled breakpoint, select the node on the canvas and click its green dot icon. Depending on whether the disabled breakpoint is conditional or unconditional, it turns yellow or red, respectively, to indicate that it has been re-enabled.

Note

You can also disable and re-enable breakpoints during debugging sessions. For details, see Chapter 19, Disabling Breakpoints in a Running Context.

Deleting breakpoints

You can delete individual breakpoints or all breakpoints.

  • To delete individual breakpoints — in a route container, select the node whose breakpoint you want to delete, and click its delete bp icon.
  • To delete all breakpoints in a particular route — right-click the target route’s container, and select gray dot Delete all breakpoints.
  • To delete all breakpoints in all routes — right-click the canvas, and select gray dot Delete all breakpoints.
Red Hat logoGithubRedditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

© 2024 Red Hat, Inc.