Requirements and Restrictions

On this page, we present the requirements and restrictions that must be followed when developing and configuring integration flows. These guidelines are essential to ensure the correct implementation and expected functioning of your project.

  • File requirements

    • File format: the file content must be a syntactically valid .yaml.

  • Route limit: the file can have at most one route that is not of the type from: direct:xxx.

    • This route will be the trigger for the integration flow.

  • Requirements for triggers and components in steps

    • Triggers: the component specified in the trigger must be a consumer.

      • If a non-consumer component is used in the trigger, the flow can still proceed, but an error will be displayed during deployment.

    • Components in steps: the component specified in a flow step must be a producer.

      • If a non-producer component is used in a flow step, the flow can still proceed, but an error will be displayed during deployment.

  • Rules for URLs and EIPs

    • URLs in EIPs must reference approved components.

    • EIP Process: you can use processes that are already natively available in Camel, but creating new processes is currently disabled.

Naming and prefixes

  • Route names: creating routes with names that start with the prefix sensedia_ is not allowed.

Global configuration restrictions ** Prohibited configurations:

  • beans;

  • errorHandler;

  • onException;

  • routeConfiguration;

  • route;

  • routeTemplate;

  • templatedRoute;

  • rest (you must use from: rest).

Thanks for your feedback!
EDIT

Share your suggestions with us!
Click here and then [+ Submit idea]