[
https://issues.apache.org/jira/browse/CAMEL-16757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376278#comment-17376278
]
Claus Ibsen edited comment on CAMEL-16757 at 8/3/21, 9:46 AM:
--------------------------------------------------------------
TODO:
- Collect routes vs build routes: Use 2 pass so we collect all resources first,
and then use 1st pass to load only routes configuration. And 2nd pass to load
the rest *DONE*
- RouteBuilder Java DSL should we have routesConfiguration() in its own class?
*DONE*
- RoutesConfiguration: Add interceptor, on completion *DONE*
- RoutesConfiguration: Add error handler (this requires to move the error
handler definition from spring dsl, blueprint dsl into core dsl)
- RoutesLoader to support new routes-configuration *DONE*
- Classic XML DSL for spring/blueprint to use routes-configuration instead of
its own way *WONT FIX*
- Allow to configure data formats *WONT FIX*
- Allow to configure endpoints? (see classic spring/blueprint <camelContext>)
*WONT FIX*
- Documentation
- Examples (main *DONE*, spring boot *DONE*, quarkus)
- RouteConfiguration to have ID and reusable as global or per route; a route
can then refer to the configuration id *DONE*
- Java DSL prepare eager problem *DONE*
- RoutesConfiguration rename to RouteConfiguration *DONE*
- Scrub auto assigned ids when applied again
- EndpointRouteConfigurationBuilder in camel-endpointdsl *DONE*
- Startup summary logging of routes configuration (option to tweak logging
level) *DONE*
- Logging of which route is using which routes configurations *DONE*
- JMX MBean attribute for routes *DONE*
- classic spring xml support *DONE*
- classic cdi xml support *DONE*
- classic osgi blueprint support *DONE*
- check for duplicate route configuration ids *DONE*
was (Author: davsclaus):
TODO:
- Collect routes vs build routes: Use 2 pass so we collect all resources first,
and then use 1st pass to load only routes configuration. And 2nd pass to load
the rest *DONE*
- RouteBuilder Java DSL should we have routesConfiguration() in its own class?
*DONE*
- RoutesConfiguration: Add interceptor, on completion *DONE*
- RoutesConfiguration: Add error handler (this requires to move the error
handler definition from spring dsl, blueprint dsl into core dsl)
- RoutesLoader to support new routes-configuration *DONE*
- Classic XML DSL for spring/blueprint to use routes-configuration instead of
its own way *WONT FIX*
- Allow to configure data formats *WONT FIX*
- Allow to configure endpoints? (see classic spring/blueprint <camelContext>)
*WONT FIX*
- Documentation
- Examples (main *DONE*, spring boot *DONE*, quarkus)
- RouteConfiguration to have ID and reusable as global or per route; a route
can then refer to the configuration id *DONE*
- Java DSL prepare eager problem *DONE*
- RoutesConfiguration rename to RouteConfiguration *DONE*
- Scrub auto assigned ids when applied again
- EndpointRouteConfigurationBuilder in camel-endpointdsl *DONE*
- Startup summary logging of routes configuration (option to tweak logging
level) *DONE*
- Logging of which route is using which routes configurations *DONE*
- JMX MBean attribute for routes *DONE*
- classic spring xml support *DONE*
- classic cdi xml support *DONE*
- classic osgi blueprint support
- check for duplicate route configuration ids *DONE*
> camel-core - Allow to define global error handling in all DSL the same way
> --------------------------------------------------------------------------
>
> Key: CAMEL-16757
> URL: https://issues.apache.org/jira/browse/CAMEL-16757
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 3.12.0
>
>
> In the legacy camel-spring-xml and camel-blueprint you have <camelContext>
> where you can setup global error handlers, interceptors etc
> In the microservice world we may want to look at allowing to have a
> <camelConfiguration> or some other name, where you can drop that as a file
> into the routes loader to setup global error handling, and so on.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
