Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
CAMEL-13792 - Rename components to default names, Camel-quartz2 to camel-quartz

    • -303
    • +0
    ./CronScheduledRoutePolicyTest.java
    • -50
    • +0
    ./RouteAutoStopFalseCronScheduledPolicyTest.java
    • -73
    • +0
    ./SimpleScheduledCombinedRoutePolicyTest.java
    • -261
    • +0
    ./SimpleScheduledRoutePolicyTest.java
    • -51
    • +0
    ./SpringCronScheduledRoutePolicyTest.java
    • -48
    • +0
    ./SpringMultiplePoliciesOnRouteTest.java
    • -94
    • +0
    ./SpringQuartzTwoAppsClusteredFailoverTest.java
    • -137
    • +0
    ./SpringScheduledRoutePolicyTest.java
    • -51
    • +0
    ./SpringSimpleScheduledRoutePolicyTest.java
  1. … 213 more files in changeset.
CAMEL-13555: Producer and consumer template/cache should check if camel is started when being used

    • -6
    • +0
    ./RouteAutoStopFalseCronScheduledPolicyTest.java
CAMEL-13336: update license headers

    • -1
    • +1
    ./RouteAutoStopFalseCronScheduledPolicyTest.java
    • -1
    • +1
    ./SimpleScheduledCombinedRoutePolicyTest.java
    • -1
    • +1
    ./SpringCronScheduledRoutePolicyTest.java
    • -1
    • +1
    ./SpringMultiplePoliciesOnRouteTest.java
    • -1
    • +1
    ./SpringQuartzTwoAppsClusteredFailoverTest.java
    • -1
    • +1
    ./SpringSimpleScheduledRoutePolicyTest.java
  1. … 17913 more files in changeset.
CAMEL-8293: camel-test should use Registry and let user bind beans more easily instead of having to use JndiRegistry.

  1. … 46 more files in changeset.
Fixed CS for Camel-Quartz2

  1. … 3 more files in changeset.
Move service helper classes into a separate package to avoid split packages for OSGi

  1. … 348 more files in changeset.
Isolate o.a.c.management from o.a.c.impl

  1. … 48 more files in changeset.
Move stuff around to isolate o.a.c.util from o.a.c and o.a.c.support from o.a.c.impl

# Conflicts:

# camel-core/src/main/java/org/apache/camel/impl/InterceptSendToEndpointProcessor.java

  1. … 2742 more files in changeset.
[CAMEL-10469] Remove @version in java source code

  1. … 3762 more files in changeset.
[CAMEL-12818] Remove deprecated stuff

    • -13
    • +13
    ./CronScheduledRoutePolicyTest.java
    • -2
    • +2
    ./SimpleScheduledCombinedRoutePolicyTest.java
  1. … 1268 more files in changeset.
CAMEL-1202: use the old default of not block for direct in these tests as they rely on that.

    • -2
    • +11
    ./CronScheduledRoutePolicyTest.java
    • -1
    • +3
    ./SimpleScheduledCombinedRoutePolicyTest.java
    • -4
    • +11
    ./SimpleScheduledRoutePolicyTest.java
  1. … 2 more files in changeset.
CAMEL-11261 Revise Camel context destruction in...

... Spring (Boot) applications

This changes the way `CamelContext` is started/stopped when used with

Spring Framework. It uses `ContextRefreshedEvent` for startup and

`Lifecycle::stop` to stop, the reason why `Lifecycle` can't be used for

startup is that only beans that implement `SmartLifecycle` are started

and `SpringCamelContext` can't implement `SmartLifecycle` because of

overlapping `isAutoStartupMethod` in `RuntimeConfiguration` and

`SmartLifecycle` with different return types -- that cannot be used as

covariant return type as the `SmartLifecycle` signature uses primitive

type.

The order of startup is quite important, as some changes to Camel

context are not properly expressed if made after context startup (for

instance `EndpointStrategy` change), so `SpringCamelContext` has

`LOWEST_PRECEDENCE` and `RoutesCollector`s, `CamelContextFactoryBean`

have +1 precedence over that in order to add routes and setup context

before startup.

Using `ContextRefreshedEvent` is actually better than using

`SmartLifecycle` as `SmartLifecycle` invocation precedes

`ContextRefreshedEvent` emission, so there could be beans in the context

that also start on `ContextRefreshedEvent` and Camel would start before

those.

One side note on using events is that at some point Spring might

default, however unlikely that seems, to using multi-threaded event

listener invocation, so this might complicate things.

    • -5
    • +5
    ./SpringQuartzTwoAppsClusteredFailoverTest.java
  1. … 31 more files in changeset.
Fixed tests

  1. … 5 more files in changeset.
CAMEL-9424 Correctly build TriggerKey using the trigger prefix relevant to the Action. This fixes the fuplicate trigger name issue when setting both start and stop route times on a CronScheduledRoutePolicy.

    • -0
    • +56
    ./CronScheduledRoutePolicyTest.java
  1. … 1 more file in changeset.
CAMEL-9424 Correctly build TriggerKey using the trigger prefix relevant to the Action. This fixes the fuplicate trigger name issue when setting both start and stop route times on a CronScheduledRoutePolicy.

    • -0
    • +56
    ./CronScheduledRoutePolicyTest.java
  1. … 1 more file in changeset.
Fixed Quartz2 component tests

Fixed Quartz2 component tests

CAMEL-6365: Better reuse the IOHelper utility to close the Spring contexts.

    • -6
    • +4
    ./SpringQuartzTwoAppsClusteredFailoverTest.java
  1. … 5 more files in changeset.
CAMEL-7030: quartz components now register the quartz scheduler in JMX by default, unless configured not to do so by end user. Fixed route policy tests using custom date type instead of using the java.util.Date.

  1. … 52 more files in changeset.
Polished the comment of the tests being recently added into the codebase.

    • -4
    • +2
    ./SpringQuartzTwoAppsClusteredFailoverTest.java
  1. … 4 more files in changeset.
Polished the comment of the tests being recently added into the codebase.

    • -4
    • +2
    ./SpringQuartzTwoAppsClusteredFailoverTest.java
  1. … 4 more files in changeset.
Polished the comments a bit.

    • -5
    • +7
    ./SpringQuartzTwoAppsClusteredFailoverTest.java
  1. … 1 more file in changeset.
Polished the comments a bit.

    • -5
    • +7
    ./SpringQuartzTwoAppsClusteredFailoverTest.java
  1. … 1 more file in changeset.
Polished the test SpringQuartzTwoAppsClusteredFailoverTest to be aligned with the same test in camel-quartz.

    • -10
    • +12
    ./SpringQuartzTwoAppsClusteredFailoverTest.java
  1. … 7 more files in changeset.
Polished the test SpringQuartzTwoAppsClusteredFailoverTest to be aligned with the same test in camel-quartz.

    • -10
    • +12
    ./SpringQuartzTwoAppsClusteredFailoverTest.java
  1. … 7 more files in changeset.
CAMEL-6782: Polished.

    • -1
    • +1
    ./SpringQuartzTwoAppsClusteredFailoverTest.java
  1. … 3 more files in changeset.
CAMEL-6782: Polished.

    • -1
    • +1
    ./SpringQuartzTwoAppsClusteredFailoverTest.java
  1. … 3 more files in changeset.
CAMEL-6782: Added test demonstrating the failover of Camel routing inside a clustered quartz setup.

    • -85
    • +0
    ./SpringQuartzPersistentStoreClusteredAppTest.java
    • -0
    • +94
    ./SpringQuartzTwoAppsClusteredFailoverTest.java
  1. … 4 more files in changeset.
CAMEL-6782: Added test demonstrating the failover of Camel routing inside a clustered quartz setup.

    • -85
    • +0
    ./SpringQuartzPersistentStoreClusteredAppTest.java
    • -0
    • +94
    ./SpringQuartzTwoAppsClusteredFailoverTest.java
  1. … 4 more files in changeset.
Corrected the typo.

    • -1
    • +1
    ./SpringQuartzPersistentStoreClusteredAppTest.java