Re: [VOTE] Release Apache Camel Kamelets 4.4.2

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Tue, Apr 30, 2024 at 10:48 AM Andrea Cosentino  wrote:
>
> Hello all,
>
> This is a vote for releasing camel-kamelets 4.4.2
>
> This is a release supporting Camel 4.4.2 and it's an LTS release.
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.4.2
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1707
> Kamelets Tag:
> https://github.com/apache/camel-kamelets/releases/tag/v4.4.2
>
> Please cast your vote.
>
> [ ] +1 Release camel-kamelets 4.4.2
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino

Re: [VOTE] Release Apache Camel Kamelets 4.4.1

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Fri, Mar 22, 2024 at 7:05 AM Andrea Cosentino  wrote:
>
> Hello all,
>
> This is a vote for releasing camel-kamelets 4.4.1
>
> This is the second release of camel-kamelets supporting LTS Camel 4.4.x and
> it contains alignment to 4.4.1 and some fixes.
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.4.1
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1687
> Kamelets Tag:
> https://github.com/apache/camel-kamelets/releases/tag/v4.4.1
>
> Please cast your vote.
>
> [ ] +1 Release camel-kamelets 4.4.1
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino

Re: [VOTE] Release Apache Camel Kamelets 4.0.1

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Tue, Sep 26, 2023 at 10:13 AM Andrea Cosentino  wrote:
>
> Hello all,
>
> This is a vote for releasing camel-kamelets 4.0.1
>
> This release will support the 4.0.1 release of Apache Camel.
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.1
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1616
> Kamelets Tag:
> https://github.com/apache/camel-kamelets/releases/tag/v4.0.1
>
> Please cast your vote.
>
> [ ] +1 Release camel-kamelets 4.0.1
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino

Re: [VOTE] Release Camel K Runtime 2.16.0

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Tue, Jul 4, 2023 at 10:45 AM Pasquale Congiusti
 wrote:
>
> Hello,
>
> This is a vote to release Camel K Runtime 2.16.0. This release mostly
> contains the runtime artifacts required for Camel K version 2 to be
> released independently. As the Camel K Runtime depends mostly on Camel
> Quarkus, we've aligned the version to the same used in Camel Quarkus. From
> now on we expect to release Camel K Runtime beside Camel Quarkus and have
> an available runtime for Camel K as soon as the runtime is released.
>
> Camel K Runtime source files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/2.16.0/
>
> Camel K Runtime staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1587
>
> Camel K Runtime Tag:
> https://github.com/apache/camel-k-runtime/releases/tag/camel-k-runtime-project-2.16.0
>
> It's possible test the staging artifacts by installing the latest Camel K
> CLI (kamel) with the staging repository and run any Integration with the
> new runtime (2.16.0):
>
> kamel install --maven-repository=
> https://repository.apache.org/content/repositories/orgapachecamel-1587
>  --olm=false
> ...
>
> kamel run Test.java -t camel.runtime-version=2.16.0
>
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release Apache Camel K Runtime 2.16.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> I start the vote with my +1.
>
> Thanks and regards,
> Pasquale Congiusti

Re: [VOTE] Release Apache Camel Kamelets 4.0.0-RC1

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Wed, Jul 5, 2023 at 12:23 PM Andrea Cosentino  wrote:
>
> Hello all,
>
> This is a vote for releasing camel-kamelets 4.0.0-RC1
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.0-RC1
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1589
> Kamelets Tag:
> https://github.com/apache/camel-kamelets/releases/tag/v4.0.0-RC1
>
> Please cast your vote.
>
> [ ] +1 Release camel-kamelets 4.0.0-RC1
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino

Re: [VOTE] Release Apache Camel Kamelets 3.20.6

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Mon, Jun 26, 2023 at 11:41 AM Andrea Cosentino  wrote:
>
> Hello all:
>
> This is a vote for releasing camel-kamelets 3.20.6
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/3.20.6
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1580
> Kamelets Tag:
> https://github.com/apache/camel-kamelets/releases/tag/v3.20.6
>
> Please cast your vote.
>
> [ ] +1 Release camel-kamelets 3.20.6
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino

Re: [VOTE] Release Apache Camel K 1.12.1 and Camel K runtime 1.17.1 - second attempt

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Wed, Jun 7, 2023 at 2:56 PM Pasquale Congiusti
 wrote:
>
> Hello,
>
> This is a combined vote to release Apache Camel K 1.12.1 and Camel K
> Runtime1.17.1. The release also contains the Camel K CRD 1.12.1, a Java
> client for Kubernetes Camel K CRDs. The release is based on Camel 3.20.x
> and Camel Quarkus 2.16.x. It contains mostly bug fixes. A first attempt to
> release this version was canceled last week due to a bug found while
> testing the staging version.
>
> Camel K Runtime source files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/1.17.1/
>
> Camel K Runtime staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1565
>
> Camel K Runtime Tag:
> https://github.com/apache/camel-k-runtime/releases/tag/camel-k-runtime-project-1.17.1
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/1.12.1/
>
> Camel K Tag:
> https://github.com/apache/camel-k/releases/tag/v1.12.1
>
> Camel K CRD Java dependency staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1566
>
> Staging container image repository:
> https://hub.docker.com/layers/camelk/camel-k/1.12.1/images/sha256-34b0ea1de619b1790fce1031dcd332f4be1429c045fab30dfe60d589554f842c?context=repo
>
> It's possible to install all staging artifacts with a single command
> (preferably using the kamel CLI you find in Camel K release files):
>
> kamel install --operator-image=camelk/camel-k:1.12.1 --maven-repository=
> https://repository.apache.org/content/repositories/orgapachecamel-1565
>  --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release the binary as Apache Camel K 1.12.1 and Apache Camel K
> Runtime 1.17.1
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> I start the vote with my +1.
>
> Thanks and regards,
> Pasquale Congiusti

Re: [VOTE] Release Apache Camel Kamelets 3.20.4

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Tue, May 16, 2023 at 12:15 PM Andrea Cosentino  wrote:
>
> Hello all:
>
> This is a vote for releasing camel-kamelets 3.20.4
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/3.20.4
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1554
> Kamelets Tag:
> https://github.com/apache/camel/releases/tag/camel-3.20.4
>
> Please cast your vote.
>
> [ ] +1 Release camel-kamelets 3.20.4
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino

Re: [VOTE] Release Apache Camel Kamelets 3.20.3

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Thu, Apr 13, 2023 at 2:41 PM Andrea Cosentino  wrote:
>
> Hello all:
>
> This is a vote for releasing camel-kamelets 3.20.3
>
> This release contains bug fixes and upgrade to latest camel 3.20.3
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/3.20.3
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1545
> Kamelets Tag:
> https://gitbox.apache.org/repos/asf?p=camel-kamelets.git;a=shortlog;h=refs/tags/v3.20.3
>
> Please cast your vote.
>
> [ ] +1 Release camel-kamelets 3.20.3
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino

Re: [VOTE] Release Apache Camel Kamelets 4.0.0-M2

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Thu, Apr 13, 2023 at 2:40 PM Andrea Cosentino  wrote:
>
> Hello all:
>
> This is a vote for releasing camel-kamelets 4.0.0-M2
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.0-M2
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1544
> Kamelets Tag:
> https://gitbox.apache.org/repos/asf?p=camel-kamelets.git;a=shortlog;h=refs/tags/v4.0.0-M2
>
> Please cast your vote.
>
> [ ] +1 Release camel-kamelets 4.0.0-M2
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino

Re: [VOTE] Release Apache Camel K 1.12.0 and Camel K runtime 1.17.0

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Tue, Feb 21, 2023 at 6:37 PM Andrea Cosentino  wrote:
>
> Hello,
>
> This is a combined vote to release Apache Camel K 1.12.0 and Camel K Runtime
> 1.17.0.
>
> This release contains also the Camel K CRD 1.12.0: and experimental module
> containing all the CRDs for this particular release, ready to be used.
>
> The release is the first based on Camel 3.20.x and Camel Quarkus 2.16.x. It
> contains a lot new features and bug fixes.
>
> Runtime source files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/1.17.0/
> Runtime staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1528
> Runtime Tag:
> https://gitbox.apache.org/repos/asf?p=camel-k-runtime.git;a=shortlog;h=refs/tags/camel-k-runtime-project-1.17.0
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/1.12.0/
> Camel K Tag:
> https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/v1.12.0
>
> The Camel K CRD 1.12.0 could be found at:
> https://repository.apache.org/content/repositories/orgapachecamel-1529
>
> Staging container image repository:
> https://hub.docker.com/r/camelk/camel-k/tags
>
> It's possible to install all staging artifacts with a single command:
>
> kamel install --operator-image=camelk/camel-k:1.10.2 --maven-repository=
> https://repository.apache.org/content/repositories/orgapachecamel-1528
>  --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release the binary as Apache Camel K 1.12.0 and
> Apache Camel K Runtime
> 1.17.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino

Re: [VOTE] Release Apache Camel Kamelets 3.20.1.1

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Thu, Jan 26, 2023 at 7:43 AM Andrea Cosentino  wrote:
>
> Hello all:
>
> This is a vote for releasing camel-kamelets 3.20.1.1
>
> The release contains fixes and it's updated to Camel 3.20.1.1
>
> It's mainly related to this issue:
> https://github.com/apache/camel-kamelets/issues/1252
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/3.20.1.1
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1520
> Kamelets Tag:
> https://gitbox.apache.org/repos/asf?p=camel-kamelets.git;a=shortlog;h=refs/tags/v3.20.1.1
>
> Please cast your vote.
>
> [ ] +1 Release camel-kamelets 3.20.1.1
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino

Re: [VOTE] Release Apache Camel K 1.11.1

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Tue, Jan 24, 2023 at 6:50 PM Andrea Cosentino  wrote:
>
> Hello,
>
> This is a combined vote to release Apache Camel K 1.11.1
>
> Camel K 1.11.1 wasn't supposed to be an LTS release, but since OpenJDK
> image for JDK 11 has been discontinued (and suddenly removed from Docker
> hub), we are upgrading the base image from openjdk for JDK 11 to Temurin
> JDK11 (since Openjdk won't release JDK 11 image anymore).
>
> Essentially, a fresh installation of Camel k 1.11.0 won't work OOTB, there
> will need to be some env variables tuning. That's reason behind this
> non-LTS patch release.
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/1.11.1/
> Camel K Tag:
> https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/v1.11.1
>
> Staging container image repository:
> https://hub.docker.com/r/camelk/camel-k/tags
>
> It's possible to install all staging artifacts with a single command:
>
> kamel install --operator-image=camelk/camel-k:1.11.1 --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release the binary as Apache Camel K 1.11.1
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino

Re: [VOTE] Release Apache Camel K 1.10.4 and Camel Kamelets 0.9.4

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Tue, Jan 24, 2023 at 6:33 PM Andrea Cosentino  wrote:
>
> Hello,
>
> This is a combined vote to release Apache Camel K 1.10.4 and Camel Kamelets
> 0.9.4
>
> We are upgrading the base image from openjdk for JDK 11 to Temurin JDK11
> (since Openjdk won't release JDK 11 image anymore), plus some fixes on
> camel-k and camel-kamelets
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/1.10.4/
> Camel K Tag:
> https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/v1.10.4
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/0.9.4
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1519
> Kamelets Tag:
> https://gitbox.apache.org/repos/asf?p=camel-kamelets.git;a=shortlog;h=refs/tags/v0.9.4
>
> Staging container image repository:
> https://hub.docker.com/r/camelk/camel-k/tags
>
> It's possible to install all staging artifacts with a single command:
>
> kamel install --operator-image=camelk/camel-k:1.10.4 --maven-repository=
> https://repository.apache.org/content/repositories/orgapachecamel-1519
>  --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release the binary as Apache Camel K 1.10.4 and
> Apache Camel Kamelets 0.9.4
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino

Re: [Follow/Help] - Apache Camel v4 work in progress

[Jean-Baptiste Onofré]

Hi Claus,

Thanks for that (and I saw you invited me on this channel, thanks :) ).

Regards
JB

On Thu, Jan 12, 2023 at 9:29 AM Claus Ibsen  wrote:
>
> Hi
>
> We have created a room on zulip chat where you can follow and participate
> with the work for Camel v4 that just started this week
>
> https://camel.zulipchat.com/#narrow/stream/364655-camel-v4-work-in-progress
>
> We can use the chat room to coordinate what help is needed and chances for
> you to help or follow what goes on.
>
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2

Re: [VOTE] Release Apache Camel Kamelets 3.20.0

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Wed, Dec 21, 2022 at 2:25 PM Andrea Cosentino  wrote:
>
> Hello all:
>
> This is a vote for releasing camel-kamelets 3.20.0
>
> The release contains fixes and it's updated to Camel 3.20.0.
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/3.20.0
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1510
> Kamelets Tag:
> https://gitbox.apache.org/repos/asf?p=camel-kamelets.git;a=shortlog;h=refs/tags/v3.20.0
>
> Please cast your vote.
>
> [ ] +1 Release camel-kamelets 3.20.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino

Re: [VOTE] Release Apache Camel Kamelets 0.9.3

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Fri, Nov 4, 2022 at 10:33 AM Andrea Cosentino  wrote:
>
> Hello all:
>
> This is a vote for releasing only camel-kamelets 0.9.3.
>
> The release contains fixes and it's updated to Camel 3.18.3.
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/0.9.3/
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1494
> Kamelets Tag:
> https://gitbox.apache.org/repos/asf?p=camel-kamelets.git;a=shortlog;h=refs/tags/v0.9.3
>
> Please cast your vote.
>
> [ ] +1 Release camel-kamelets 0.9.3
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino

Re: Load a route from Blueprint XML

[Jean-Baptiste Onofré]

Hi

you can take a look on the examples in Karaf:

https://github.com/apache/karaf/tree/main/examples/karaf-camel-example

Regards
JB

On Mon, Sep 26, 2022 at 3:51 PM Domke, Alexander
 wrote:
>
> Hello all,
>
> I am trying to load an external route from a blueprint XML file and it is not 
> working. Has anyone done this before and has a tip for me? I am using camel 
> 3.18.2 and Karaf 4.4.1.
>
> My Test Implementation:
>
> package testbundle;
>
> import java.io.File;
> import java.nio.file.Files;
>
> import org.apache.camel.CamelContext;
> import org.apache.camel.Exchange;
> import org.apache.camel.ExtendedCamelContext;
> import org.apache.camel.ProducerTemplate;
> import org.apache.camel.blueprint.BlueprintCamelContext;
> import org.apache.camel.spi.Resource;
> import org.apache.camel.support.DefaultExchange;
> import org.apache.camel.support.ResourceHelper;
> import org.osgi.service.component.annotations.Component;
> import org.osgi.service.component.annotations.Reference;
>
> @Component(
> immediate = true,
> service = TestBundle.class,
> property = {"osgi.command.scope=test", 
> "osgi.command.function=loadRoutes"})
> public class TestBundle {
>
>   public BlueprintCamelContext camelContext;
>
>   @Reference(target = "(camel.context.name=dummyCamelContext)")
>   public void bindCamelContext(CamelContext camelContext) {
> this.camelContext = (BlueprintCamelContext) camelContext;
>   }
>
>   public void unbindCamelContext() {
> camelContext = null;
>   }
>
>   public void loadRoutes() throws Exception {
> loadRoute("C:\\tmp\\before_create.xml", camelContext);
> camelContext.start();
> Exchange exchange = new DefaultExchange(camelContext);
> ProducerTemplate producerTemplate = 
> exchange.getContext().createProducerTemplate();
> Exchange resultExchange = producerTemplate.send("direct:start", exchange);
> System.out.println("resultExchange: " + resultExchange);
>
> if (resultExchange.getException() != null) {
>   throw resultExchange.getException();
> }
>   }
>
>   private void loadRoute(String name, BlueprintCamelContext camelContext) {
> ExtendedCamelContext ecc = camelContext.adapt(ExtendedCamelContext.class);
> try {
>   File file = new File(name);
>   byte[] content = Files.readAllBytes(file.toPath());
>   Resource resource = ResourceHelper.fromBytes(file.getAbsolutePath(), 
> content);
>   ecc.getRoutesLoader().loadRoutes(resource);
>   System.out.println("ecc routes: " + ecc.getRoutes());
>   System.out.println("camelContext routes: " + 
> camelContext.getRouteDefinitions());
>
> } catch (Exception e) {
>   throw new RuntimeException(e);
> }
>   }
> }
>
> My Blueprint with camel context:
>
>
> 
>
> http://www.osgi.org/xmlns/blueprint/v1.0.0; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0; 
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0; 
> xmlns:enc="http://karaf.apache.org/xmlns/jasypt/v1.0.0; xsi:schemaLocation="
>
>http://www.osgi.org/xmlns/blueprint/v1.0.0 
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
>
> http://camel.apache.org/schema/blueprint; 
> id="dummyCamelContext">
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
>
> My Route to load:
>
>
> 
>
> http://www.osgi.org/xmlns/blueprint/v1.0.0;>
>
> http://www.w3.org/2001/XMLSchema-instance; 
> xmlns="http://camel.apache.org/schema/blueprint; xsi:schemaLocation="
>
> http://camel.apache.org/schema/blueprint
>
> http://camel.apache.org/schema/blueprint/camel-blueprint.xsd;>
>
>
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
>
> Error executing command: No consumers available on endpoint: direct://start. 
> Exchange[]
>
> I am at a loss, do you have any idea what I am doing wrong?
>
> Greeting
> Alex
>
> CENIT AG, Industriestrasse 52-54, 70565 Stuttgart, Tel.: +49 711 7825-30, 
> Fax: +49 711 7825-4000, Internet: www.cenit.com
> Geschaeftsstellen (Branch Offices): Berlin, Frankfurt, Hamburg, Hannover, 
> Muenchen, Oelsnitz, Ratingen, Saarbruecken
> Vorstandsmitglieder (Members of the Board): Peter Schneck, Dr. Markus Wesel
> Aufsichtsratsmitglieder (Supervisory Board Members): Rainer Koppitz 
> (Vorsitzender des Aufsichtsrats / Chairman of the Supervisory Board), Prof. 
> Dr. Isabell Welpe, Ricardo Malta
> Bankverbindungen (Bank Accounts):
> Deutsche Bank (BLZ 600 700 70) Kto. 1661 040 IBAN : DE85 6007 0070 0166 1040 
> 00 SWIFT-CODE : DEUTDESS,
> Commerzbank (BLZ 600 400 71) Kto. 532 015 500 IBAN : DE83 6004 0071 0532 0155 
> 00 SWIFT-Code : COBADEFF600,
> Registergericht (Registry court): Amtsgericht Stuttgart
> Handelsregister (Commercial Register): HRB Nr. 19117
> Umsatzsteuer (VAT) ID: DE 147 862 777

Re: camel-spring-security feature

[Jean-Baptiste Onofré]

Hi,

It seems spring-security version used is 4.x, whereas spring-securiy 5.x
feature is available.

I gonna take a look and fix the feature/bundles.

Regards
JB

On Fri, Aug 26, 2022 at 11:16 AM BROUCKE Vincent <
vincent.brou...@contractor.voo.be> wrote:

> Hi,
>
> I would like to install camel-spring-security in my Karaf 4.3.6.
>
>
>
> It seems that feature *camel-spring-security* has disappeared in version
> 3.15.0 :
> https://repo1.maven.org/maven2/org/apache/camel/karaf/apache-camel/3.15.0/apache-camel-3.15.0-features.xml
> .
>
> So I tried to install it without feature :
>
>
>
> feature:install spring-security
>
> install -s mvn:org.apache.camel/camel-spring-security/3.15.0
>
>
>
> But Karaf gives me the following error :
>
>
>
> Error executing command: Error installing bundles:
>
> Unable to start bundle mvn:org.apache.camel/camel-spring-security/3.15.0: 
> org.osgi.framework.BundleException: Unable to resolve 
> org.apache.camel.camel-spring-security [263](R 263.0): missing requirement 
> [org.apache.camel.camel-spring-security [263](R 263.0)] osgi.wiring.package; 
> (&(osgi.wiring.package=org.springframework.security.access)(version>=4.0.0)(!(version>=5.0.0)))
>  Unresolved requirements: [[org.apache.camel.camel-spring-security [263](R 
> 263.0)] osgi.wiring.package; 
> (&(osgi.wiring.package=org.springframework.security.access)(version>=4.0.0)(!(version>=5.0.0)))]
>
>
>
> When I look at the pom, I see that camel-spring-security depends on
> spring-core in version 5.3.15 :
>
>
>
> 
>
>org.springframework
>
>spring-core
>
>5.3.15
>
>compile
>
> 
>
>
>
> But when I look at the Manifest, it requires the following version :
>
>
>
> org.springframework.security.core.context;version="[4,5)"
>
> All 4.x.y version but not 5.x.y version.
>
>
>
> Do you have an idea?
>
>
>
> Thank you for your help
>
>
>
>
>
>
>
> *Vincent Broucke*
>
> *IT BSS*
>
> *BSS Integration Component Owner*
>
> *Consultant externe pour Wavenet*
>
> M +32(0)495 29 69 65
>
> vincent.brou...@contractor.voo.be
>
>
>
>
> Ce message transmis par voie électronique ainsi que toutes ses annexes
> contiennent des informations qui peuvent être confidentielles ou protégées.
> Ces informations sont uniquement destinées à l’usage des personnes ou des
> entités précisées dans les champs ‘A’, ‘Cc’ et ‘Cci’. Si vous n’êtes pas
> l’un de ces destinataires, soyez conscient que toute forme, partielle ou
> complète, de divulgation, copie, distribution ou utilisation de ces
> informations est strictement interdite. Si vous avez reçu ce message par
> erreur, veuillez nous en informer par téléphone ou par message électronique
> et détruire les informations immédiatement. Ce message n’engage que son
> signataire et aucunement son employeur.
>

Re: Component activemq not found

[Jean-Baptiste Onofré]

Hi,

It's normal that the bundle works outside of the feature: it's the
feature resolver who checks the requirements/capabilities of the
bundles/features.

And you didn't get my point: the fact that a ConnectionFactory service
is there or not at runtime doesn't matter. The most important is to
have a bundle/feature that provides the service capability (not the
service itself).

Regards
JB

On Thu, Aug 25, 2022 at 1:45 PM Ephemeris Lappis
 wrote:
>
> Hello.
>
> You've probably not seen my own answers on the post to update it with
> my last tests :
> - the bundle has no problem when installed out of the feature, and I
> think the service manifest itself is not the issue
> - In this manifest, I understand the requirement on the jms service,
> but the existing connection factory should satisfy it
> - why the similar jdbc datasource requirement is processed as expected
> and doesn't lead to a similar issue ?
> - Disabling the serviceRequirements in the feature configuration, the
> feature installer works as expected.
>
> I agree with you, I'm going to post a new message on the Karaf list.
>
> Do you think that in my new post I should mention a Karaf feature
> installer's (its "resolver") issue, since the bundle installer has no
> problem finding the existing services to satisfy requirements ?
>
> Thanks again.
>
> Le jeu. 25 août 2022 à 07:23, Jean-Baptiste Onofré  a 
> écrit :
> >
> > Hi,
> >
> > you have a requirement in your bundle: it's the Import-Service
> > statement. The problem comes from there: it's nothing about the
> > runtime.
> >
> > I would recommend adding configuration to maven-bundle-plugin to not
> > put this requirement in your bundle MANIFEST.
> >
> > I already answered similar questions on the Karaf mailing list several 
> > times.
> >
> > By the way, this kind of question should be discussed on the Karaf
> > mailing list IMHO.
> >
> > Regards
> > JB
> >
> > On Tue, Aug 23, 2022 at 10:35 AM Ephemeris Lappis
> >  wrote:
> > >
> > > Hello again !
> > >
> > > Well, I'm not sure I understand what you mean about "requirements" in my 
> > > bundle. I have no requirement in my manifest. Here the full copy of the 
> > > manifest :
> > >
> > > Manifest-Version: 1.0
> > > Bnd-LastModified: 1661240801094
> > > Build-Jdk-Spec: 1.8
> > > Bundle-Blueprint: OSGI-INF/blueprint/routes.xml
> > > Bundle-Description: Fifi-T26 :: Camel routes
> > > Bundle-ManifestVersion: 2
> > > Bundle-Name: Fifi-T26 :: Camel
> > > Bundle-SymbolicName: my-test-26-karaf-2-routes
> > > Bundle-Version: 0.0.1.SNAPSHOT
> > > Created-By: Apache Maven Bundle Plugin 5.1.8
> > > DynamicImport-Package: groovy.*,org.codehaus.groovy.*
> > > Import-Package: javax.jms,javax.sql,my.test.t26.helper;version="[0.0,1
> > >  )",my.test.t26.uow;version="[0.0,1)",org.osgi.service.blueprint;versi
> > >  on="[1.0.0,2.0.0)"
> > > Import-Service: javax.jms.ConnectionFactory;multiple:=false,my.test.t2
> > >  6.helper.Helper;multiple:=false,my.test.t26.uow.CustomUnitOfWorkFacto
> > >  ry;multiple:=false,javax.sql.DataSource;multiple:=false;filter=(osgi.
> > >  jndi.service.name=jdbc/fifi)
> > > Tool: Bnd-6.3.1.202206071316
> > >
> > > I aim to provide my bundle (and all similar bundles in our projects) as a 
> > > feature, with dependencies that pull all the common features. For that I 
> > > have created a global common feature, and for  every applicative bundle, 
> > > this feature is referenced as a prerequisite. Here are the bundle feature 
> > > and the common one :
> > >
> > > 
> > > http://karaf.apache.org/xmlns/features/v1.6.0; 
> > > name="my-test-26-karaf-2-routes">
> > > 
> > > mvn:my.tests/my-test-26-karaf-x-feature/0.0.1-SNAPSHOT/xml/features
> > > 
> > > Fifi-T26 :: Camel routes - Configuration
> > >  > > finalname="/etc/my_test_26_karaf_2_routes.cfg">mvn:my.tests/my-test-26-karaf-2-routes/0.0.1-SNAPSHOT/cfg/configuration
> > > 
> > > 
> > > Fifi-T26 :: Camel routes
> > >  > > prerequisite="true">my-test-26-karaf-x-feature
> > >  > > prerequisite="true">my-test-26-karaf-2-routes-cfg
> > > 
> > > mvn:my.tests/my-test-26-karaf-2-routes/0.0.1-SNAPSHOT
> > > 
> > > 
> > >
> > > 
> > > http://k

Re: Component activemq not found

[Jean-Baptiste Onofré]

Hi,

you have a requirement in your bundle: it's the Import-Service
statement. The problem comes from there: it's nothing about the
runtime.

I would recommend adding configuration to maven-bundle-plugin to not
put this requirement in your bundle MANIFEST.

I already answered similar questions on the Karaf mailing list several times.

By the way, this kind of question should be discussed on the Karaf
mailing list IMHO.

Regards
JB

On Tue, Aug 23, 2022 at 10:35 AM Ephemeris Lappis
 wrote:
>
> Hello again !
>
> Well, I'm not sure I understand what you mean about "requirements" in my 
> bundle. I have no requirement in my manifest. Here the full copy of the 
> manifest :
>
> Manifest-Version: 1.0
> Bnd-LastModified: 1661240801094
> Build-Jdk-Spec: 1.8
> Bundle-Blueprint: OSGI-INF/blueprint/routes.xml
> Bundle-Description: Fifi-T26 :: Camel routes
> Bundle-ManifestVersion: 2
> Bundle-Name: Fifi-T26 :: Camel
> Bundle-SymbolicName: my-test-26-karaf-2-routes
> Bundle-Version: 0.0.1.SNAPSHOT
> Created-By: Apache Maven Bundle Plugin 5.1.8
> DynamicImport-Package: groovy.*,org.codehaus.groovy.*
> Import-Package: javax.jms,javax.sql,my.test.t26.helper;version="[0.0,1
>  )",my.test.t26.uow;version="[0.0,1)",org.osgi.service.blueprint;versi
>  on="[1.0.0,2.0.0)"
> Import-Service: javax.jms.ConnectionFactory;multiple:=false,my.test.t2
>  6.helper.Helper;multiple:=false,my.test.t26.uow.CustomUnitOfWorkFacto
>  ry;multiple:=false,javax.sql.DataSource;multiple:=false;filter=(osgi.
>  jndi.service.name=jdbc/fifi)
> Tool: Bnd-6.3.1.202206071316
>
> I aim to provide my bundle (and all similar bundles in our projects) as a 
> feature, with dependencies that pull all the common features. For that I have 
> created a global common feature, and for  every applicative bundle, this 
> feature is referenced as a prerequisite. Here are the bundle feature and the 
> common one :
>
> 
> http://karaf.apache.org/xmlns/features/v1.6.0; 
> name="my-test-26-karaf-2-routes">
> 
> mvn:my.tests/my-test-26-karaf-x-feature/0.0.1-SNAPSHOT/xml/features
> 
> Fifi-T26 :: Camel routes - Configuration
>  finalname="/etc/my_test_26_karaf_2_routes.cfg">mvn:my.tests/my-test-26-karaf-2-routes/0.0.1-SNAPSHOT/cfg/configuration
> 
>  version="0.0.1.SNAPSHOT">
> Fifi-T26 :: Camel routes
>  prerequisite="true">my-test-26-karaf-x-feature
>  prerequisite="true">my-test-26-karaf-2-routes-cfg
> mvn:my.tests/my-test-26-karaf-2-routes/0.0.1-SNAPSHOT
> 
> 
>
> 
> http://karaf.apache.org/xmlns/features/v1.6.0; 
> name="my-test-26-karaf">
> 
> mvn:org.apache.camel.karaf/apache-camel/2.25.4/xml/features
> 
> Fifi-T26 :: Feature Definition
> transaction
> camel-spring
> camel-blueprint
> camel-groovy
> camel-csv
> camel-jms
> camel-sql
> 
> mvn:my.tests/my-test-26-karaf-1-service/0.0.1-SNAPSHOT
> mvn:my.tests/my-test-26-karaf-1-api/0.0.1-SNAPSHOT
> 
> 
>
> The error happens when I try to install my bundle as a feature :
> repo-add mvn:my.tests/my-test-26-karaf-2-routes/0.0.1-SNAPSHOT/XML/features
> feature:install my-test-26-karaf-2-routes
>
> All the dependent features and their bundles are installed and started as 
> expected, and when my bundle is deployed, the missing jms service message 
> appears, and the operation fails.
>
> org.apache.felix.resolver.reason.ReasonException: Unable to resolve 
> my-test-26-karaf-2-routes/0.0.1.SNAPSHOT: missing requirement 
> [my-test-26-karaf-2-routes/0.0.1.SNAPSHOT] osgi.service; effective:=active; 
> filter:="(objectClass=javax.jms.ConnectionFactory)"
>
> BUT when I install my bundle manually, it works : no missing service !
>
> bundle:install -s mvn:my.tests/my-test-26-karaf-2-routes/0.0.1-SNAPSHOT
>
> The referenced services (my custom ones, a data source and the jms connection 
> factory) are all found without any problem, and my routes are started, and 
> work as expected, including XA transactions...
>
> What's wrong when the bundle is deployed using its feature ? What is the 
> difference between a raw bundle installing and doing the same using the 
> feature ?
>
> Thanks again for your help.
>
> Regards.
>
>
> Le mar. 23 août 2022 à 07:09, Jean-Baptiste Onofré  a 
> écrit :
>>
>> Hi,
>>
>> That's not a problem of package but of OSGi requirement.
>>
>> You can do:
>> - do not include requirement in your my-test... bundle
>> - provide the capability in your feature (similar to
>> https:

Re: Component activemq not found

[Jean-Baptiste Onofré]

Hi,

That's not a problem of package but of OSGi requirement.

You can do:
- do not include requirement in your my-test... bundle
- provide the capability in your feature (similar to
https://github.com/apache/karaf/blob/main/examples/karaf-jpa-example/karaf-jpa-example-features/src/main/feature/feature.xml#L28)

IMHO, the easiest way is to avoid requirement in your bundle (adding
this to the maven-bundle-plugin configuration).

So, there's no problem with the packages, etc. The problem is simply
the requirement in your bundle (you can see in the MANIFEST of your
bundle, you will see a Require-Capability/Require-Service
instructions).

Regards
JB

See:

On Mon, Aug 22, 2022 at 12:23 PM Ephemeris Lappis
 wrote:
>
> Hello again.
>
> As it seems I have no solution to get an implicit connection factory, I've 
> adapted my POC setting myself a reference. But it seems that it doesn't work 
> because the service that is created by the jms:create command doesn't match 
> some class definition.
>
> In my POC's code I've added a dependency javax.jms-api version 2.0 to match 
> the API version that the bundle that is deployed is providing.
> karaf@root()> exports | grep javax.jms
> javax.jms.doc-files│ 2.0.0   │ 83  │ 
> javax.jms-api
> javax.jms  │ 2.0.0   │ 83  │ 
> javax.jms-api
>
> In my blueprints I've added the service reference, and used it on my JMS 
> routes :
>   id="myJMS"
> interface="javax.jms.ConnectionFactory"
> availability="mandatory" />
>
> 
>
> My bundle's manifest imports the correct package and service :
> Import-Package: javax.jms;version="[2.0,3)",my.test.t26.helper;version
>  ="[0.0,1)",my.test.t26.uow;version="[0.0,1)",org.osgi.service.bluepri
>  nt;version="[1.0.0,2.0.0)"
> Import-Service: javax.jms.ConnectionFactory;multiple:=false,my.test.t2
>  6.helper.Helper;multiple:=false,my.test.t26.uow.CustomUnitOfWorkFacto
>  ry;multiple:=false
>
> The service seems to be present on Karaf :
>
> karaf@root()> jms:connectionfactories
> JMS Connection Factory
> ──
> jms/my_amq
>
> and with service:list :
>
> [javax.jms.ConnectionFactory]
> -
>  name = my_amq
>  osgi.jndi.service.name = jms/my_amq
>  password = secret
>  pax.jms.managed = true
>  service.bundleid = 93
>  service.factoryPid = org.ops4j.connectionfactory
>  service.id = 147
>  service.pid = 
> org.ops4j.connectionfactory.4d276d00-2c50-49b0-93f9-18dc16a107ce
>  service.scope = singleton
>  type = activemq
>  url = tcp://localhost:61616
>  user = application
> Provided by :
>  OPS4J Pax JMS Config (93)
> Used by:
>  System Bundle (0)
>
> [javax.management.MBeanRegistration, 
> org.apache.karaf.features.management.FeaturesServiceMBean, 
> javax.management.NotificationEmitter, 
> javax.management.NotificationBroadcaster, javax.management.DynamicMBean, 
> javax.management.MBeanRegistration]
>
> But when installing my feature, the services do not match, and I have the 
> following error :( !!!
>
> Unable to resolve root: missing requirement [root] osgi.identity; 
> osgi.identity=my-test-26-karaf-2-routes; type=karaf.feature; 
> version="[0.0.1.SNAPSHOT,0.0.1.SNAPSHOT]"; 
> filter:="(&(osgi.identity=my-test-26-karaf-2-routes)(type=karaf.feature)(version>=0.0.1.SNAPSHOT)(version<=0.0.1.SNAPSHOT))"
>  [caused by: Unable to resolve my-test-26-karaf-2-routes/0.0.1.SNAPSHOT: 
> missing requirement [my-test-26-karaf-2-routes/0.0.1.SNAPSHOT] osgi.identity; 
> osgi.identity=my-test-26-karaf-2-routes; type=osgi.bundle; 
> version="[0.0.1.SNAPSHOT,0.0.1.SNAPSHOT]"; resolution:=mandatory [caused by: 
> Unable to resolve my-test-26-karaf-2-routes/0.0.1.SNAPSHOT: missing 
> requirement [my-test-26-karaf-2-routes/0.0.1.SNAPSHOT] osgi.service; 
> effective:=active; filter:="(objectClass=javax.jms.ConnectionFactory)"]]
>
> I thought it may come from the class origin, but only one bundle seems to 
> export it. So I tried to find the issue elsewhere...
>
> Inspecting the ActiveMQ OSGi bundle :
>  52 │ Active   │  80 │ 5.17.1 │ ActiveMQ :: OSGi bundle
>
> I saw that it also gets the class, but doesn't export it :
>
> karaf@root()> bundle:classes 52 | grep javax.jms.ConnectionFactory
> javax/jms/ConnectionFactory.class | exported: false
>
> Can I deduce that the JMS connection factory service may have been created 
> using a bad class from a private package, and this may be the reason why it 
> doesn't match my reference, and perhaps why the camel-jms component doesn't 
> detect it ?
>
&g

Re: Component activemq not found

[Jean-Baptiste Onofré]

Hi,

here's the documentation about camel-activemq:
https://camel.apache.org/components/3.18.x/activemq-component.html

About the ConnectionFactory, you have to define it as reference in
your route. You can find an example here:

https://github.com/jbonofre/camel-amq-redelivery/blob/master/src/main/resources/OSGI-INF/blueprint/route.xml
https://github.com/jbonofre/camel-amq-redelivery/blob/master/src/main/resources/OSGI-INF/blueprint/connectionfactory.xml

Regards
JB

On Sun, Aug 21, 2022 at 10:22 AM Ephemeris Lappis
 wrote:
>
> Hello.
>
> I've never seen any documentation about "camel-activeemq" : what's the
> feature that provides it ?
>
> As I've said before, I've been trying to use camel-jms but surprisingly
> my unique connection factory is not detected, and the component asks for
> an explicit declaration. I thought that one unique connection factory
> should be taken into account... I've created a unique connection factory
> using "jms:create" connecting to an external ActiveMQ, and I've checked
> that the service is present declaring the right interface. Is there a
> special way of declaring or naming the connexion factory to make it
> available for routes with camel-jms endpoints ?
>
> Thanks a lot for your help.
>
> Regards.
>
> Ephemeris Lappis
>
> Le 21/08/2022 à 08:12, Jean-Baptiste Onofré a écrit :
> > That's correct: activemq-camel has been removed.
> >
> > You can now use camel-jms (recommended) or camel-activeemq.
> >
> > You can wrap your own component if needed, but I would rather update
> > to camel-jms (not so hard to do).
> >
> > Regards
> > JB
> >
> > On Fri, Aug 19, 2022 at 12:33 PM Ephemeris Lappis
> >  wrote:
> >> Hello.
> >>
> >> I've been working before on ActiveMQ 5.16.5, but as this version leads to
> >> too many problems on Karaf 4.4.1 (spring compatibility among other issues),
> >> I've decided to switch to ActiveMQ 5.17.1.
> >>
> >> Before, I think the component camel-activemq was provided by the feature
> >> activemq-camel, but with 5.17.1 it doesn't appear anymore in this feature,
> >> if I'm not wrong...
> >>
> >> I've also tried as you suggested to use the jms component in my routes, but
> >> the connection factory I've created to connect to my ActiveMQ server is not
> >> taken into account by the component that requires an explicit connection
> >> factory... Changing all our about 100 camel projects to change from
> >> activemq to jms and declare a connection factory reference seems to be a
> >> very bad choice for us...
> >>
> >> So, from both sides I've issues.
> >>
> >> Any idea to get out of this sad situation  ?
> >>
> >> Thanks a lot !
> >>
> >> Regards.
> >>
> >> PS: Perhaps the documentation on the component should say that it's
> >> available "Since Camel 1.0" but also only with restriction after a given
> >> version...
> >>
> >>
> >> Le ven. 19 août 2022 à 11:51, Claus Ibsen  a écrit :
> >>
> >>> camel-activemq is not out of the box in Apache Camel in Camel v2.
> >>> It comes from Apache ActiveMQ 5.x instead.
> >>>
> >>> However starting from ActiveMQ 5.17 then they dropped their camel-activemq
> >>> JAR and its no longer available.
> >>> Instead use the generic camel-jms instead. Or go back to ActiveMQ 5.16.x
> >>>
> >>> In the Camel website make sure to browse the components list for the Camel
> >>> version you use. The list is different per version.
> >>>
> >>>
> >>> On Fri, Aug 19, 2022 at 11:35 AM Ephemeris Lappis <
> >>> ephemeris.lap...@gmail.com> wrote:
> >>>
> >>>> Hello.
> >>>>
> >>>> I've already asked the question, but probably not clearly...
> >>>>
> >>>> I don't understand why I can't resolve the dependency for :
> >>>> org.apache.camel:camel-activemq:jar:2.25.4
> >>>>
> >>>> I used this component for a long time on old servicemix environments,
> >>>> and I'm trying to port my projects to Karaf using Camel 2.25.4 (and
> >>>> ActiveMQ 5.17.1).
> >>>>
> >>>> The component is still documented on the Camel components list, but I
> >>>> can't find it.
> >>>>
> >>>> Any help ?
> >>>>
> >>>> Thanks in advance.
> >>>>
> >>>> Regards.
> >>>>
> >>>
> >>> --
> >>> Claus Ibsen
> >>> -
> >>> http://davsclaus.com @davsclaus
> >>> Camel in Action 2: https://www.manning.com/ibsen2
> >>>
>
> --
> Cet e-mail a été vérifié par le logiciel antivirus d'Avast.
> www.avast.com

Re: Component activemq not found

[Jean-Baptiste Onofré]

That's correct: activemq-camel has been removed.

You can now use camel-jms (recommended) or camel-activeemq.

You can wrap your own component if needed, but I would rather update
to camel-jms (not so hard to do).

Regards
JB

On Fri, Aug 19, 2022 at 12:33 PM Ephemeris Lappis
 wrote:
>
> Hello.
>
> I've been working before on ActiveMQ 5.16.5, but as this version leads to
> too many problems on Karaf 4.4.1 (spring compatibility among other issues),
> I've decided to switch to ActiveMQ 5.17.1.
>
> Before, I think the component camel-activemq was provided by the feature
> activemq-camel, but with 5.17.1 it doesn't appear anymore in this feature,
> if I'm not wrong...
>
> I've also tried as you suggested to use the jms component in my routes, but
> the connection factory I've created to connect to my ActiveMQ server is not
> taken into account by the component that requires an explicit connection
> factory... Changing all our about 100 camel projects to change from
> activemq to jms and declare a connection factory reference seems to be a
> very bad choice for us...
>
> So, from both sides I've issues.
>
> Any idea to get out of this sad situation  ?
>
> Thanks a lot !
>
> Regards.
>
> PS: Perhaps the documentation on the component should say that it's
> available "Since Camel 1.0" but also only with restriction after a given
> version...
>
>
> Le ven. 19 août 2022 à 11:51, Claus Ibsen  a écrit :
>
> > camel-activemq is not out of the box in Apache Camel in Camel v2.
> > It comes from Apache ActiveMQ 5.x instead.
> >
> > However starting from ActiveMQ 5.17 then they dropped their camel-activemq
> > JAR and its no longer available.
> > Instead use the generic camel-jms instead. Or go back to ActiveMQ 5.16.x
> >
> > In the Camel website make sure to browse the components list for the Camel
> > version you use. The list is different per version.
> >
> >
> > On Fri, Aug 19, 2022 at 11:35 AM Ephemeris Lappis <
> > ephemeris.lap...@gmail.com> wrote:
> >
> > > Hello.
> > >
> > > I've already asked the question, but probably not clearly...
> > >
> > > I don't understand why I can't resolve the dependency for :
> > > org.apache.camel:camel-activemq:jar:2.25.4
> > >
> > > I used this component for a long time on old servicemix environments,
> > > and I'm trying to port my projects to Karaf using Camel 2.25.4 (and
> > > ActiveMQ 5.17.1).
> > >
> > > The component is still documented on the Camel components list, but I
> > > can't find it.
> > >
> > > Any help ?
> > >
> > > Thanks in advance.
> > >
> > > Regards.
> > >
> >
> >
> > --
> > Claus Ibsen
> > -
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >

Re: Get Bundle Version from CamelContext or CamelMessage

[Jean-Baptiste Onofré]

Hi

what do you mean by "your bundle" ? You mean the one containing the route ?

If your bundle just contains the blueprint xml, the most secure way is
to get the bundle list, filter by your name to get the version.

Regards
JB

On Fri, Jul 8, 2022 at 10:45 AM Ephemeris Lappis
 wrote:
>
> Hello again !
>
> I've tested it, but I'm afraid the solution #2 doesn't work as is.
>
> With the following code, the retrieved bundle seems to be the system's
> bundle that creates the exchange, not mine :
>
> // e is the current Exchange
> final Bundle bundle = FrameworkUtil.getBundle(e.getClass());
> return bundle != null ? bundle.getVersion().toString() : "no.version";
>
> The returned version is "2.17.0.redhat-630377", that matches the Fuse
> environment I'm working on, and not my own bundle that manages the
> Camel Context...
>
> What other class could be used to retrieve my bundle ?
>
> Thanks again.
>
> Regards.
>
>
> Le ven. 8 juil. 2022 à 06:49, Jean-Baptiste Onofré  a 
> écrit :
> >
> > Hi,
> >
> > You have two ways to do that:
> > 1. in your blueprint XML, you can inject blueprintBundleContext
> > (implicit bean) in your camel route/processor.
> > 2. you can do FrameworkUtil.getBundle(Exchange.class).getBundleContext()
> >
> > Regards
> > JB
> >
> > On Thu, Jul 7, 2022 at 4:33 PM Ephemeris Lappis
> >  wrote:
> > >
> > > Hello.
> > >
> > > I'd like to know if there's some way to retrieve the bundle version
> > > from either the CamelContext or the CamelMessage objects.
> > >
> > > The code should be executed in a service that is provided from another
> > > bundle. I suppose I could get the BundleContext using the
> > > FrameworkUtil.getBundleContext(someClass), but I don't know how I
> > > could get the given "someClass" that would match the origin Camel
> > > Exchange scope.
> > >
> > > All our Camel contexts are executed from OSGi blueprints packaged as
> > > bundles, and they share the services that need to get the
> > > corresponding bundles versions.
> > >
> > > Any idea ?
> > >
> > > Thanks for your help.
> > >
> > > Regards.

Re: Get Bundle Version from CamelContext or CamelMessage

[Jean-Baptiste Onofré]

Hi,

You have two ways to do that:
1. in your blueprint XML, you can inject blueprintBundleContext
(implicit bean) in your camel route/processor.
2. you can do FrameworkUtil.getBundle(Exchange.class).getBundleContext()

Regards
JB

On Thu, Jul 7, 2022 at 4:33 PM Ephemeris Lappis
 wrote:
>
> Hello.
>
> I'd like to know if there's some way to retrieve the bundle version
> from either the CamelContext or the CamelMessage objects.
>
> The code should be executed in a service that is provided from another
> bundle. I suppose I could get the BundleContext using the
> FrameworkUtil.getBundleContext(someClass), but I don't know how I
> could get the given "someClass" that would match the origin Camel
> Exchange scope.
>
> All our Camel contexts are executed from OSGi blueprints packaged as
> bundles, and they share the services that need to get the
> corresponding bundles versions.
>
> Any idea ?
>
> Thanks for your help.
>
> Regards.

Re: Does camel-extra/firebase component works properly with the latest versions of Camel?

[Jean-Baptiste Onofré]

Hi

I'm not sure about camel-firebase component. I updated camel-wmq to
3.15.x individually and most of the components, but I didn't test all
components.

Regards
JB

On Thu, Jun 9, 2022 at 10:54 AM Vyacheslav Boyko  wrote:
>
> I've found this component on github
>
> https://github.com/camel-extra/camel-extra/tree/master/components/camel-firebase/src/main/java/org/apache/camel/component/firebase
>
> Will it work with Camel 3.15-3.17?
>
> --
> Vyacheslav Boyko
> mailto:mail4...@gmail.com
>

Re: Supporting camel-jira OSGi deployment

[Jean-Baptiste Onofré]

Hi,

This kind of issue would not be an issue with the new approach I'm
preparing for Camel component (creating component uber bundle with
private package): any component will be available as bundle, no need
to create SMX bundles and features.

Anyway, can you please create a Jira about camel-jira OSGi support, I
will fix that.

Thanks,
Regards
JB

On Tue, Jun 7, 2022 at 10:15 AM Xilai Dai  wrote:
>
> Hi there,
>
> Is there a plan supporting camel-jira OSGi deployment on Camel 3.x?
> there is no "camel-jira" karaf feature available e.g in the 
> https://repo1.maven.org/maven2/org/apache/camel/karaf/apache-camel/3.17.0/apache-camel-3.17.0-features.xml
> for sure currently the libraries from com.atlassian.jira are not in the maven 
> central but here http://packages.atlassian.com/maven-external/,
> also the libraries are plain jar, NOT OSGi bundle, (yes using "wrap:" is an 
> option)
> But it would be good to the users if we can make camel-jira OSGi-ready.
>
> Thanks!
> Xilai
>
> As a recipient of an email from Talend, your contact personal data will be on 
> our systems. Please see our privacy notice. 
>
>

Re: producerTemplate gets blocked calling back to previous OSGI bundle

[Jean-Baptiste Onofré]

Hi,

It looks like a change in the Camel routing engine
(DefaultAsyncProcessorAwaitManager).
Let me take a look.

Regards
JB

On Wed, Jun 1, 2022 at 8:21 PM Wing, Lucas A (US)
 wrote:
>
> Hey guys, question about some camel functionality.
>
> Java version: jdk1.8.0_152
> Karaf version: 4.3.2   (I also tested 4.3.7, and it has the same odd behavior)
> Camel version: 3.11.0  (I also tested 3.14.0, and it has the same odd 
> behavior)
>
> In a clean karaf install, I created two different bundles. TestService1 and 
> TestService2.
> TestService1 sends message to TestService2, then TestService2 uses 
> producerTemplate to hit a route on TestService1.
>
> That producerTemplate call appears to get stuck forever on an internal block.
> If I do the same call without using producerTemplate (aka with to() or 
> Recipient List), it works fine.
>
> This did work in karaf 4.1.5 & camel 2.21.0, but appears to have stopped 
> functioning when I tried the versions stated above.
> I guess my question here is, is this a bug? Or is this some sort of 
> functionality to prevent looping routes.
> It only seems to happen if it's two separate bundles (and thus separate camel 
> contexts) so I'd guess this is a bug, but I'm unsure.
>
> If anyone happens to know any way around this possible issue as well, that'd 
> be great to know.
> The only ways I've found is calling producerTemplate in a new thread (not a 
> good solution), or just outright avoiding the use of producerTemplate (even 
> worse solution).
>
>
> Stack trace when I forcibly killed the thread:
> 
>
> Caused by: java.lang.InterruptedException
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:998)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231)
> at 
> org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.await(DefaultAsyncProcessorAwaitManager.java:107)
> at 
> org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:85)
> at 
> org.apache.camel.impl.engine.SharedCamelInternalProcessor.process(SharedCamelInternalProcessor.java:108)
> at 
> org.apache.camel.support.cache.DefaultProducerCache.send(DefaultProducerCache.java:190)
> at 
> org.apache.camel.impl.engine.DefaultProducerTemplate.send(DefaultProducerTemplate.java:176)
> at 
> org.apache.camel.impl.engine.DefaultProducerTemplate.send(DefaultProducerTemplate.java:172)
> at 
> org.apache.camel.impl.engine.DefaultProducerTemplate.send(DefaultProducerTemplate.java:137)
>
> Code:
> 
>
> classes:
>
> public class TestService1 extends RouteBuilder {
>
> private static final Logger logger = 
> LoggerFactory.getLogger(TestService1.class);
>
> public static final String TEST_SERVICE2_ROUTE = 
> "direct-vm://testService2Route";
> public static final String TEST_SERVICE1_RETURN_ROUTE = 
> "direct-vm://testService1ReturnRoute";
>
> @Override
> public void configure() throws Exception {
>
> // On startup, send message to second jar/camel context
> from("timer://startup?repeatCount=1=30s")
> .routeId("startup")
> .to(TEST_SERVICE2_ROUTE);
>
> // Listens for return call from second jar
> from(TEST_SERVICE1_RETURN_ROUTE).routeId("testService1ReturnRoute")
> .bean(this, "returnedMethod");
> }
>
> public void returnedMethod() {
> logger.info("Made it back to the first jar!!!");
> }
>
> }
>
> public class TestService2 extends RouteBuilder {
>
> private static final Logger logger = 
> LoggerFactory.getLogger(TestService2.class);
>
> public static final String TEST_SERVICE2_ROUTE = 
> "direct-vm://testService2Route";
> public static final String TEST_SERVICE1_RETURN_ROUTE = 
> "direct-vm://testService1ReturnRoute";
>
> @Produce(TEST_SERVICE1_RETURN_ROUTE)
> ProducerTemplate executor;
>
> @Override
> public void configure() throws Exception {
>
> //listens for a call from service 1, then hits a route in service 1
> from(TEST_SERVICE2_ROUTE).routeId("testService2Route")
> .bean(this, "hitService1");
>
> }
>
> public void hitService1() {
> logger.info("This call gets locked up");
> executor.sendBody("hello");
> }
>
> }
>
>
> blueprints:
>
>
> 
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0 
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
>
> 
>
> 
> http://camel.apache.org/schema/blueprint;>
> 
> 
>
> 
>
> 
> 

Re: Training request

[Jean-Baptiste Onofré]

Hi,

You can take a look on Camel commercial support to find training provider:

https://camel.apache.org/manual/commercial-camel-offerings.html

Regards
JB

On Tue, May 31, 2022 at 10:48 AM Maciej Kajetan Chrzanowski
 wrote:
>
> Hello,
> I was wondering if there are any training sessions related to camel? I'm
> interested in XML configuration and development.
>
> Kind regards,
> Maciej Kajetan Chrzanowski

Re: Karaf BundleStateService not accessible

[Jean-Baptiste Onofré]

Hi,

Agree, as the API is compatible, we can extend the range. I will do that.

Regards
JB

On Tue, May 17, 2022 at 9:25 PM Martin Lichtin  wrote:
>
> Ah ok, thanks.
> It's because I use Camel version 3.14.x with Karaf 4.2.x and Camel seems
> to have a version range [4.3,5.0) for some Karaf packages.
> I fully understand that Camel is only tested against certain versions of
> Karaf, but still find this restriction somewhat unnecessary as long as
> the service/interface is compatible.
>
> On 16/05/2022 18:18, Jean-Baptiste Onofré wrote:
> > Hi,
> >
> > It's not a big deal, it means that the bundle will stay active even if
> > the context is stopped. Which makes sense as you can have several
> > contexts in the same blueprint container.
> >
> > Anyway, it's worth it to improve this. Can you please share a test
> > case to reproduce it (I tried and it works fine for me) ?
> >
> > Thanks,
> > Regards
> > JB
> >
> > On Mon, May 16, 2022 at 11:56 AM Martin Lichtin
> >  wrote:
> >> I was wondering of any side-effects once this message appears
> >>
> >> BlueprintCamelStateService  137 | 134 -
> >> org.apache.camel.karaf.camel-blueprint - 3.14.3 | Karaf
> >> BundleStateService not accessible. Bundle state won't reflect Camel
> >> context state
> >>
> >> not instantly seeing an issue, just curious about it. It's an info
> >> message, not a warn.
> >>

Re: [VOTE] Release Apache Camel K 1.9.2

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Tue, May 17, 2022 at 11:29 AM Andrea Cosentino  wrote:
>
> Hello all:
>
> This is a combined vote to release Apache Camel K 1.9.2.
>
> This is a patch release fixing an issue with OLM installation and Kamelets
> support.
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/1.9.2/
> Camel K Tag:
> https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/v1.9.2
>
> Staging container image repository:
> https://hub.docker.com/r/camelk/camel-k/tags
>
> It's possible to install all staging artifacts with a single command:
>
> kamel install --operator-image=camelk/camel-k:1.9.2 --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release the binary as Apache Camel K 1.9.2
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino

Re: Karaf BundleStateService not accessible

[Jean-Baptiste Onofré]

Hi,

It's not a big deal, it means that the bundle will stay active even if
the context is stopped. Which makes sense as you can have several
contexts in the same blueprint container.

Anyway, it's worth it to improve this. Can you please share a test
case to reproduce it (I tried and it works fine for me) ?

Thanks,
Regards
JB

On Mon, May 16, 2022 at 11:56 AM Martin Lichtin
 wrote:
>
> I was wondering of any side-effects once this message appears
>
> BlueprintCamelStateService  137 | 134 -
> org.apache.camel.karaf.camel-blueprint - 3.14.3 | Karaf
> BundleStateService not accessible. Bundle state won't reflect Camel
> context state
>
> not instantly seeing an issue, just curious about it. It's an info
> message, not a warn.
>

Re: [VOTE] Release Apache Camel K 1.9.1 and Camel-Kamelets 0.8.1

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Mon, May 9, 2022 at 2:42 PM Andrea Cosentino  wrote:
>
> Hello all:
>
> This is a combined vote to release Apache Camel K 1.9.1 and Kamelets 0.8.1.
>
> This is a patch release fixing an issue with OLM installation and a little
> bug on the AWS Kinesis source Kamelet.
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/0.8.1/
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1436
> Kamelets Tag:
> https://gitbox.apache.org/repos/asf?p=camel-kamelets.git;a=shortlog;h=refs/tags/v0.8.1
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/1.9.1/
> Camel K Tag:
> https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/v1.9.1
>
> Staging container image repository:
> https://hub.docker.com/r/camelk/camel-k/tags
>
> It's possible to install all staging artifacts with a single command:
>
> kamel install --operator-image=camelk/camel-k:1.9.1 --maven-repository=
> https://repository.apache.org/content/repositories/orgapachecamel-1436
>  --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release the binary as Apache Camel K 1.9.1 and Apache Camel Kamelets
> 0.8.1
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino

Re: Camel 3.14.2 features, xml-specs-api loading jaxb-runtime/2.3.1_1

[Jean-Baptiste Onofré]

Hi Martin,

+1, it's already planned for a while:
https://issues.apache.org/jira/browse/CAMEL-16888

Feel free to comment in this Jira.

As you can see on the mailing list (dev), I'm restarting/reviving camel-karaf ;)

Regards
JB

On Tue, May 3, 2022 at 3:23 PM Martin Lichtin  wrote:
>
> Camel 3.14.2 features, xml-specs-api loading jaxb-runtime/2.3.1_1
>
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jaxb-runtime/2.3.1_1
>
> but better would be to load jaxb-runtime version 2.3.2_1 as this version
> contains the "com.sun.istack" classes that 2.3.1_1 is missing.
>
>

Re: [SPAM] Re: Wiring issues with camel-cxf 3.14.2 and CXF 3.4.5 on Karaf 4.3.6

[Jean-Baptiste Onofré]

t; org.apache.cxf.cxf-rt-bindings-soap
> org.apache.cxf.binding.soap.jms.interceptor | 3.4.5   | 307 | 
> org.apache.cxf.cxf-rt-bindings-soap
> org.apache.cxf.binding.soap.model   | 3.4.5   | 307 | 
> org.apache.cxf.cxf-rt-bindings-soap
> org.apache.cxf.binding.soap.saaj| 3.4.5   | 307 | 
> org.apache.cxf.cxf-rt-bindings-soap
> org.apache.cxf.binding.soap.spring  | 3.4.5   | 307 | 
> org.apache.cxf.cxf-rt-bindings-soap
> org.apache.cxf.binding.soap.wsdl.extensions | 3.4.5   | 307 | 
> org.apache.cxf.cxf-rt-bindings-soap
> org.apache.cxf.binding.soap.wsdl11  | 3.4.5   | 307 | 
> org.apache.cxf.cxf-rt-bindings-soap
> org.apache.cxf.binding.soap | 3.4.5   | 307 | 
> org.apache.cxf.cxf-rt-bindings-soap
>
> Do you think this is a bug in Karaf? I checked the OSGi spec, but it is not 
> too clear to me about what this is supposed to wire.
>
> Best regards
> Stephan
>
> -Original Message-
> From: Jean-Baptiste Onofré 
> Sent: Tuesday, 12 April 2022 11:20
> To: users@camel.apache.org; u...@karaf.apache.org
> Subject: [SPAM] Re: Wiring issues with camel-cxf 3.14.2 and CXF 3.4.5 on 
> Karaf 4.3.6
>
> Hi Stephan,
>
> About the version range, [3.4,3.4] includes 3.4.5, so it's normal that it 
> wires. [3.4.4,3.4.4] will exclude 3.4.5, but it will include 3.4.4.x.
>  
> filter:="(&(osgi.wiring.package=org.apache.cxf)(version>=3.4.0)(version<=3.4.0))"
> will actually exclude 3.4.5 (but again, it could include 3.4.0.x).
>
> About CXF import range, I already removed , so, it would make 
> sense to use a "flexible" range, like [3.4,3.5).
>
> Regards
> JB
>
> On Tue, Apr 12, 2022 at 9:39 AM Siano, Stephan 
>  wrote:
> >
> > Hi,
> >
> > I am trying to install camel-cxf 3.14.2 together with CXF 3.4.5 on a custom 
> > distribution of Karaf 4.3.6, but the camel-cxf and camel-cxf-transport 
> > bundles do not wire.
> >
> > The problem is that the CXF packages are imported by the camel-cxf bundles 
> > with an import range of [3.4,3.4] which does not wire with the bundles CXF 
> > 3.4.5 exports (Karaf translates the import range into  
> > filter:="(&(osgi.wiring.package=org.apache.cxf)(version>=3.4.0)(version<=3.4.0))",
> >  which would only match version 3.4.0, but not 3.4.5).
> >
> > The issue was introduced with 
> > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FCAMEL-17137data=04%7C01%7Cstephan.siano%40sap.com%7C608acdcc2479427861ca08da1c65a0a6%7C42f7676cf455423c82f6dc2d99791af7%7C0%7C0%7C637853520169794077%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=Q0EWbpGBQRNO5yJGYe5p4p6FVFAVbKWVs%2Fd5WlTpjk4%3Dreserved=0
> >  and I think this was supposed to restrict the import range to any 3.4 
> > version (but for my gut feeling the filter for that would have to be 
> > “[3.4,3.5)”). Rastislav Papp has added the same issue to the incident, but 
> > I am not sure if that was noted by someone.
> >
> > Do determine what to do as a follow up I have a few questions:
> > To the karaf experts:
> > Is the assumption correct that an import range of [3.4,3.4] should not wire 
> > to a package with version 3.4.5?
> > Is there a setting I didn’t set in my custom distribution that might make 
> > this work?
> >
> > To the camel experts:
> > Wouldn’t it be better to change the CXF import range to [3.4,3.5) or was 
> > that avoided on purpose?
> > With that change the wiring issues are resolved.
> >
> > Best regards
> > Stephan

Re: Wiring issues with camel-cxf 3.14.2 and CXF 3.4.5 on Karaf 4.3.6

[Jean-Baptiste Onofré]

Hi Stephan,

About the version range, [3.4,3.4] includes 3.4.5, so it's normal that
it wires. [3.4.4,3.4.4] will exclude 3.4.5, but it will include
3.4.4.x.
 
filter:="(&(osgi.wiring.package=org.apache.cxf)(version>=3.4.0)(version<=3.4.0))"
will actually exclude 3.4.5 (but again, it could include 3.4.0.x).

About CXF import range, I already removed , so, it would
make sense to use a "flexible" range, like [3.4,3.5).

Regards
JB

On Tue, Apr 12, 2022 at 9:39 AM Siano, Stephan
 wrote:
>
> Hi,
>
> I am trying to install camel-cxf 3.14.2 together with CXF 3.4.5 on a custom 
> distribution of Karaf 4.3.6, but the camel-cxf and camel-cxf-transport 
> bundles do not wire.
>
> The problem is that the CXF packages are imported by the camel-cxf bundles 
> with an import range of [3.4,3.4] which does not wire with the bundles CXF 
> 3.4.5 exports (Karaf translates the import range into  
> filter:="(&(osgi.wiring.package=org.apache.cxf)(version>=3.4.0)(version<=3.4.0))",
>  which would only match version 3.4.0, but not 3.4.5).
>
> The issue was introduced with 
> https://issues.apache.org/jira/browse/CAMEL-17137 and I think this was 
> supposed to restrict the import range to any 3.4 version (but for my gut 
> feeling the filter for that would have to be “[3.4,3.5)”). Rastislav Papp has 
> added the same issue to the incident, but I am not sure if that was noted by 
> someone.
>
> Do determine what to do as a follow up I have a few questions:
> To the karaf experts:
> Is the assumption correct that an import range of [3.4,3.4] should not wire 
> to a package with version 3.4.5?
> Is there a setting I didn’t set in my custom distribution that might make 
> this work?
>
> To the camel experts:
> Wouldn’t it be better to change the CXF import range to [3.4,3.5) or was that 
> avoided on purpose?
> With that change the wiring issues are resolved.
>
> Best regards
> Stephan

Re: EXT:Re: Lost connection to ActiveMQ for Camel routes after configuration changes

[Jean-Baptiste Onofré]

By the way, I have routes with jms endpoints, and afair, it works
fine. So I have to check.

Regards
JB

On Fri, Feb 18, 2022 at 10:36 AM Jean-Baptiste Onofré  wrote:
>
> Thanks for the update.
>
> Let me try to reproduce it with a simple route.
>
> Regards
> JB
>
> On Fri, Feb 18, 2022 at 10:20 AM Zinner, Frank Uwe Alfred
>  wrote:
> >
> > Hi JB,
> >
> > this doesn't work either.
> >
> > This are the relevant log parts from karaf.log and activemq.log for further 
> > investigation:
> >
> >  KARAF LOG
> >
> > 2022-02-17T17:06:55,593 | INFO  | CM Configuration Updater (Update: 
> > pid=org.ops4j.pax.logging) | EventAdminConfigurationNotifier  | 6 - 
> > org.ops4j.pax.logging.pax-logging-api - 1.11.13 | Sending Event Admin 
> > notification (configuration successful) to 
> > org/ops4j/pax/logging/Configuration
> > 2022-02-17T17:08:52,202 | INFO  | pipe-bundle:restart 337 | 
> > BlueprintExtender| 22 - org.apache.aries.blueprint.core - 
> > 1.10.3 | Destroying container for blueprint bundle 
> > de.dfs.services.xxx.xxx.xxx.CatoAftnFilterRouter/3.0.0.SNAPSHOT
> > 2022-02-17T17:08:52,205 | INFO  | pipe-bundle:restart 337 | 
> > AbstractCamelContext | 78 - org.apache.camel.camel-base-engine 
> > - 3.11.5 | Apache Camel 3.11.5 (CATO-FILTER-Context) shutting down 
> > (timeout:5s)
> > 2022-02-17T17:08:53,180 | INFO  | pipe-bundle:restart 337 | 
> > AbstractCamelContext | 78 - org.apache.camel.camel-base-engine 
> > - 3.11.5 | Routes shutdown summary (total:1 stopped:1)
> > 2022-02-17T17:08:53,180 | INFO  | pipe-bundle:restart 337 | 
> > AbstractCamelContext | 78 - org.apache.camel.camel-base-engine 
> > - 3.11.5 | Stopped CATO-FILTER-Router 
> > (opsActivemq://topic:aftn.inbound.records)
> > 2022-02-17T17:08:53,196 | INFO  | pipe-bundle:restart 337 | 
> > AbstractCamelContext | 78 - org.apache.camel.camel-base-engine 
> > - 3.11.5 | Apache Camel 3.11.5 (CATO-FILTER-Context) shutdown in 991ms 
> > (uptime:3m4s)
> > 2022-02-17T17:08:53,201 | INFO  | pipe-bundle:restart 337 | 
> > CommandExtension | 188 - org.apache.karaf.shell.core - 
> > 4.2.15 | Unregistering commands for bundle 
> > de.dfs.services.xxx.xxx.xxx.CatoAftnFilterRouter/3.0.0.SNAPSHOT
> > 2022-02-17T17:08:53,218 | INFO  | pipe-bundle:restart 337 | 
> > AbstractCamelContextFactoryBean  | 91 - org.apache.camel.camel-core-xml - 
> > 3.11.5 | Using custom ShutdownStrategy: 
> > org.apache.camel.impl.engine.DefaultShutdownStrategy@abb6303
> > 2022-02-17T17:08:53,222 | INFO  | pipe-bundle:restart 337 | 
> > BlueprintCamelStateService   | 139 - 
> > org.apache.camel.karaf.camel-blueprint - 3.11.5 | Karaf BundleStateService 
> > not accessible. Bundle state won't reflect Camel context state
> > 2022-02-17T17:08:53,223 | INFO  | pipe-bundle:restart 337 | 
> > BlueprintContainerImpl   | 22 - org.apache.aries.blueprint.core - 
> > 1.10.3 | Blueprint bundle 
> > de.dfs.services.xxx.xxx.xxx.CatoAftnFilterRouter/3.0.0.SNAPSHOT has been 
> > started
> > 2022-02-17T17:08:53,223 | INFO  | Blueprint Event Dispatcher: 1 | 
> > BlueprintCamelContext| 139 - 
> > org.apache.camel.karaf.camel-blueprint - 3.11.5 | Attempting to start 
> > CamelContext: CATO-FILTER-Context
> > 2022-02-17T17:08:53,226 | INFO  | Blueprint Event Dispatcher: 1 | 
> > JmxManagementStrategy| 111 - org.apache.camel.camel-management 
> > - 3.11.5 | JMX is enabled2022-02-17T17:08:53,257 | WARN  | Blueprint Event 
> > Dispatcher: 1 | CoreTypeConverterRegistry| 77 - 
> > org.apache.camel.camel-base - 3.11.5 | Overriding type converter from: 
> > StaticMethodTypeConverter: public static 
> > org.apache.activemq.command.ActiveMQDestination 
> > org.apache.activemq.camel.converter.ActiveMQConverter.toDestination(java.lang.String)
> >  to: org.apache.camel.support.SimpleTypeConverter@6b36dbea
> > 2022-02-17T17:08:53,257 | WARN  | Blueprint Event Dispatcher: 1 | 
> > CoreTypeConverterRegistry| 77 - org.apache.camel.camel-base - 
> > 3.11.5 | Overriding type converter from: InstanceMethodTypeConverter: 
> > public org.apache.activemq.command.ActiveMQMessage 
> > org.apache.activemq.camel.converter.ActiveMQMessageConverter.toMessage(org.apache.camel.Exchange)
> >  throws javax.jms.JMSException to: 
> > org.apache.camel.support.SimpleTypeConverter@1bb26af7
> > 2022-02-17T17:08:53,257 | WARN  | Blueprint Event Dispatcher: 1 | 
> > CoreTypeConverterRegistry| 77 - org.apache.camel.camel-base - 
> > 

Re: EXT:Re: Lost connection to ActiveMQ for Camel routes after configuration changes

[Jean-Baptiste Onofré]

 17:08:53,193 [dle:restart 337] - DEBUG ThreadPoolUtils 
>-  - Forcing shutdown 
> of ExecutorService: java.util.concurrent.ThreadPoolExecutor@780bfee[Running, 
> pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 1]
> 2022-02-17 17:08:53,266 [e[dise] Task-11] - DEBUG TaskRunnerFactory   
>-  - Initialized 
> TaskRunnerFactory[ActiveMQ VMTransport: vm://dise#25] using ExecutorService: 
> java.util.concurrent.ThreadPoolExecutor@5ace9ef1[Running, pool size = 0, 
> active threads = 0, queued tasks = 0, completed tasks = 0]
> 2022-02-17 17:08:53,266 [t Dispatcher: 1] - DEBUG TaskRunnerFactory   
>-  - Initialized 
> TaskRunnerFactory[ActiveMQ VMTransport: vm://dise#24] using ExecutorService: 
> java.util.concurrent.ThreadPoolExecutor@c271484[Running, pool size = 0, 
> active threads = 0, queued tasks = 0, completed tasks = 0]
> 2022-02-17 17:08:53,268 [ vm://dise#25-1] - DEBUG TransportConnection 
>-vm://dise - Setting up new 
> connection id: ID:clienthost-40191-1645113948293-16:1, address: vm://dise#24, 
> info: ConnectionInfo {commandId = 1, responseRequired = true, connectionId = 
> ID:clienthost-40191-1645113948293-16:1, clientId = 
> ID:clienthost-40191-1645113948293-15:1, clientIp = null, userName = 
> y, password = *, brokerPath = null, brokerMasterConnector = 
> false, manageable = true, clientMaster = true, faultTolerant = false, 
> failoverReconnect = false}
> 2022-02-17 17:08:53,268 [ vm://dise#25-1] - DEBUG TransportConnector  
>-vm://dise - Publishing: 
> vm://dise for broker transport URI: vm://dise
> 2022-02-17 17:08:53,268 [ vm://dise#25-1] - DEBUG TransportConnector  
>-vm://dise - Publishing: 
> vm://dise for broker transport URI: vm://dise
> 2022-02-17 17:08:53,268 [ vm://dise#25-1] - DEBUG AbstractRegion  
>-vm://dise - dise adding 
> consumer: ID:clienthost-40191-1645113948293-16:1:-1:1 for destination: 
> ActiveMQ.Advisory.TempQueue,ActiveMQ.Advisory.TempTopic
> 2022-02-17 17:08:53,268 [ vm://dise#25-1] - DEBUG PolicyEntry 
>-vm://dise - Setting the 
> maximumPendingMessages size to: 1000 for consumer: 
> ID:clienthost-40191-1645113948293-16:1:-1:1
> 2022-02-17 17:08:53,270 [ vm://dise#25-1] - DEBUG AbstractRegion  
>-vm://dise - dise adding 
> consumer: ID:clienthost-40191-1645113948293-16:1:1:1 for destination: 
> topic://aftn.inbound.records
> 2022-02-17 17:08:53,270 [ vm://dise#25-1] - DEBUG PolicyEntry 
>-vm://dise - Setting the 
> maximumPendingMessages size to: 1000 for consumer: 
> ID:clienthost-40191-1645113948293-16:1:1:1
> 2022-02-17 17:08:53,271 [ vm://dise#25-1] - DEBUG TransportConnector  
>-vm://dise - Publishing: 
> vm://dise for broker transport URI: vm://dise
> 2022-02-17 17:08:53,271 [ vm://dise#25-1] - DEBUG TransportConnector  
>-vm://dise - Publishing: 
> vm://dise for broker transport URI: vm://dise
> 2022-02-17 17:08:53,271 [ vm://dise#25-1] - DEBUG AbstractRegion  
>-vm://dise - dise adding 
> destination: topic://ActiveMQ.Advisory.Consumer.Topic.aftn.inbound.records
> 2022-02-17 17:08:53,272 [nbound.records]] - DEBUG TaskRunnerFactory   
>-  - Initialized 
> TaskRunnerFactory[ActiveMQ Session Task] using ExecutorService: 
> java.util.concurrent.ThreadPoolExecutor@4a07d63e[Running, pool size = 0, 
> active threads = 0, queued tasks = 0, completed tasks = 0]
> 2022-02-17 17:08:53,595 [eckpoint Worker] - DEBUG MessageDatabase 
>- dise - Checkpoint 
> started.
> 2022-02-17 17:08:53,601 [eckpoint Worker] - DEBUG MessageDatabase 
>- dise - Checkpoint done.
> 2022-02-17 17:08:58,607 [eckpoint Worker] - DEBUG MessageDatabase 
>- dise - Checkpoint 
> started.
> 2022-02-17 17:08:58,607 [eckpoint Worker] - DEBUG MessageDatabase         
>- dise - Checkpoint done.
> 2022-02-17

Re: Lost connection to ActiveMQ for Camel routes after configuration changes

[Jean-Baptiste Onofré]

Hi Frank,

does restarting the blueprint container help (not the bundle, I mean
restarting the route using camel:* commands for instance) ?

Regards
JB

On Thu, Feb 17, 2022 at 3:37 PM Zinner, Frank Uwe Alfred
 wrote:
>
>
> Hi,
> I have a running Kafka 4.2.15 with Camel 3.11.5 and ActiveMQ 5.16.2 with a 
> Camel route to an external ActiveMQ broker.
> When I start my local Karaf, the Camel routes connect both ActiveMQ servers 
> local and external and all works as expected.
> Then when I change the local configuration, Karaf restarts the route but the 
> connection is lost.
> I can see on the external broker side, that the client connection is not 
> present after configuration changed or if I restart the bundle.
>
> The configuration properties got promoted to the camel component e.g. when I 
> change one of the values but I wasn't able to track/debug this down further 
> why the connection is lost.
> Only a restart of the hole Karaf, brings the connection up again.
>
> Any ideas what I can do here or has someone experienced the same as me?
>
> The external ActiveMQ broker has version 5.13.3 the local broker has version 
> 5.16.2.
>
> I connect to an external topic and I use a RouteBuilder to create this route:
>
> from(source).id("Router").description("Filter messages")
> .choice()
> .when(predicate) // predicate is a Camel Predicate
> .to(destination) // this is a topic on a local 
> ActiveMQ broker
> .otherwise()
> .to(destinationFiltered); // also a topic on a local 
> ActiveMQ broker
>
> BrokerURL is tcp://hostname:61616 where hostname is the external 5.13.3 
> ActiveMQ broker.
>
> Nothing special there. The route connects to the remote broker topic, fetches 
> the incoming messages, filters them and sends them to the local broker.
> Again, when I change a parameter in the configuration.cfg file on my local 
> running Karaf or even restart the bundle this causes camel to lose the 
> connection.
>
>
> Frank Uwe Alfred Zinner (extern)
>
> DFS Deutsche Flugsicherung GmbH
> SH/AM
> Am DFS-Campus 7
> 63225 Langen
>
> Mail: 
> frank.uwe.alfred.zin...@externe.dfs.de
>
>
>
> DFS Deutsche Flugsicherung GmbH * Am DFS-Campus * 63225 Langen * Tel.: +49 
> 6103 707-0 * Sitz der Gesellschaft: Langen/Hessen * Zust?ndiges 
> Registergericht: AG Offenbach am Main, HRB 34977 * Vorsitzende des 
> Aufsichtsrats: Antje Geese * Gesch?ftsf?hrer: Arndt Schoenemann (Vors.), Dr. 
> Kerstin B?cker, Dirk Mahns, Friedrich-Wilhelm Menge * 
> www.dfs.de
>
> Sollten Sie nicht der richtige Empf?nger dieser E-Mail sein, l?schen Sie 
> diese bitte.

Re: Camel load resource from classloader broken

[Jean-Baptiste Onofré]

Hi François,

thanks for pointing this.

That's a *huge* regression impacting camel-karaf.
Definitely we have to fix that (I consider this regression as 
blocker/critical).


Can you create a Jira about that, I will fix that ?

Thanks,
Regards
JB

On 03/01/2022 17:35, Francois Papon wrote:

Hi,

It seems like this commit broke the OSGi compatibility by loading 
resources from another classloader:


https://github.com/apache/camel/commit/11bd8012743868712904b449024344bcf8130d2b#diff-8514339d35970f5c1e68df154846a293656b9a482d332b7f4423755ba0d2b0f9 



For example, when upgrading to Camel 3.14.0, we have this error when 
starting a quartz route endpoint:


Caused by: java.lang.RuntimeException: org.quartz.SchedulerException: 
Quartz properties file not found in classpath: org/quartz/quartz.properties


Regards,

Francois

Re: Using Camel, Blueprint (Aries), OSGI and Spring - Place holder issue

[Jean-Baptiste Onofré]

You can use a flat aries blueprint property placeholder backed with 
ConfigAdmin or a file.


Is it what you want ?

Regards
JB

On 16/09/2021 15:46, Andrei Petru Mura wrote:

This definitely isn't a good option as I don't intend to make a difference
by the way in which I reference a variable.
Anyway, property-placeholder doesn't seem to me to be a good option as some
of the variables inside my cfg file are seen, some aren't. For example I
get this:

Error creating bean with name 'ftpClientFactory' defined in URL
[bundle://afa89085-51c4-4cb3-a419-afeccd70a35f_304.0:0/OSGI-INF/blueprint/spring-conf/spring-context.xml]:
Initialization of bean failed; nested exception is
org.springframework.beans.TypeMismatchException: Failed to convert property
value of type 'java.lang.String' to required type 'int' for property
'reconnectRetries'; nested exception is java.lang.NumberFormatException:
For input string: "{{reconnect.retries}}"

In the same spring context, another variable (which is present in the same
configuration file) is well referenced.

Thanks,
Andrei M.

On Thu, Sep 16, 2021 at 4:12 PM John Taylor  wrote:


Hi,

A single property-placeholder is only going to allow one backing
persistent-id.
You can instead create multiple property-placeholders with different ids,
e.g.
   https://stackoverflow.com/questions/50354932/how-to-use-multiple-property-placeholder-in-jboss-fuse-blueprint

Hope that helps.
-John

On Thu, Sep 16, 2021 at 7:58 AM Andrei Petru Mura 
wrote:


Hi all,

I'm trying to migrate my camel routes from an older karaf using Spring-DM
to a newer one using Blueprint. For this, I intend to import my spring

XML

configuration in my blueprint XML file. The camel context is defined in

the

blueprint XML file.
Currently I'm stuck with a placeholder issue. I'm trying to import some
configuration properties from OSGI environment which are stored in a few
files under the ${karaf.home}/etc directory.
I tried many ways according to this documentation page (
https://camel.apache.org/components/2.x/properties-component.html), but
still not getting the functionality which I want.

On short, I want to be able to define in my XML files (blueprint, spring)
some default values for some properties, overriding them with the
configurations found in the configuration files from ${karaf.home}/etc/

and

be able to use them in in both blueprint XML and spring XML files.
Preferable by ${variableName}.

Currently, I did this:

Blueprint XML:

http://www.osgi.org/xmlns/blueprint/v1.0.0;
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
 xmlns:bean="http://www.springframework.org/schema/beans;
 xmlns:camel="http://camel.apache.org/schema/spring;
 xmlns:osgix="http://www.springframework.org/schema/osgi-compendium;
 xmlns:cm="

http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0;

 xsi:schemaLocation="
 http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
 http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd
 http://www.springframework.org/schema/osgi-compendium



http://www.springframework.org/schema/osgi-compendium/spring-osgi-compendium.xsd

">

 
 ...
 

...

 
 
 ... accessing ${configVarHere1}
 
 


http://www.springframework.org/schema/beans;
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
 xmlns:ctx="http://www.springframework.org/schema/context;
 xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
 http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context.xsd;>

 

 
 

...accessing ${configVarHere2}
 


I get this kind of error (because of spring XML):
Failed to convert property value of type 'java.lang.String' to required
type 'int' for property 'configPropName'; nested exception is
java.lang.NumberFormatException: For input string: "${configProprName}"

after I get a few messages like:
The property placeholder processor for ${, } in bundle
bundleName/BundleVersion found an immutable Constructor Argument at
location Bean named beanName->Argument index -1 and value type null->.

This

may prevent properties, beans, or other items referenced by this

component

from being properly processed.

Any idea how I can solve my issue?

Thanks,
Mura Andrei

Re: Migration from 2.x to 3.x

[Jean-Baptiste Onofré]

Hi,

Most of the time, you have one bundle (blueprint, scr, ...) == one camel 
context.
Technically speaking, you can have several camel contexts in the same 
bundle (for instance several blueprint XML, or service).


You can take a look on the Karaf camel examples.

Regards
JB

On 27/08/2021 16:52, Daniel Langevin wrote:

Hi,

In OSGI,
Each blueprint file equal 1 deployment.  So you can put 1 Camel Context by 
deployment file.

Example: File deploy_xxx-0.0.1.xml
===
http://www.osgi.org/xmlns/blueprint/v1.0.0;
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
 xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0;
 xmlns:camel="http://camel.apache.org/schema/blueprint;
 xmlns:osgi="http://www.springframework.org/schema/osgi;
 xsi:schemaLocation="
http://www.osgi.org/xmlns/blueprint/v1.0.0 
http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
http://camel.apache.org/schema/blueprint  
http://camel.apache.org/schema/blueprint/camel-blueprint.xsd
http://camel.apache.org/schema/spring  
http://camel.apache.org/schema/spring/camel-spring-3.11.xsd
http://www.springframework.org/schema/osgi 
http://www.springframework.org/schema/osgi/spring-osgi.xsd;>

http://camel.apache.org/schema/blueprint; 
trace="false">




x
  

GET
text/plain
{{smx.hostname}}
http://{{smx.hostname}}/routes/${header.sysXXX}/${header.localRoutes}/${header.actionsRoutes}
http://dummyhost; />
 1000 


...
...  Another routes





Hope it's help

-Message d'origine-
De : Martin Lichtin 
Envoyé : 27 août 2021 10:37
À : users@camel.apache.org
Objet : Migration from 2.x to 3.x

Hi,

the migration says

"Support for multiple CamelContexts has been removed and only 1 CamelContext per 
deployment is supported."

The term "deployment" seem loose.
My concern here is that in OSGi each bundle has its own CamelContext (e.g. via 
blueprint configuration), how will that work?

- Martin

Re: Feature camel-atlasmap not found

[Jean-Baptiste Onofré]

Hi Gerald,

Thanks, I created the Jira at Camel (with karaf as component) as it's 
not really a Karaf task.


Regards
JB

On 18/08/2021 16:36, Gerald Kallas wrote:

Hi JB,

done. See
https://issues.apache.org/jira/projects/KARAF/issues/KARAF-7241

Best
Gerald


Jean-Baptiste Onofré  hat am 16.08.2021 14:08 geschrieben:

  
Hi,


IMHO, we should create a Jira to add Karaf support for non existing
features.

I can work on it (using component private package or creating required
bundle).

@Gerald, can you please create a Jira about atlasmap ?

Thanks,
Regards
JB

On 13/08/2021 22:24, Gerald Kallas wrote:

Ah ok. Tx.

Is it supported in Camel-K? And if yes, how to hand over the map file to the 
integration?

Best
Gerald


Andrea Cosentino  hat am 13.08.2021 22:12 geschrieben:

   
Hello,


It's not supported in OSGi

Il ven 13 ago 2021, 22:06 Gerald Kallas  ha
scritto:


Dear all.

I did install a vanilla karaf 4.2.9 w/ Camel 3.11.1.

The command

feature:install camel-atlasmap

responds with

Error executing command: No matching features for camel-atlasmap/0

Same with Camel 3.7.5. Did I miss something? The documentation says
camel-atlasmap is available from Camel 3.7.

Best
Gerald

Re: Feature camel-atlasmap not found

[Jean-Baptiste Onofré]

Hi,

IMHO, we should create a Jira to add Karaf support for non existing 
features.


I can work on it (using component private package or creating required 
bundle).


@Gerald, can you please create a Jira about atlasmap ?

Thanks,
Regards
JB

On 13/08/2021 22:24, Gerald Kallas wrote:

Ah ok. Tx.

Is it supported in Camel-K? And if yes, how to hand over the map file to the 
integration?

Best
Gerald


Andrea Cosentino  hat am 13.08.2021 22:12 geschrieben:

  
Hello,


It's not supported in OSGi

Il ven 13 ago 2021, 22:06 Gerald Kallas  ha
scritto:


Dear all.

I did install a vanilla karaf 4.2.9 w/ Camel 3.11.1.

The command

feature:install camel-atlasmap

responds with

Error executing command: No matching features for camel-atlasmap/0

Same with Camel 3.7.5. Did I miss something? The documentation says
camel-atlasmap is available from Camel 3.7.

Best
Gerald

Re: Copy files between 2 windows servers with Camel - Can it be done?

[Jean-Baptiste Onofré]

Hi Ronnie,

Yes it's possible, but the right question is with "which" protocol.

You have different options:
- go via a messaging middleware (like Kafka or ActiveMQ)
- use FTP or kind of shared filesystem (NFS, SMB, ...)

Basically, Camel can read (consume) files from one machine and send to 
ActiveMQ. Then the second machine consumes from ActiveMQ and create the 
file (produce).

That's an option.

Regards
JB

On 02/08/2021 16:08, Ronnie Jorgensen wrote:

Hi all,

I am new to Apache Camel or any MQ software for that matter.

I need some advice. Can Camel copy files between 2 Windows servers?

My scenario is this, I have a cloud HR/Finance system (Workday) and a SWIFT 
Alliance Lite 2 server. Both systems/servers generate txt files the other 
server need. My job is to get the files copied across.

The way I do it now is this:
Workday drop a file on our secure FTP. Then I have a scheduled task that runs 
every 5-10 minutes and copy files over to the other server where the Alliance 
Lite 2 system is running and will pick up the file and process.

The other way is that a file is dropped on the Alliance Lite 2 system from 
SWIFT. My scheduled task that runs also every 5-10 minutes copy files from that 
server and over to the secure FTP server for Workday to pick up.

As you can imagine, I would be very keen to get rid of a scheduled task that 
copies files.

Can Camel help?

Best regards

Ronnie J


E-mail sent for and on behalf of a member of the UPP Group in the UK which 
includes:


UPP Group Holdings Limited, registered number: 5016028
UPP Group Limited, registered number: 6218832
UPP Residential Services Limited, registered number: 5337048
UPP Projects Limited, registered number: 5272122


Registered office: 1st Floor, 12 Arthur Street, London, EC4R 9AB.
Registered in England and Wales


This message (and any associated files) is intended only for the
use of the individual or entity to which it is addressed and may
contain information that is confidential, subject to copyright or
constitutes a trade secret. If you are not the intended recipient
you are hereby notified that any dissemination, copying or
distribution of this message, or files associated with this message,
is strictly prohibited. If you have received this message in error,
please notify us immediately by replying to the message and deleting
it from your computer. Messages sent to and from us may be monitored.


Internet communications cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. Therefore, we do not accept
responsibility for any errors or omissions that are present in this
message, or any attachment, that have arisen as a result of e-mail
transmission. If verification is required, please request a hard-copy
version. Any views or opinions presented are solely those of the author
and do not necessarily represent those of the company.

-

Re: REST API - Basic Authentication?

[Jean-Baptiste Onofré]

Hi,

Not sure I follow (related to your previous message): are you using
servlet registration or camel-jetty ?

On camel-jetty, you can define a security handler.

Using servlet, you can always register a filter.

Regards
JB

On 03/02/2020 18:34, Gerald Kallas wrote:
> Dear community,
> 
> I've following REST API (see below).
> 
> How can I add a Basic Authentication to the REST API in Blueprint DSL? Any 
> hints are highly welcome.
> 
> Best
> - Gerald
> 
> Configuration XML ..
> 
> http://www.osgi.org/xmlns/blueprint/v1.0.0;>
> 
>interface="org.osgi.service.http.HttpService"/>
> 
>class="org.apache.camel.component.servlet.CamelHttpTransportServlet"/>
> 
>class="org.apache.camel.component.servlet.osgi.OsgiServletRegisterer"
> init-method="register"
> destroy-method="unregister">
>   
>   
>   
>   
> 
> 
> 
> .. and REST API ..
> 
> http://www.osgi.org/xmlns/blueprint/v1.0.0;>
> 
>xmlns="http://camel.apache.org/schema/blueprint; streamCache="true">
> 
>contextPath="/api" port="443">
>   
>   
> 
>   
>id="isp.routes.RST001">
>   
>   
>id="isp.routes.RST002">
>   
>   
>   
> 
>   
>   
>   
>   application/json
>   
>   
>   {"text": "Hello World"}
>       
>   
> 
>   
>   
>   
>   application/json
>   
>   
>   {"text": "Bye World"}
>   
>   
> 
>   
> 
> 
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: REST DSL in conjunction with VM component?

[Jean-Baptiste Onofré]

Hi Gerald,

Maybe more direct-vm (sync, whereas VM is like SEDA, so async).

Most of the time, I have the "exposing" REST API in one route that
target a "impl" route using direct-vm (where I have my processor, etc).
I split both in separate bundle. The good thing about that is that I can
change the impl at runtime without impacting the facading API.

Regards
JB

On 03/02/2020 23:33, Gerald Kallas - mailbox.org wrote:
> Dear community,
> 
> I wonder whether the VM component will be a good practice to define 
> functional consumer endpoints for a REST definition in another Camel Context? 
> Background .. I‘d like to decouple an API implementation from the API 
> definition.
> 
> Any hints are welcome.
> 
> Sent by my mobile device
> - Gerald
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: SSL_ERROR_NO_CYPHER_OVERLAP with camel-jetty

[Jean-Baptiste Onofré]

Oh, sorry, the example was in spring, not blueprint.

Let me check in the component how to inject the configuration.

Regards
JB

On 03/02/2020 13:43, Gerald Kallas wrote:
> Tx JB.
> 
> So I tried this (see below) but getting
> 
> Blueprint bundle isp.route.RST.xml/0.0.0 is waiting for namespace handlers 
> [http://camel.apache.org/schema/spring]
> 
> As Claus mentioned earlier one must not mix Blueprint with Spring. Without 
> the Spring namespace the keyword "sslContextParameters" can't be resolved. Is 
> there an example for this pure Blueprint configuration?
> 
> And .. can I define the sslContextParameters once in another Blueprint file?
> 
> Best
> - Gerald
> 
> http://www.osgi.org/xmlns/blueprint/v1.0.0;>
> 
>xmlns="http://camel.apache.org/schema/spring;>
>   
>   
>   TLSv1
>   TLSv1.1
>   TLSv1.2
>   
>   
>password="x"/>
>   
>   
> 
>class="org.apache.camel.component.jetty9.JettyHttpComponent9">
>ref="sslContextParameters" />
>   
> 
>xmlns="http://camel.apache.org/schema/blueprint; streamCache="true">
> 
>scheme="https" port="8443" />
> 
>   
>id="isp.routes.RST001">
>   
>   
>id="isp.routes.RST002">
>   
>   
>   
> 
>   
>   https://0.0.0.0:8443/hello; />
>   
>   application/json
>   
>   
>   {"text": "Hello World"}
>   
>   
> 
>   
>   
>   
>   application/json
>   
>   
>   {"text": "Hello World"}
>   
>   
> 
>   
>   
>   
>   application/json
>   
>   
>   {"text": "Bye World"}
>   
>   
> 
>   
> 
> 
> 
> 
>> Jean-Baptiste Onofré  hat am 3. Februar 2020 13:04 
>> geschrieben:
>>
>>  
>> Hi,
>>
>> By default, camel-jetty create a new connector: it doesn't use the one
>> provided by pax-web. If you want to "plug" into the pax-web jetty
>> connector, you have to use camel-servlet.
>>
>> camel-jetty fully creates a new jetty connector, so the TLS
>> configuration has to be set on camel-jetty.
>>
>> Regards
>> JB
>>
>> On 03/02/2020 11:52, Gerald Kallas wrote:
>>> I tried this setting
>>>
>>> org.ops4j.pax.web.ssl.protocols.included = TLSv1.2
>>>
>>> in
>>>
>>> org.ops4j.pax.web.cfg.
>>>
>>> But this doesn't have any effect.
>>>
>>> Still the same, I'm getting in the log
>>>
>>> 2020-02-03T02:00:35,872 | INFO  | Blueprint Event Dispatcher: 1 | 
>>> JettyHttpComponent9  | 105 - org.apache.camel.camel-jetty - 
>>> 3.0.1 | Connector on port: 8443 is using includeCipherSuites: [] 
>>> excludeCipherSuites: [^.*_(MD5|SHA|SHA1)$, ^TLS_RSA_.*$, ^SSL_.*$, 
>>> ^.*_NULL_.*$, ^.*_anon_.*$] includeProtocols: [] excludeProtocols: [SSL, 
>>> SSLv2, SSLv2Hello, SSLv3]
>>>
>>> Any idea where I can set the includeProtocols value?
>>>
>>> Best
>>> - Gerald
>>>
>>>> Gerald Kallas  hat am 3. Februar 2020 09:46 
>>>> geschrieben:
>>>>
>>>>  
>>>> Tested with cURL
>>>>
>>>> curl --insecure -v https://host:8443/say/hello
>>>> *   Trying 10.0.0.147...
>>>> * TCP_NODELAY set
>>>> * Connected to host (10.0.0.147) port 8443 (#0)
>>>> * ALPN, offering h2
>>>> * ALPN, offering http/1.1
>>>> * successfully set certificate verify locations:
>>>> *   CAfile: /etc/pki/tls/certs/ca-bundle.crt
>>>>   CApath: none
>>>> * TLSv1.3 (OUT), TL

Re: SSL_ERROR_NO_CYPHER_OVERLAP with camel-jetty

[Jean-Baptiste Onofré]

You have a example here:
https://access.redhat.com/documentation/en-us/red_hat_jboss_fuse/6.2/html/security_guide/cameljetty

On 03/02/2020 11:52, Gerald Kallas wrote:
> I tried this setting
> 
> org.ops4j.pax.web.ssl.protocols.included = TLSv1.2
> 
> in
> 
> org.ops4j.pax.web.cfg.
> 
> But this doesn't have any effect.
> 
> Still the same, I'm getting in the log
> 
> 2020-02-03T02:00:35,872 | INFO  | Blueprint Event Dispatcher: 1 | 
> JettyHttpComponent9  | 105 - org.apache.camel.camel-jetty - 3.0.1 
> | Connector on port: 8443 is using includeCipherSuites: [] 
> excludeCipherSuites: [^.*_(MD5|SHA|SHA1)$, ^TLS_RSA_.*$, ^SSL_.*$, 
> ^.*_NULL_.*$, ^.*_anon_.*$] includeProtocols: [] excludeProtocols: [SSL, 
> SSLv2, SSLv2Hello, SSLv3]
> 
> Any idea where I can set the includeProtocols value?
> 
> Best
> - Gerald
> 
>> Gerald Kallas  hat am 3. Februar 2020 09:46 
>> geschrieben:
>>
>>  
>> Tested with cURL
>>
>> curl --insecure -v https://host:8443/say/hello
>> *   Trying 10.0.0.147...
>> * TCP_NODELAY set
>> * Connected to host (10.0.0.147) port 8443 (#0)
>> * ALPN, offering h2
>> * ALPN, offering http/1.1
>> * successfully set certificate verify locations:
>> *   CAfile: /etc/pki/tls/certs/ca-bundle.crt
>>   CApath: none
>> * TLSv1.3 (OUT), TLS handshake, Client hello (1):
>> * TLSv1.3 (IN), TLS alert, handshake failure (552):
>> * error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure
>> * Closing connection 0
>> curl: (35) error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake 
>> failure
>>
>> Seems that the fallback to TLSv1.2 isn't possible
>>
>> So, where is the place to enable TLSv1.2 for camel-jetty?
>>
>> Best
>> - Gerald
>>
>>
>>> Gerald Kallas  hat am 3. Februar 2020 09:00 
>>> geschrieben:
>>>
>>>  
>>> Thanks JB,
>>>
>>> I did not install bouncycastle.
>>>
>>> I did install camel-jetty only as Karaf feature. The underpinning Jetty for 
>>> the Karaf web console is working fine with HTTPS. So far I wonder what I'm 
>>> still missing that camel-jetty could work also with HTTPS.
>>>
>>> Best
>>> - Gerald
>>>
>>>> Jean-Baptiste Onofré  hat am 3. Februar 2020 05:57 
>>>> geschrieben:
>>>>
>>>>  
>>>> Hi,
>>>>
>>>> do you have bouncycastle installed ?
>>>>
>>>> Regards
>>>> JB
>>>>
>>>> On 03/02/2020 00:29, Gerald Kallas wrote:
>>>>> Dear community,
>>>>>
>>>>> I'm going to access some camel-jetty driven consumer endpoints and 
>>>>> getting a
>>>>>
>>>>> SSL_ERROR_NO_CYPHER_OVERLAP
>>>>>
>>>>> error. The web console nevertheless is working well.
>>>>>
>>>>> Any hints are appreciated.
>>>>>
>>>>> That's the jetty.xml section
>>>>>
>>>>>   
>>>>>   https
>>>>>   
>>>>>   
>>>>>   
>>>>>   32768
>>>>>   8192
>>>>>   8192
>>>>>   true
>>>>>   false
>>>>>   512
>>>>>   
>>>>>
>>>>> P.S. I'm running
>>>>>
>>>>> openjdk version "1.8.0_242"
>>>>> OpenJDK Runtime Environment (build 1.8.0_242-b08)
>>>>> OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode)
>>>>> Karaf 4.2.7
>>>>> Camel 3.0.1
>>>>>
>>>>> Best
>>>>> - Gerald
>>>>>
>>>>
>>>> -- 
>>>> Jean-Baptiste Onofré
>>>> jbono...@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: SSL_ERROR_NO_CYPHER_OVERLAP with camel-jetty

[Jean-Baptiste Onofré]

Hi,

By default, camel-jetty create a new connector: it doesn't use the one
provided by pax-web. If you want to "plug" into the pax-web jetty
connector, you have to use camel-servlet.

camel-jetty fully creates a new jetty connector, so the TLS
configuration has to be set on camel-jetty.

Regards
JB

On 03/02/2020 11:52, Gerald Kallas wrote:
> I tried this setting
> 
> org.ops4j.pax.web.ssl.protocols.included = TLSv1.2
> 
> in
> 
> org.ops4j.pax.web.cfg.
> 
> But this doesn't have any effect.
> 
> Still the same, I'm getting in the log
> 
> 2020-02-03T02:00:35,872 | INFO  | Blueprint Event Dispatcher: 1 | 
> JettyHttpComponent9  | 105 - org.apache.camel.camel-jetty - 3.0.1 
> | Connector on port: 8443 is using includeCipherSuites: [] 
> excludeCipherSuites: [^.*_(MD5|SHA|SHA1)$, ^TLS_RSA_.*$, ^SSL_.*$, 
> ^.*_NULL_.*$, ^.*_anon_.*$] includeProtocols: [] excludeProtocols: [SSL, 
> SSLv2, SSLv2Hello, SSLv3]
> 
> Any idea where I can set the includeProtocols value?
> 
> Best
> - Gerald
> 
>> Gerald Kallas  hat am 3. Februar 2020 09:46 
>> geschrieben:
>>
>>  
>> Tested with cURL
>>
>> curl --insecure -v https://host:8443/say/hello
>> *   Trying 10.0.0.147...
>> * TCP_NODELAY set
>> * Connected to host (10.0.0.147) port 8443 (#0)
>> * ALPN, offering h2
>> * ALPN, offering http/1.1
>> * successfully set certificate verify locations:
>> *   CAfile: /etc/pki/tls/certs/ca-bundle.crt
>>   CApath: none
>> * TLSv1.3 (OUT), TLS handshake, Client hello (1):
>> * TLSv1.3 (IN), TLS alert, handshake failure (552):
>> * error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure
>> * Closing connection 0
>> curl: (35) error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake 
>> failure
>>
>> Seems that the fallback to TLSv1.2 isn't possible
>>
>> So, where is the place to enable TLSv1.2 for camel-jetty?
>>
>> Best
>> - Gerald
>>
>>
>>> Gerald Kallas  hat am 3. Februar 2020 09:00 
>>> geschrieben:
>>>
>>>  
>>> Thanks JB,
>>>
>>> I did not install bouncycastle.
>>>
>>> I did install camel-jetty only as Karaf feature. The underpinning Jetty for 
>>> the Karaf web console is working fine with HTTPS. So far I wonder what I'm 
>>> still missing that camel-jetty could work also with HTTPS.
>>>
>>> Best
>>> - Gerald
>>>
>>>> Jean-Baptiste Onofré  hat am 3. Februar 2020 05:57 
>>>> geschrieben:
>>>>
>>>>  
>>>> Hi,
>>>>
>>>> do you have bouncycastle installed ?
>>>>
>>>> Regards
>>>> JB
>>>>
>>>> On 03/02/2020 00:29, Gerald Kallas wrote:
>>>>> Dear community,
>>>>>
>>>>> I'm going to access some camel-jetty driven consumer endpoints and 
>>>>> getting a
>>>>>
>>>>> SSL_ERROR_NO_CYPHER_OVERLAP
>>>>>
>>>>> error. The web console nevertheless is working well.
>>>>>
>>>>> Any hints are appreciated.
>>>>>
>>>>> That's the jetty.xml section
>>>>>
>>>>>   
>>>>>   https
>>>>>   
>>>>>   
>>>>>   
>>>>>   32768
>>>>>   8192
>>>>>   8192
>>>>>   true
>>>>>   false
>>>>>   512
>>>>>   
>>>>>
>>>>> P.S. I'm running
>>>>>
>>>>> openjdk version "1.8.0_242"
>>>>> OpenJDK Runtime Environment (build 1.8.0_242-b08)
>>>>> OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode)
>>>>> Karaf 4.2.7
>>>>> Camel 3.0.1
>>>>>
>>>>> Best
>>>>> - Gerald
>>>>>
>>>>
>>>> -- 
>>>> Jean-Baptiste Onofré
>>>> jbono...@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: SSL_ERROR_NO_CYPHER_OVERLAP with camel-jetty

[Jean-Baptiste Onofré]

Hi,

do you have bouncycastle installed ?

Regards
JB

On 03/02/2020 00:29, Gerald Kallas wrote:
> Dear community,
> 
> I'm going to access some camel-jetty driven consumer endpoints and getting a
> 
> SSL_ERROR_NO_CYPHER_OVERLAP
> 
> error. The web console nevertheless is working well.
> 
> Any hints are appreciated.
> 
> That's the jetty.xml section
> 
>   
>   https
>   
>   
>   
>   32768
>   8192
>   8192
>   true
>   false
>   512
>   
> 
> P.S. I'm running
> 
> openjdk version "1.8.0_242"
> OpenJDK Runtime Environment (build 1.8.0_242-b08)
> OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode)
> Karaf 4.2.7
> Camel 3.0.1
> 
> Best
> - Gerald
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Installing camel-jsonpath fails with NoClassDefFound error

[Jean-Baptiste Onofré]

Hi,

It sounds like a mismatch in ASM version.

I don't think I changed ASM version between Karaf 4.2.7 and 4.2.8. Let
me check. I keep you posted.

Regards
JB

On 02/02/2020 22:23, Gerald Kallas wrote:
> Dear community,
> 
> I'm going to install Camel 3.0.1 within the new Karaf 4.2.8.
> 
> While executing
> 
> feature:install camel-jsonpath
> 
> I'm getting an error
> 
> org.osgi.service.blueprint.container.ComponentDefinitionException: 
> java.lang.NoClassDefFoundError: org/objectweb/asm/commons/AdviceAdapter
> 
> several times. With Karaf 4.2.7 it works.
> 
> Any hints are highly welcome.
> 
> Best
> - Gerald
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Disable karaf remote repositories for Karaf as Camel runtime

[Jean-Baptiste Onofré]

See my comment on the karaf mailing list.

Regards
JB

On 02/02/2020 14:02, Gerald Kallas wrote:
> Dear community,
> 
> I did setup a docker container for Camel/Karaf based on a pre-configured 
> runtime. Finally I want to instantiate the container on a system with no 
> internet access.
> 
> I'm getting a lot of maven connectivity errors at startup depite all features 
> are installed and working.
> 
> Ho can I disable the maven remote access properly?
> 
> Many thanks for any hints.
> 
> Best
> - Gerald
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: java.lang.NoClassDefFoundError: groovy/lang/Script

[Jean-Baptiste Onofré]

Thanks, I will fix that.

Regards
JB

On 29/01/2020 14:35, Alex Soto wrote:
> Thank you JB,
> 
> I created a new ticket:
> 
> https://issues.apache.org/jira/browse/CAMEL-14457 
> <https://issues.apache.org/jira/browse/CAMEL-14457>
> 
> Best regards,
> Alex soto
> 
> 
> 
> 
>> On Jan 29, 2020, at 3:15 AM, Claus Ibsen  wrote:
>>
>> On Wed, Jan 29, 2020 at 6:57 AM Jean-Baptiste Onofré > <mailto:j...@nanthrax.net>> wrote:
>>>
>>> Hi Alex,
>>>
>>> It's what I thought, you are welcome ;)
>>>
>>> Not sure if we consider this as an issue in camel-groovy or in usage.
>>>
>>> Can you reopen CAMEL-4171 and assign to me ? I will improve the current
>>> state.
>>
>> No do not reopen old tickets. Create a new ticket.
>>
>>>
>>> Thanks,
>>> Regards
>>> JB
>>>
>>> On 28/01/2020 19:51, Alex Soto wrote:
>>>> Adding:
>>>>
>>>>  DynamicImport-Package:  groovy.*, org.codehaus.groovy.*
>>>>
>>>> To my bundle seems to work.
>>>> So I suppose this should be added somewhere in a Camel bundle?
>>>>
>>>> Best regards,
>>>> Alex soto
>>>>
>>>>
>>>>
>>>>
>>>>> On Jan 28, 2020, at 1:29 PM, Alex Soto  wrote:
>>>>>
>>>>> This appears to be a regression, as I remember seeing this problem in the 
>>>>> past:
>>>>>
>>>>> https://issues.apache.org/jira/browse/CAMEL-4171 
>>>>> <https://issues.apache.org/jira/browse/CAMEL-4171>
>>>>>
>>>>> I will try your suggestion
>>>>>
>>>>> Best regards,
>>>>> Alex soto
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> On Jan 28, 2020, at 1:24 PM, Jean-Baptiste Onofré >>>>> <mailto:j...@nanthrax.net>> wrote:
>>>>>>
>>>>>> Hi Alex,
>>>>>>
>>>>>> It sounds like a classloader issue (two classloaders, the one of
>>>>>> camel-groovy bundle and the one of your bundle).
>>>>>>
>>>>>> I guess the camel-groovy is actually missing the groovy import.
>>>>>> Can you try to enable dynamic import for camel-groovy and your bundle to
>>>>>> see if it helps ?
>>>>>>
>>>>>> If not, can you please create a Jira and assign to me ?
>>>>>>
>>>>>> Thanks
>>>>>> Regards
>>>>>> JB
>>>>>>
>>>>>> On 28/01/2020 19:17, Alex Soto wrote:
>>>>>>> Hello,
>>>>>>>
>>>>>>> With Camel 3.0.1, I am experiencing this error:
>>>>>>>
>>>>>>> java.lang.RuntimeException: java.lang.NoClassDefFoundError: 
>>>>>>> groovy/lang/Script
>>>>>>>   at 
>>>>>>> org.codehaus.groovy.control.CompilationUnit.convertUncaughtExceptionToCompilationError(CompilationUnit.java:1107)
>>>>>>>   at 
>>>>>>> org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1087)
>>>>>>>   at 
>>>>>>> org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:634)
>>>>>>>   at 
>>>>>>> org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:612)
>>>>>>>   at 
>>>>>>> org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:589)
>>>>>>>   at 
>>>>>>> groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:401)
>>>>>>>   at groovy.lang.GroovyClassLoader.access$300(GroovyClassLoader.java:89)
>>>>>>>   at groovy.lang.GroovyClassLoader$5.provide(GroovyClassLoader.java:341)
>>>>>>>   at groovy.lang.GroovyClassLoader$5.provide(GroovyClassLoader.java:338)
>>>>>>>   at 
>>>>>>> org.codehaus.groovy.runtime.memoize.ConcurrentCommonCache.getAndPut(ConcurrentCommonCache.java:147)
>>>>>>>   at 
>>>>>>> groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:336)
>>>>>>>   at 
>>>>>>> groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:320)
>>>>>>>   at 
>>>>>>> groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:262)
>>>>>>>   at 
>>>>>>> groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:272)
>>>>>>>   at 
>>>>>>> org.apache.camel.language.groovy.GroovyExpression.instantiateScript(GroovyExpression.java:73)
>>>>>>>   …
>>>>>>>
>>>>>>>
>>>>>>> I am running Camel in Karaf OSGi environment with camel-groovy feature 
>>>>>>> installed.  In old Karaf 2.X, I had to install features camel-script, 
>>>>>>> and camel-script-groovy, but they are no longer available.
>>>>>>>
>>>>>>>
>>>>>>> Best regards,
>>>>>>> Alex soto
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Jean-Baptiste Onofré
>>>>>> jbono...@apache.org <mailto:jbono...@apache.org>
>>>>>> http://blog.nanthrax.net
>>>>>> Talend - http://www.talend.com
>>>>>
>>>>
>>>>
>>>
>>> --
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>
>>
>>
>> -- 
>> Claus Ibsen
>> -
>> http://davsclaus.com <http://davsclaus.com/> @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2 
>> <https://www.manning.com/ibsen2>
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Property placeholder causes an error

[Jean-Baptiste Onofré]

Hi Gerald,

You should better use blueprint-cm for the placeholder or directly Camel
property placeholder (which supports blueprint behind the hood).

See
https://camel.apache.org/manual/latest/using-propertyplaceholder.html#UsingPropertyPlaceholder-UsingBlueprintPropertyPlaceholderwithCamelRoutes

Regards
JB

On 28/01/2020 20:47, Gerald Kallas wrote:
> Dear community,
> 
> I'm using Camel 3.0.0 and have following snippet ..
> 
> http://www.osgi.org/xmlns/blueprint/v1.0.0;>
> 
>  class="org.apache.camel.spring.spi.BridgePropertyPlaceholderConfigurer">
> 
> 
> ...
> 
> While deploying I'm getting the following error
> 
> org.osgi.service.blueprint.container.ComponentDefinitionException: Name 
> bridgePropertyPlaceholder is already instanciated as null and cannot be 
> removed.
> 
> With the Sping DSL in Camel 2.x it worked. Any hints are really appreciated.
> 
> Best
> - Gerald
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: java.lang.NoClassDefFoundError: groovy/lang/Script

[Jean-Baptiste Onofré]

Hi Alex,

It's what I thought, you are welcome ;)

Not sure if we consider this as an issue in camel-groovy or in usage.

Can you reopen CAMEL-4171 and assign to me ? I will improve the current
state.

Thanks,
Regards
JB

On 28/01/2020 19:51, Alex Soto wrote:
> Adding:
> 
>   DynamicImport-Package:  groovy.*, org.codehaus.groovy.*
> 
> To my bundle seems to work.
> So I suppose this should be added somewhere in a Camel bundle?
> 
> Best regards,
> Alex soto
> 
> 
> 
> 
>> On Jan 28, 2020, at 1:29 PM, Alex Soto  wrote:
>>
>> This appears to be a regression, as I remember seeing this problem in the 
>> past:
>>
>> https://issues.apache.org/jira/browse/CAMEL-4171 
>> <https://issues.apache.org/jira/browse/CAMEL-4171>
>>
>> I will try your suggestion
>>
>> Best regards,
>> Alex soto
>>
>>
>>
>>
>>> On Jan 28, 2020, at 1:24 PM, Jean-Baptiste Onofré >> <mailto:j...@nanthrax.net>> wrote:
>>>
>>> Hi Alex,
>>>
>>> It sounds like a classloader issue (two classloaders, the one of
>>> camel-groovy bundle and the one of your bundle).
>>>
>>> I guess the camel-groovy is actually missing the groovy import.
>>> Can you try to enable dynamic import for camel-groovy and your bundle to
>>> see if it helps ?
>>>
>>> If not, can you please create a Jira and assign to me ?
>>>
>>> Thanks
>>> Regards
>>> JB
>>>
>>> On 28/01/2020 19:17, Alex Soto wrote:
>>>> Hello,
>>>>
>>>> With Camel 3.0.1, I am experiencing this error:
>>>>
>>>> java.lang.RuntimeException: java.lang.NoClassDefFoundError: 
>>>> groovy/lang/Script
>>>>at 
>>>> org.codehaus.groovy.control.CompilationUnit.convertUncaughtExceptionToCompilationError(CompilationUnit.java:1107)
>>>>at 
>>>> org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1087)
>>>>at 
>>>> org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:634)
>>>>at 
>>>> org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:612)
>>>>at 
>>>> org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:589)
>>>>at 
>>>> groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:401)
>>>>at groovy.lang.GroovyClassLoader.access$300(GroovyClassLoader.java:89)
>>>>at groovy.lang.GroovyClassLoader$5.provide(GroovyClassLoader.java:341)
>>>>at groovy.lang.GroovyClassLoader$5.provide(GroovyClassLoader.java:338)
>>>>at 
>>>> org.codehaus.groovy.runtime.memoize.ConcurrentCommonCache.getAndPut(ConcurrentCommonCache.java:147)
>>>>at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:336)
>>>>at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:320)
>>>>at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:262)
>>>>at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:272)
>>>>at 
>>>> org.apache.camel.language.groovy.GroovyExpression.instantiateScript(GroovyExpression.java:73)
>>>>…
>>>>
>>>>
>>>> I am running Camel in Karaf OSGi environment with camel-groovy feature 
>>>> installed.  In old Karaf 2.X, I had to install features camel-script, and 
>>>> camel-script-groovy, but they are no longer available.
>>>>
>>>>
>>>> Best regards,
>>>> Alex soto
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>> -- 
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org <mailto:jbono...@apache.org>
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>
> 
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: java.lang.NoClassDefFoundError: groovy/lang/Script

[Jean-Baptiste Onofré]

Hi Alex,

It sounds like a classloader issue (two classloaders, the one of
camel-groovy bundle and the one of your bundle).

I guess the camel-groovy is actually missing the groovy import.
Can you try to enable dynamic import for camel-groovy and your bundle to
see if it helps ?

If not, can you please create a Jira and assign to me ?

Thanks
Regards
JB

On 28/01/2020 19:17, Alex Soto wrote:
> Hello,
> 
> With Camel 3.0.1, I am experiencing this error:
> 
> java.lang.RuntimeException: java.lang.NoClassDefFoundError: groovy/lang/Script
>   at 
> org.codehaus.groovy.control.CompilationUnit.convertUncaughtExceptionToCompilationError(CompilationUnit.java:1107)
>   at 
> org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1087)
>   at 
> org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:634)
>   at 
> org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:612)
>   at 
> org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:589)
>   at 
> groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:401)
>   at groovy.lang.GroovyClassLoader.access$300(GroovyClassLoader.java:89)
>   at groovy.lang.GroovyClassLoader$5.provide(GroovyClassLoader.java:341)
>   at groovy.lang.GroovyClassLoader$5.provide(GroovyClassLoader.java:338)
>   at 
> org.codehaus.groovy.runtime.memoize.ConcurrentCommonCache.getAndPut(ConcurrentCommonCache.java:147)
>   at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:336)
>   at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:320)
>   at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:262)
>   at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:272)
>   at 
> org.apache.camel.language.groovy.GroovyExpression.instantiateScript(GroovyExpression.java:73)
>   …
> 
> 
> I am running Camel in Karaf OSGi environment with camel-groovy feature 
> installed.  In old Karaf 2.X, I had to install features camel-script, and 
> camel-script-groovy, but they are no longer available.
> 
> 
> Best regards,
> Alex soto
> 
> 
> 
> 
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Feature camel-activemq causes an runtime error starting the activemq-broker (twice)

[Jean-Baptiste Onofré]

Hi,

you can configure the jmsConnectionFacotry in one blueprint like this:

http://www.osgi.org/xmlns/blueprint/v1.0.0;>











and then you can use this factory in several:

http://www.osgi.org/xmlns/blueprint/v1.0.0;>

   

   
  
   
   ...
  
 



NB: I would use a pooled connection factory.

You can find some example there: http://blog.nanthrax.net/?p=820

Regards
JB

On 13/01/2020 10:55, Gerald Kallas wrote:
> Hi JB,
> 
> finally this works ..
> 
> feature:repo-add hawtio 2.8.0
> feature:repo-add activemq 5.15.11
> feature:repo-add camel 3.0.0
> 
> feature:install webconsole hawtio activemq-broker-noweb camel camel-jms jms 
> pax-jms-config pax-jms-activemq
> 
> with the route
> 
> http://www.osgi.org/xmlns/blueprint/v1.0.0;>
> 
>   
>class="org.apache.activemq.ActiveMQConnectionFactory">
>   
>   
>   
>   
> 
>xmlns="http://camel.apache.org/schema/blueprint; streamCache="true">
> 
>   
>   
>uri="file:E:/tmp/in?include=.*\.xmlmoveFailed=error" />
>   
>   
> 
>   
> 
> 
> 
> The only thing that I'm still missing is to configure the JMS connection 
> factory system wide (with pax?). I don't want to configure this again in each 
> blueprint file.
> 
> ActiveMQ doesn't support JMS 2.0 so this doesn't work
> https://ops4j1.jira.com/wiki/spaces/PAXJMS/pages/331350050/Configuration
> 
> May be any other way around works?
> 
> Best
> - Gerald
> 
> P.S. I saw this sentence within the Camel JMS documentation ..
> 
> USING ACTIVEMQ
> The JMS component reuses Spring 2’s JmsTemplate for sending messages. This is 
> not ideal for use in a non-J2EE container and typically requires some caching 
> in the JMS provider to avoid poor performance.
> 
> If you intend to use Apache ActiveMQ as your message broker, the 
> recommendation is that you do one of the following:
> 
> Use the ActiveMQ component, which is already optimized to use ActiveMQ 
> efficiently
> 
> Use the PoolingConnectionFactory in ActiveMQ.
> 
> 
> Does that really matter an when?
> 
>> Jean-Baptiste Onofré  hat am 13. Januar 2020 um 07:24 
>> geschrieben:
>>
>>
>> Hi Gerald,
>>
>> That's not fully correct. ActiveMQ component gives you some deep
>> configuration but 99% of the features can be achieved with camel-jms.
>>
>> In Karaf, you can just create a ActiveMQ connection factory (using jms
>> feature/commands), and use this connection factory directly with camel-jms.
>>
>> On my blog (blog.nanthrax.net), you have several examples how to use
>> ActiveMQ with Camel JMS.
>>
>> If you need some details/helps, don't hesitate to ping me directly.
>>
>> Regards
>> JB
>>
>> On 13/01/2020 07:01, Gerald Kallas - mailbox.org wrote:
>>> Hi JB,
>>>
>>> tx for the comprehensive reply.
>>>
>>> Within the Camel documentation I read that the activemq component is 
>>> optimized for ActiveMQ. So what does that mean and where are the 
>>> differences between the activemq and the camel-jms component? What does the 
>>> jms component provide?
>>>
>>> Sent by my mobile device
>>> - Gerald Kallas
>>>
>>>> Am 13.01.2020 um 06:00 schrieb Jean-Baptiste Onofré :
>>>>
>>>> Hi Gerald,
>>>>
>>>> Again camel-activemq is not require: you can directy use JMS. It's what
>>>> I'm always doing. The ActiveMQ connection factory in Karaf (most of the
>>>> time I have ActiveMQ broker standalone outside of the Karaf runtime) and
>>>> using jms in my Camel routes.
>>>>
>>>> Anyway, the ActiveMQServiceFactory.updated means you have a refresh or a
>>>> configuration change (in etc/activemq.xml). I'm suspecting hawtio to
>>>> cause this.
>>>>
>>>> If you do feature:install -v you will see the refresh and the cause of
>>>> the refresh. I will reproduce it to identify the root cause.
>>>>
>>>> Regards
>>>> JB
>>>>
>>>>> On 12/01/2020 21:59, Gerald Kallas wrote:
>>>>> Hi JB,
>>>>>
>>>>> feature:install camel
>>>>>
>>>>> instead of
>>>>>
>>>>> feature:install camel-blueprint
>>>>>
>>>>> did it 

Re: Feature camel-activemq causes an runtime error starting the activemq-broker (twice)

[Jean-Baptiste Onofré]

Hi Gerald,

That's not fully correct. ActiveMQ component gives you some deep
configuration but 99% of the features can be achieved with camel-jms.

In Karaf, you can just create a ActiveMQ connection factory (using jms
feature/commands), and use this connection factory directly with camel-jms.

On my blog (blog.nanthrax.net), you have several examples how to use
ActiveMQ with Camel JMS.

If you need some details/helps, don't hesitate to ping me directly.

Regards
JB

On 13/01/2020 07:01, Gerald Kallas - mailbox.org wrote:
> Hi JB,
> 
> tx for the comprehensive reply.
> 
> Within the Camel documentation I read that the activemq component is 
> optimized for ActiveMQ. So what does that mean and where are the differences 
> between the activemq and the camel-jms component? What does the jms component 
> provide?
> 
> Sent by my mobile device
> - Gerald Kallas
> 
>> Am 13.01.2020 um 06:00 schrieb Jean-Baptiste Onofré :
>>
>> Hi Gerald,
>>
>> Again camel-activemq is not require: you can directy use JMS. It's what
>> I'm always doing. The ActiveMQ connection factory in Karaf (most of the
>> time I have ActiveMQ broker standalone outside of the Karaf runtime) and
>> using jms in my Camel routes.
>>
>> Anyway, the ActiveMQServiceFactory.updated means you have a refresh or a
>> configuration change (in etc/activemq.xml). I'm suspecting hawtio to
>> cause this.
>>
>> If you do feature:install -v you will see the refresh and the cause of
>> the refresh. I will reproduce it to identify the root cause.
>>
>> Regards
>> JB
>>
>>> On 12/01/2020 21:59, Gerald Kallas wrote:
>>> Hi JB,
>>>
>>> feature:install camel
>>>
>>> instead of
>>>
>>> feature:install camel-blueprint
>>>
>>> did it finally without the jaxb exception. btw, I'm running Java 8.
>>>
>>> Nevertheless, the feature camel-activemq is required to use the activemq 
>>> component. This I did finally
>>>
>>> karaf@root()> feature:repo-add hawtio 2.8.0
>>> Adding feature url mvn:io.hawt/hawtio-karaf/2.8.0/xml/features
>>> karaf@root()> feature:repo-add activemq 5.15.11
>>> Adding feature url 
>>> mvn:org.apache.activemq/activemq-karaf/5.15.11/xml/features
>>> karaf@root()> feature:repo-add camel 3.0.0
>>> Adding feature url 
>>> mvn:org.apache.camel.karaf/apache-camel/3.0.0/xml/features
>>> karaf@root()> feature:install webconsole hawtio activemq-broker-noweb camel 
>>> camel-activemq
>>>
>>> The error
>>>
>>>at 
>>> org.apache.activemq.osgi.ActiveMQServiceFactory.updated(ActiveMQServiceFactory.java:147)
>>>  ~[!/:5.15.11]
>>>at 
>>> org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.updated(ManagedServiceFactoryTracker.java:159)
>>>  ~[!/:?]
>>>at 
>>> org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.provideConfiguration(ManagedServiceFactoryTracker.java:93)
>>>  [!/:?]
>>>at 
>>> org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceFactoryUpdate.provide(ConfigurationManager.java:1253)
>>>  [!/:?]
>>>at 
>>> org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceFactoryUpdate.run(ConfigurationManager.java:1197)
>>>  [!/:?]
>>>at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:138) 
>>> [!/:?]
>>>at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:105) 
>>> [!/:?]
>>>at java.lang.Thread.run(Unknown Source) [?:1.8.0_201]
>>> Caused by: javax.management.InstanceAlreadyExistsException: 
>>> org.apache.activemq:type=Broker,brokerName=amq-broker
>>>
>>> remains the same. Seems that there is a doubled activemq startup sequence 
>>> somewhere. The system runs but the error message may confuse the operating 
>>> people finally.
>>>
>>> Any further hints at this?
>>>
>>> Thanks
>>> - Gerald
>>>
>>>> Jean-Baptiste Onofré  hat am 12. Januar 2020 um 21:06 
>>>> geschrieben:
>>>>
>>>>
>>>> Hi,
>>>>
>>>> I guess you are using Java 11 ? That's JAXB version (it should work
>>>> without change with JDK8).
>>>>
>>>> Do you use JAXB from JDK or from bundle ?
>>>>
>>>> Regards
>>>> JB
>>>>
>>>> On 12/01/2020 19:06, Gerald Kallas wrote:
>>>>> Tx JB.
>>>>>
>>>&g

Re: Feature camel-activemq causes an runtime error starting the activemq-broker (twice)

[Jean-Baptiste Onofré]

Hi Gerald,

Again camel-activemq is not require: you can directy use JMS. It's what
I'm always doing. The ActiveMQ connection factory in Karaf (most of the
time I have ActiveMQ broker standalone outside of the Karaf runtime) and
using jms in my Camel routes.

Anyway, the ActiveMQServiceFactory.updated means you have a refresh or a
configuration change (in etc/activemq.xml). I'm suspecting hawtio to
cause this.

If you do feature:install -v you will see the refresh and the cause of
the refresh. I will reproduce it to identify the root cause.

Regards
JB

On 12/01/2020 21:59, Gerald Kallas wrote:
> Hi JB,
> 
> feature:install camel
> 
> instead of
> 
> feature:install camel-blueprint
> 
> did it finally without the jaxb exception. btw, I'm running Java 8.
> 
> Nevertheless, the feature camel-activemq is required to use the activemq 
> component. This I did finally
> 
> karaf@root()> feature:repo-add hawtio 2.8.0
> Adding feature url mvn:io.hawt/hawtio-karaf/2.8.0/xml/features
> karaf@root()> feature:repo-add activemq 5.15.11
> Adding feature url mvn:org.apache.activemq/activemq-karaf/5.15.11/xml/features
> karaf@root()> feature:repo-add camel 3.0.0
> Adding feature url mvn:org.apache.camel.karaf/apache-camel/3.0.0/xml/features
> karaf@root()> feature:install webconsole hawtio activemq-broker-noweb camel 
> camel-activemq
> 
> The error
> 
> at 
> org.apache.activemq.osgi.ActiveMQServiceFactory.updated(ActiveMQServiceFactory.java:147)
>  ~[!/:5.15.11]
> at 
> org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.updated(ManagedServiceFactoryTracker.java:159)
>  ~[!/:?]
> at 
> org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.provideConfiguration(ManagedServiceFactoryTracker.java:93)
>  [!/:?]
> at 
> org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceFactoryUpdate.provide(ConfigurationManager.java:1253)
>  [!/:?]
> at 
> org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceFactoryUpdate.run(ConfigurationManager.java:1197)
>  [!/:?]
> at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:138) 
> [!/:?]
> at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:105) 
> [!/:?]
> at java.lang.Thread.run(Unknown Source) [?:1.8.0_201]
> Caused by: javax.management.InstanceAlreadyExistsException: 
> org.apache.activemq:type=Broker,brokerName=amq-broker
> 
> remains the same. Seems that there is a doubled activemq startup sequence 
> somewhere. The system runs but the error message may confuse the operating 
> people finally.
> 
> Any further hints at this?
> 
> Thanks
> - Gerald
> 
>> Jean-Baptiste Onofré  hat am 12. Januar 2020 um 21:06 
>> geschrieben:
>>
>>
>> Hi,
>>
>> I guess you are using Java 11 ? That's JAXB version (it should work
>> without change with JDK8).
>>
>> Do you use JAXB from JDK or from bundle ?
>>
>> Regards
>> JB
>>
>> On 12/01/2020 19:06, Gerald Kallas wrote:
>>> Tx JB.
>>>
>>> I did the same steps as you provided. Afterwards I created a simple route 
>>> as following ..
>>>
>>> http://www.osgi.org/xmlns/blueprint/v1.0.0;>
>>>
>>> 
>>> >> class="org.apache.activemq.ActiveMQConnectionFactory">
>>> 
>>> 
>>> 
>>> 
>>>
>>> >> xmlns="http://camel.apache.org/schema/blueprint; streamCache="true">
>>>
>>> 
>>> 
>>> >> uri="file:E:/tmp/in?include=.*\.xml=error" />
>>> 
>>> 
>>>
>>> 
>>>
>>> 
>>>
>>> While trying to deploy the route I'm getting
>>>
>>> java.lang.NoClassDefFoundError: com/sun/istack/FinalArrayList
>>> at 
>>> com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:249) 
>>> ~[?:?]
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
>>> ~[?:1.8.0_201]
>>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) 
>>> ~[?:1.8.0_201]
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 
>>> ~[?:1.8.0_201]
>>> at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_201]
>>> at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:143) 
>>> ~[?:1.8.0_201]
>>> at javax.xml.bind.ContextFinder.find(ContextFinder.java:31

Re: Feature camel-activemq causes an runtime error starting the activemq-broker (twice)

[Jean-Baptiste Onofré]

Hi,

I guess you are using Java 11 ? That's JAXB version (it should work
without change with JDK8).

Do you use JAXB from JDK or from bundle ?

Regards
JB

On 12/01/2020 19:06, Gerald Kallas wrote:
> Tx JB.
> 
> I did the same steps as you provided. Afterwards I created a simple route as 
> following ..
> 
> http://www.osgi.org/xmlns/blueprint/v1.0.0;>
> 
>   
>class="org.apache.activemq.ActiveMQConnectionFactory">
>   
>   
>   
>   
> 
>xmlns="http://camel.apache.org/schema/blueprint; streamCache="true">
> 
>   
>   
>uri="file:E:/tmp/in?include=.*\.xmlmoveFailed=error" />
>   
>   
> 
>   
> 
> 
> 
> While trying to deploy the route I'm getting
> 
> java.lang.NoClassDefFoundError: com/sun/istack/FinalArrayList
> at 
> com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:249) 
> ~[?:?]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[?:1.8.0_201]
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) 
> ~[?:1.8.0_201]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 
> ~[?:1.8.0_201]
> at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_201]
> at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:143) 
> ~[?:1.8.0_201]
> at javax.xml.bind.ContextFinder.find(ContextFinder.java:310) 
> ~[?:1.8.0_201]
> at javax.xml.bind.JAXBContext.newInstance(Unknown Source) 
> ~[?:1.8.0_201]
> at javax.xml.bind.JAXBContext.newInstance(Unknown Source) 
> ~[?:1.8.0_201]
> at 
> org.apache.camel.impl.DefaultModelJAXBContextFactory.newJAXBContext(DefaultModelJAXBContextFactory.java:38)
>  ~[?:?]
>     at 
> org.apache.camel.blueprint.handler.CamelNamespaceHandler.getJaxbContext(CamelNamespaceHandler.java:678)
>  ~[?:?]
> ...
> 
> Any idea about this?
> 
> Best
> - Gerald
> 
>> Jean-Baptiste Onofré  hat am 12. Januar 2020 um 16:22 
>> geschrieben:
>>
>>
>> Hi,
>>
>> First, you don't need camel-activemq feature, just camel-jms is enough.
>>
>> The activemq-broker-noweb feature seems to work fine, so you have
>> probably a refresh.
>>
>> Here's what I did:
>>
>> feature:install webconsole
>> feature:repo-add activemq 5.15.11
>> feature:repo-add camel 3.0.0
>> feature:install activemq-broker-noweb
>> feature:install camel-blueprint
>> feature:install camel-jms
>> feature:install jms
>>
>> I don't have any issue so far (activemq:bstat is fine with an unique
>> broker).
>>
>> Regards
>> JB
>>
>> On 12/01/2020 15:57, Gerald Kallas wrote:
>>> Dear community,
>>>
>>> I'm going to setup a vanilla karaf / activemq / camel3 installation with 
>>> the following commands
>>>
>>> karaf@root()> feature:repo-add hawtio 2.8.0
>>> Adding feature url mvn:io.hawt/hawtio-karaf/2.8.0/xml/features
>>> karaf@root()> feature:repo-add activemq 5.15.11
>>> Adding feature url 
>>> mvn:org.apache.activemq/activemq-karaf/5.15.11/xml/features
>>> karaf@root()> feature:repo-add camel 3.0.0
>>> Adding feature url 
>>> mvn:org.apache.camel.karaf/apache-camel/3.0.0/xml/features
>>> karaf@root()> feature:install webconsole
>>> karaf@root()> feature:install hawtio
>>> karaf@root()> feature:install activemq-broker-noweb
>>> karaf@root()> feature:install camel
>>> karaf@root()> feature:install camel-jms
>>> karaf@root()> feature:install camel-activemq
>>>
>>> The last command caused an error that comes on board again when restarting 
>>> karaf
>>>
>>> org.osgi.service.cm.ConfigurationException: null : Cannot start the broker
>>> at 
>>> org.apache.activemq.osgi.ActiveMQServiceFactory.updated(ActiveMQServiceFactory.java:147)
>>>  ~[!/:5.15.10]
>>> at 
>>> org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.updated(ManagedServiceFactoryTracker.java:159)
>>>  ~[!/:?]
>>> at 
>>> org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.provideConfiguration(ManagedServiceFactoryTracker.java:93)
>>>  [!/:?]
>>> at 
>>> org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceFactoryUpdate.provide(ConfigurationManager.java:1253)
>>>  [!/:?]
>>> at 
>>> org.apache.felix.cm.impl.Config

Re: Feature camel-activemq causes an runtime error starting the activemq-broker (twice)

[Jean-Baptiste Onofré]

Hi,

First, you don't need camel-activemq feature, just camel-jms is enough.

The activemq-broker-noweb feature seems to work fine, so you have
probably a refresh.

Here's what I did:

feature:install webconsole
feature:repo-add activemq 5.15.11
feature:repo-add camel 3.0.0
feature:install activemq-broker-noweb
feature:install camel-blueprint
feature:install camel-jms
feature:install jms

I don't have any issue so far (activemq:bstat is fine with an unique
broker).

Regards
JB

On 12/01/2020 15:57, Gerald Kallas wrote:
> Dear community,
> 
> I'm going to setup a vanilla karaf / activemq / camel3 installation with the 
> following commands
> 
> karaf@root()> feature:repo-add hawtio 2.8.0
> Adding feature url mvn:io.hawt/hawtio-karaf/2.8.0/xml/features
> karaf@root()> feature:repo-add activemq 5.15.11
> Adding feature url mvn:org.apache.activemq/activemq-karaf/5.15.11/xml/features
> karaf@root()> feature:repo-add camel 3.0.0
> Adding feature url mvn:org.apache.camel.karaf/apache-camel/3.0.0/xml/features
> karaf@root()> feature:install webconsole
> karaf@root()> feature:install hawtio
> karaf@root()> feature:install activemq-broker-noweb
> karaf@root()> feature:install camel
> karaf@root()> feature:install camel-jms
> karaf@root()> feature:install camel-activemq
> 
> The last command caused an error that comes on board again when restarting 
> karaf
> 
> org.osgi.service.cm.ConfigurationException: null : Cannot start the broker
> at 
> org.apache.activemq.osgi.ActiveMQServiceFactory.updated(ActiveMQServiceFactory.java:147)
>  ~[!/:5.15.10]
> at 
> org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.updated(ManagedServiceFactoryTracker.java:159)
>  ~[!/:?]
> at 
> org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.provideConfiguration(ManagedServiceFactoryTracker.java:93)
>  [!/:?]
> at 
> org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceFactoryUpdate.provide(ConfigurationManager.java:1253)
>  [!/:?]
> at 
> org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceFactoryUpdate.run(ConfigurationManager.java:1197)
>  [!/:?]
> at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:138) [!/:?]
> at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:105) [!/:?]
> at java.lang.Thread.run(Unknown Source) [?:1.8.0_201]
> Caused by: javax.management.InstanceAlreadyExistsException: 
> org.apache.activemq:type=Broker,brokerName=amq-broker
> at com.sun.jmx.mbeanserver.Repository.addMBean(Unknown Source) ~[?:1.8.0_201]
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(Unknown
>  Source) ~[?:1.8.0_201]
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(Unknown
>  Source) ~[?:1.8.0_201]
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(Unknown 
> Source) ~[?:1.8.0_201]
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(Unknown 
> Source) ~[?:1.8.0_201]
> at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(Unknown Source) 
> ~[?:1.8.0_201]
> at 
> org.apache.activemq.broker.jmx.ManagementContext.registerMBean(ManagementContext.java:409)
>  ~[!/:5.15.10]
> at 
> org.apache.activemq.broker.jmx.AnnotatedMBean.registerMBean(AnnotatedMBean.java:93)
>  ~[!/:5.15.10]
> at 
> org.apache.activemq.broker.BrokerService.startManagementContext(BrokerService.java:2627)
>  ~[!/:5.15.10]
> at org.apache.activemq.broker.BrokerService.start(BrokerService.java:621) 
> ~[!/:5.15.10]
> at 
> org.apache.activemq.osgi.ActiveMQServiceFactory.updated(ActiveMQServiceFactory.java:141)
>  ~[!/:5.15.10]
> ... 7 more
> 
> I tried some other sequences, always the same. Seems that the broker 
> attempted to start twice.
> 
> Any hints and suggestions are highly appreciated.
> 
> Best
> - Gerald
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: IBM MQ with camel

[Jean-Baptiste Onofré]

Hi,

just a side note: camel-wmq is a camel-extra component allowing you to
directly interact with IBM MQ (without JMS layer):

https://github.com/camel-extra/camel-extra/tree/master/components/camel-wmq/

Regards
JB

On 07/01/2020 15:25, Ravi Kumar wrote:
> Hi All,
> 
> I was trying to read message from IBM MQ queue with the help of the code
> mentioned in below thread
> 
> https://camel.465427.n5.nabble.com/Can-Camel-communicate-over-IBM-MQ-sender-receiver-channels-td4429050.html
> 
> 
> I am able to connect to IBM queue, but whenever am trying to print the
> content of camel body after consuming message, it's printing the message
> content along with all headers contents also in body
> 
>  JMSMessage class: jms_text
>   JMSType:  null
>   JMSDeliveryMode:  2
>   JMSDeliveryDelay: 0
>   JMSDeliveryTime:  0
>   JMSExpiration:0
>   JMSPriority:  0
>   JMSMessageID: ID:414d5120546573744d616e6167657220835e135e233d3c02
>   JMSTimestamp: 1578407050630
>   JMSCorrelationID: null
>   JMSDestination:   null
>   JMSReplyTo:   null
>   JMSRedelivered:   false
> JMSXAppID: \IBM\MQ\bin64\MQExplorer.exe
> JMSXDeliveryCount: 1
> JMSXUserID: Test
> JMS_IBM_Character_Set: UTF-8
> JMS_IBM_Encoding: 546
> JMS_IBM_Format: MQSTR
> JMS_IBM_MsgType: 8
> JMS_IBM_PutApplType: 11
> JMS_IBM_PutDate: 20200107
> JMS_IBM_PutTime: 14241063
> Test Message
> 
> In fact the body content should print only "Test Message"
> 
> Appreciate any input on the same.
> 
> Thanks
> Ravi
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: JMS connection pooling configuration instance wide in Camel 3.0.0 (Karaf 4.2.7)

[Jean-Baptiste Onofré]

Hi Gerald,

Let me prepare/update Karaf 4.3.0-SNAPSHOT examples with Camel 3.0.0.

I keep you posted.

Regards
JB

On 06/01/2020 13:39, Gerald Kallas wrote:
> Thanks JB.
> 
> @Camel folks, any comments on this question from JB?
> 
> Thanks
> - Gerald
> 
>> Jean-Baptiste Onofré  hat am 6. Januar 2020 um 13:15 
>> geschrieben:
>>
>>
>> Hi Gerald,
>>
>> That's probably because camel-jms comes with JMS 2.0 whereas ActiveMQ is
>> still JMS 1.0.
>>
>> You have to check if you have both JMS version in there.
>>
>> Regards
>> JB
>>
>> On 06/01/2020 13:12, Gerald Kallas wrote:
>>> Thanks, JB.
>>>
>>> I tried these commands ..
>>>
>>> karaf@root()> feature:repo-add hawtio 2.8.0
>>> Adding feature url mvn:io.hawt/hawtio-karaf/2.8.0/xml/features
>>> karaf@root()> feature:repo-add activemq 5.15.11
>>> Adding feature url 
>>> mvn:org.apache.activemq/activemq-karaf/5.15.11/xml/features
>>> karaf@root()> feature:repo-add camel 3.0.0
>>> Adding feature url 
>>> mvn:org.apache.camel.karaf/apache-camel/3.0.0/xml/features
>>> karaf@root()> feature:install webconsole hawtio activemq-broker 
>>> pax-jms-config pax-jms-activemq jms
>>> karaf@root()> jms:create -t activemq --url tcp://localhost:61616 -u karaf 
>>> -p karaf activemq
>>> karaf@root()> jms:info -u karaf -p karaf activemq
>>> Property │ Value
>>> ─┼─
>>> product  │ ActiveMQ
>>> version  │ 5.15.11
>>> karaf@root()> feature:install camel
>>> karaf@root()> jms:info -u karaf -p karaf activemq
>>> Property │ Value
>>> ─┼─
>>> product  │ ActiveMQ
>>> version  │ 5.15.11
>>> karaf@root()> feature:install camel-activemq
>>> karaf@root()> jms:info -u karaf -p karaf activemq
>>> Error executing command: No JMS connection factory found for activemq
>>> karaf@root()>
>>>
>>> It seems that after the feature install of camel-activemq the jms 
>>> references are not working anymore. I tried also the same with the pax-jms 
>>> feature, same behaviour.
>>>
>>> Best
>>> - Gerald
>>>
>>>> Jean-Baptiste Onofré  hat am 6. Januar 2020 um 11:05 
>>>> geschrieben:
>>>>
>>>>
>>>> Hi,
>>>>
>>>> Yes, simply use the jms feature: it will use pax-jms that use a managed
>>>> service with configuration backend.
>>>>
>>>> You have a full JMS example in Karaf distribution:
>>>>
>>>> https://github.com/apache/karaf/blob/master/examples/karaf-jms-example/karaf-jms-example-features/src/main/feature/feature.xml#L35
>>>>
>>>> Regards
>>>> JB
>>>>
>>>> On 06/01/2020 09:24, Gerald Kallas wrote:
>>>>> Dear community,
>>>>>
>>>>> I'm currently configuring the JMS connection factory within a blueprint 
>>>>> XML like
>>>>>
>>>>> 
>>>>> >>>> class="org.apache.activemq.ActiveMQConnectionFactory">
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>>
>>>>> Could this be done in one of the config files in etc folder for the whole 
>>>>> instance of Karaf/Camel?
>>>>>
>>>>> Any hints are helpful, tx in advance.
>>>>>
>>>>> Best
>>>>> - Gerald
>>>>>
>>>>
>>>> -- 
>>>> Jean-Baptiste Onofré
>>>> jbono...@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>
>> -- 
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Availability of HTTP4 component in Camel 3.0.0

[Jean-Baptiste Onofré]

Hi,

now http4 is renamed as http.

Regards
JB

On 06/01/2020 09:21, Gerald Kallas wrote:
> Dear community,
> 
> I'm using Camel 3.0.0 ant did find the HTTP component only. When would become 
> the HTTP4 component part of the release?
> 
> Best
> - Gerald
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Spring DSL vs. Blueprint XML inside Camel 3.0.0

[Jean-Baptiste Onofré]

Hi Gerald,

I would rather recommend Java DSL/SCR in Karaf or Blueprint.

Regards
JB

On 06/01/2020 10:36, Gerald Kallas wrote:
> Dear community,
> 
> we're starting the use of Camel 3.0.0 inside Karaf 4.2.7.
> 
> What is the recommended XML DSL? Spring DSL or Blueprint XML?
> 
> When we want to leverage Spring XML, ho to enable the hot deployment inside 
> Karaf?
> 
> Many thanks in advance for comments and hints.
> 
> Best
> - Gerald
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: JMS connection pooling configuration instance wide in Camel 3.0.0 (Karaf 4.2.7)

[Jean-Baptiste Onofré]

Hi,

Yes, simply use the jms feature: it will use pax-jms that use a managed
service with configuration backend.

You have a full JMS example in Karaf distribution:

https://github.com/apache/karaf/blob/master/examples/karaf-jms-example/karaf-jms-example-features/src/main/feature/feature.xml#L35

Regards
JB

On 06/01/2020 09:24, Gerald Kallas wrote:
> Dear community,
> 
> I'm currently configuring the JMS connection factory within a blueprint XML 
> like
> 
> 
>  class="org.apache.activemq.ActiveMQConnectionFactory">
> 
> 
> 
> 
> 
> Could this be done in one of the config files in etc folder for the whole 
> instance of Karaf/Camel?
> 
> Any hints are helpful, tx in advance.
> 
> Best
> - Gerald
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: camel restart

[Jean-Baptiste Onofré]

Hi,

ControlBus is one way, another way is to "listen" the route, but it
depends of the runtime. With Karaf is pretty easy because easy route is
a service, and you can listen a service.

Via JMX, you can also add a listener on a route.

Regards
JB

On 26/11/2019 01:37, Bing Lu wrote:
>  Hi, is there a way to restart the app in case a route was stopped for some 
> reason? thanks    
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: camel-jasypt outside of camelContext in blueprint

[Jean-Baptiste Onofré]

Hi,

I guess you are using Karaf as runtime ? Did you install the jasypt
feature ?

Regards
JB

On 05/11/2019 10:02, Tristan Cartoux wrote:
> Hello,
> 
> I tried to follow this exemple
> <https://camel.465427.n5.nabble.com/camel-jasypt-with-Blueprint-DSL-td5752562.html>
> to use camel-jasypt to instantiate beans in my blueprint xml, but with no
> success. I have no error but jasypt just seems to ignore ENC(...) as i get
> the raw values in my beans.
> 
> Here is what i tried :
> (1)
> 
> *  update-strategy="reload" />*
> 
> 
> 
> 
> 
> 
> 
> 
> 
> *   class="org.apache.camel.component.jasypt.JasyptPropertiesParser">
>  class="org.apache.camel.component.properties.PropertiesComponent">
>   name="propertiesParser" ref="jasypt"/> *
> **
> 
> 
> *value="${keystore.password}" />*
> **
> 
> I finally managed to do this using jasypt "enc" namespace like below :
> (2)
> 
> * update-strategy="reload" />  *
> **
> *  class="org.jasypt.encryption.pbe.StandardPBEStringEncryptor">*
> 
> 
> 
> 
> 
> 
> 
> *   class="org.jasypt.encryption.pbe.config.EnvironmentStringPBEConfig">
>   
>  
>   *
> This solution required me to declare xmlns:enc="
> http://karaf.apache.org/xmlns/jasypt/v1.0.0; in my blueprint, activate
> "jasypt-encryption" karaf feature and adding
> "org.jasypt.encryption.pbe;version=1.9.1_2;" to my bundle Import-Package
> declaration.
> 
> However i would like to know if method (1) can achieve the same thing ? I
> prefer the syntax and i find it easier to use as it does not require adding
> namespace schema or odd maven import declaration.
> Since i have no error, i'm feeling like i just missed a littlle thing to
> make solution (1) work.
> 
> Furthermore, maybe camel doc on jasypt component
> <https://camel.apache.org/components/latest/jasypt.html> should have a note
> for this ?
> Initializing beans with properties is a really common need imo and doc only
> shows exemples for loading props inside of camelContext. If it is not
> possible with camel-jasypt component, maybe it should be specified as well ?
> 
> 
> (Camel version used : 2.22.2)
> 
> Thank you for your help
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Fwd: Camel always sending MQRFH2 headers to target WebsphereMQ queue

[Jean-Baptiste Onofré]

Hi,

It's seems you are using the JMS component. Did you take a look on
camel-wmq one ?

Regards
JB

On 22/10/2019 18:26, Wang Yan wrote:
> Any one has idea how to set IBM Encoding on exchange header ?
> I try to set it on IBMMQFactory but does not work therefore I did setting
> as below not sure it is correct way or not
> 
> 
>  exchange.getIn().setHeader(WMQConstants.WMQ_ENCODING, 1208);
>  exchange.getIn().setHeader(WMQConstants.JMS_IBM_MQMD_ENCODING, 1208);
>  exchange.getIn().setHeader(WMQConstants.JMS_IBM_MQMD_FORMAT,
> MQC.MQFMT_STRING);
>  exchange.getIn().setHeader(WMQConstants.JMS_IBM_FORMAT, MQC.MQFMT_STRING);
> 
> 
> -- Forwarded message -
> From: W.Y [via Camel] 
> Date: Sat, Oct 19, 2019 at 6:55 AM
> Subject: Fwd: Camel always sending MQRFH2 headers to target WebsphereMQ
> queue
> To: W.Y 
> 
> 
> @Willem.Jiang [via Camel] <[hidden email]
> <http:///user/SendEmail.jtp?type=node=5845743=0>>
> 
> Thanks for the reply, I am using openJRE11
> 
> BTW , is the cast exception due to java version? My assumption is it should
> be related to IBM libs
> according to code, during runtime, the session is expected
> as MQQueueSession instance but it is  MQSession instance instead .
> 
> MQQueueSession wmqSession = (MQQueueSession) session
> 
> -- Forwarded message -
> From: Willem.Jiang [via Camel] <[hidden email]
> <http:///user/SendEmail.jtp?type=node=5845743=1>>
> Date: Sat, Oct 19, 2019 at 3:31 AM
> Subject: Re: Camel always sending MQRFH2 headers to target WebsphereMQ
> queue
> To: W.Y <[hidden email]
> <http:///user/SendEmail.jtp?type=node=5845743=2>>
> 
> 
> Which version of JDK are you using?
> From the stack trace, it looks like you cannot cast the
> com.ibm.mq.jms.MQSession to com.ibm.mq.jms.MQQueueSession.
> I think you need to check the client code for more information.
> 
> Willem Jiang
> 
> Twitter: willemjiang
> Weibo: 姜宁willem
> 
> On Fri, Oct 18, 2019 at 11:51 PM Wang Yan <[hidden email]
> <http:///user/SendEmail.jtp?type=node=5845741=0>> wrote:
> 
>>
>> I have problem , camel is always sending MQRFH2 headers to target
>> WebsphereMQ queue
>>
>> I used below code try to solve the problem but i got
>> Setup of JMS message listener invoker failed for destination
>>
>> - trying to recover. Cause: class com.ibm.mq.jms.MQSession cannot be cast
>> to class com.ibm.mq.jms.MQQueueSession (com.ibm.mq.jms.MQSession and
>> com.ibm.mq.jms.MQQueueSession are in unnamed module of loader
>> org.springframework.boot.loader.LaunchedURLClassLoader @5056dfcb)
>>
>>
>> IBM library i used is
>>  // https://mvnrepository.com/artifact/com.ibm.mq/com.ibm.mq.allclient
>> implementation 'com.ibm.mq:com.ibm.mq.allclient:9.1.1.0'
>>
>> What could be the problem? Did I used to wrong libs? any suggestions or
>> feedback are more than welcome!
>>
>>
>> JmsComponent wmq = new JmsComponent(connectionFactory);
>> wmq.setDestinationResolver(new DestinationResolver() { public Destination
>> resolveDestinationName(Session session, String destinationName, boolean
>> pubSubDomain) throws JMSException { MQQueueSession wmqSession =
>> (MQQueueSession) session; return wmqSession.createQueue("queue:///" +
>> destinationName + "?targetClient=1"); } });
> 
> 
> --
> If you reply to this email, your message will be added to the discussion
> below:
> https://camel.465427.n5.nabble.com/Camel-always-sending-MQRFH2-headers-to-target-WebsphereMQ-queue-tp5845716p5845741.html
> To unsubscribe from Camel always sending MQRFH2 headers to target
> WebsphereMQ queue, click here
> <
> https://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code=5845716=d3lhbmJveEBnbWFpbC5jb218NTg0NTcxNnwxMTU1MzAzODM=>
> 
> .
> NAML
> <
> https://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer=instant_html%21nabble%3Aemail.naml=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
> 
> 
> 
> --
> If you reply to this email, your message will be added to the discussion
> below:
> https://camel.465427.n5.nabble.com/Camel-always-sending-MQRFH2-headers-to-target-WebsphereMQ-queue-tp5845716p5845743.html
> To unsubscribe from Camel always sending MQRFH2 headers to target
> WebsphereMQ queue, click here
> <https://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubsc

Re: batch http requests

[Jean-Baptiste Onofré]

Let me check if I have something close to what you want to do.

Regards
JB

On 18/10/2019 09:24, arshad dar wrote:
> thank you for the reply. can you please provide a small example with
> aggregators ?
> 
> On Fri, Oct 18, 2019 at 12:06 PM Jean-Baptiste Onofré 
> wrote:
> 
>> Hi,
>>
>> you can use a aggregator to gather multiple reads and do a single HTTP
>> request.
>> Another option is to use a Processor.
>>
>> Regards
>> JB
>>
>> On 18/10/2019 08:27, arshad dar wrote:
>>> in the routes below i am reading from file and sending http requests, one
>>> record for each http requests. what i want to do send multiple records in
>>> http request as an array.
>>> can any one help! thanks.
>>>
>>>
>>> from(fileURI)
>>>
>>> .to(dataformatURL)
>>>
>>> .split(body())
>>>
>>> .streaming()
>>>
>>> .parallelProcessing()
>>>
>>>  .marshal().json(JsonLibrary.Jackson)
>>>
>>>.to("direct:api");
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>    from("direct:api")
>>>
>>>   .streamCaching()
>>>
>>>   .onException(Exception.class)
>>>
>>>   .handled(true)
>>>
>>>   .to(errorFormat)
>>>
>>>   .end()
>>>
>>>   .loadBalance()
>>>
>>>   .failover(maxAttempts, false, true)
>>>
>>> .to(hostsArray)
>>>
>>> end()
>>>
>>
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
> 
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: batch http requests

[Jean-Baptiste Onofré]

Hi,

you can use a aggregator to gather multiple reads and do a single HTTP
request.
Another option is to use a Processor.

Regards
JB

On 18/10/2019 08:27, arshad dar wrote:
> in the routes below i am reading from file and sending http requests, one
> record for each http requests. what i want to do send multiple records in
> http request as an array.
> can any one help! thanks.
> 
> 
> from(fileURI)
> 
> .to(dataformatURL)
> 
> .split(body())
> 
> .streaming()
> 
> .parallelProcessing()
> 
>  .marshal().json(JsonLibrary.Jackson)
> 
>.to("direct:api");
> 
> 
> 
> 
> 
> 
> 
>from("direct:api")
> 
>   .streamCaching()
> 
>   .onException(Exception.class)
> 
>   .handled(true)
> 
>   .to(errorFormat)
> 
>   .end()
> 
>   .loadBalance()
> 
>   .failover(maxAttempts, false, true)
> 
> .to(hostsArray)
> 
> end()
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Current best way to consume paged REST api / Web service

[Jean-Baptiste Onofré]

Hi Tom,

You can also use a poll enricher with a aggregation.

All depends about the trigger to call the webservice.

Regards
JB

On 16/10/2019 16:52, Tom Coudyzer wrote:
> Hi,
> 
> I just started on learning Apache Camel, so please forgive me my basic
> questions.
> 
> I'm having a webservice called via POST having a payload with paging
> information in it.
> 
> What is the best way currently in Camel to produce an output which contains
> the consolidated values from the calls.
> 
> I was able to come up with a solution by using a loopDoWhile with a
> predicate. I manipulate the paging via a header value in the Exchange.
> 
> Are there better ways to solve this? Enrich? Aggregator?
> 
> Thanks for educating me on this !
> 
> Regards,
> /Tom
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Deploy custom Camel code on Apache Karaf

[Jean-Baptiste Onofré]

Cool ! Thanks for the update.

Don't hesitate to ping if you need help.

Regards
JB

On 14/10/2019 08:43, Kirti Arora wrote:
> Hi Jean,
> 
> Thanks a lot, It worked with Activator Bundle.
> 
> Regards,
> kirti Arora
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Configuring custom Kafka producer/consumer properties on Camel Kafka component/endpoint?

[Jean-Baptiste Onofré]

That's my point: maven plugin is good, but I would like to give a chance
for the users to give their own bean.

For instance, personally, I would probably prefer to create my own bean
because I know Kafka, I know Camel, I know what I need/want ;)

Regards
JB

On 13/10/2019 18:18, Claus Ibsen wrote:
> Hi Omar
> 
> Yeah the maven plugin idea is really good.
> But maybe we need both.
> 
> The maven plugin will only get you the options of the kafka version
> that was used for that release.
> With having a way for end users to set extra options then they could
> work against newer Kafka versions without Camel have to upgrade.
> And maybe also to proprietary options on Confluent.
> 
> 
> On Sun, Oct 13, 2019 at 2:31 PM Omar Al-Safi  wrote:
>>
>> Hi Claus,
>>
>> I also thought about this, however since Kafka producers/consumers options
>> increase and some of them may gets deprecated, I was thinking we can have a
>> maven plugin that generate these configurations for us without the need to
>> do it manually, it will generate using the configDef (e.g:
>> https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/clients/consumer/ConsumerConfig.java#L555).
>> I did this for DBZ as I built a maven plugin that scrap all these config
>> and generate the camel configurations, you can take a look at my progress
>> here:
>> https://github.com/omarsmak/camel/blob/CAMEL-14009/components/camel-debezium/camel-debezium-maven-plugin/src/main/java/org/apache/camel/maven/TestMojo.java#L24.
>> Please take a look and share your thoughts about it.
>>
>> Regards,
>> Omar
>>
>> On Sun, 13 Oct 2019 at 14:12, Claus Ibsen  wrote:
>>
>>> Hi
>>>
>>> Yeah this has come up a few times that Kafka is adding new options, or
>>> more particularly Confluent adds propriety options that they dont give
>>> back to the community.
>>>
>>> Can you create a JIRA ticket.
>>>
>>> Then we can look at adding a way to add custom options. You are of
>>> course welcome to try to implement this. We love contributions.
>>> https://github.com/apache/camel/blob/master/CONTRIBUTING.md
>>>
>>> On Tue, Oct 8, 2019 at 9:57 AM Erik Boye  wrote:
>>>>
>>>> Hi,
>>>>
>>>> Is there any way to configure custom Kafka producer/consumer properties
>>> on the Camel Kafka component/endpoint (without "breaking in")?
>>>> I specifically want to configure the Confluent Kafka property with key
>>> 'value.subject.name.strategy':
>>> https://docs.confluent.io/current/schema-registry/serializer-formatter.html
>>>>
>>>> Other Camel components (i.e Camel ActiveMQ; destination.consumer) are
>>> made extensible by providing users a way to set "additional properties".
>>> Why does not Camel Kafka provide that? Until schemaRegistryURL was added as
>>> a configurable property, we had to make our own Camel Kafka Component to
>>> make it work ("breaking in"). There should definitely be a way to set
>>> additional/custom properties on Kafka producers/consumers.
>>>>
>>>> Just have a look at the Camel Kafka documentation and do a text search
>>> for Confluent:
>>> https://camel.apache.org/components/latest/kafka-component.html ;-)
>>>> Having "native" support for schemas on Kafka records is definitely a
>>> good idea, and I am pretty sure Apache Kafka will move in that direction at
>>> some point
>>>>
>>>> Erik
>>>>
>>>> "This email with attachments is solely for the use of the individual or
>>> entity to which it is addressed. It may contain confidential or privileged
>>> information. If you are not the addressee, please notify the sender and
>>> delete this message and all attachments from your files."
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>
> 
> 
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Configuring custom Kafka producer/consumer properties on Camel Kafka component/endpoint?

[Jean-Baptiste Onofré]

Hi,

IMHO, I think maven plugin is fine if it's still generate a bean. We
have to provide configuration via a bean and/or URI for most for users.
We have to think about non-Maven users like Gradle or script users.

Regards
JB

On 13/10/2019 14:30, Omar Al-Safi wrote:
> Hi Claus,
> 
> I also thought about this, however since Kafka producers/consumers options
> increase and some of them may gets deprecated, I was thinking we can have a
> maven plugin that generate these configurations for us without the need to
> do it manually, it will generate using the configDef (e.g:
> https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/clients/consumer/ConsumerConfig.java#L555).
> I did this for DBZ as I built a maven plugin that scrap all these config
> and generate the camel configurations, you can take a look at my progress
> here:
> https://github.com/omarsmak/camel/blob/CAMEL-14009/components/camel-debezium/camel-debezium-maven-plugin/src/main/java/org/apache/camel/maven/TestMojo.java#L24.
> Please take a look and share your thoughts about it.
> 
> Regards,
> Omar
> 
> On Sun, 13 Oct 2019 at 14:12, Claus Ibsen  wrote:
> 
>> Hi
>>
>> Yeah this has come up a few times that Kafka is adding new options, or
>> more particularly Confluent adds propriety options that they dont give
>> back to the community.
>>
>> Can you create a JIRA ticket.
>>
>> Then we can look at adding a way to add custom options. You are of
>> course welcome to try to implement this. We love contributions.
>> https://github.com/apache/camel/blob/master/CONTRIBUTING.md
>>
>> On Tue, Oct 8, 2019 at 9:57 AM Erik Boye  wrote:
>>>
>>> Hi,
>>>
>>> Is there any way to configure custom Kafka producer/consumer properties
>> on the Camel Kafka component/endpoint (without "breaking in")?
>>> I specifically want to configure the Confluent Kafka property with key
>> 'value.subject.name.strategy':
>> https://docs.confluent.io/current/schema-registry/serializer-formatter.html
>>>
>>> Other Camel components (i.e Camel ActiveMQ; destination.consumer) are
>> made extensible by providing users a way to set "additional properties".
>> Why does not Camel Kafka provide that? Until schemaRegistryURL was added as
>> a configurable property, we had to make our own Camel Kafka Component to
>> make it work ("breaking in"). There should definitely be a way to set
>> additional/custom properties on Kafka producers/consumers.
>>>
>>> Just have a look at the Camel Kafka documentation and do a text search
>> for Confluent:
>> https://camel.apache.org/components/latest/kafka-component.html ;-)
>>> Having "native" support for schemas on Kafka records is definitely a
>> good idea, and I am pretty sure Apache Kafka will move in that direction at
>> some point
>>>
>>> Erik
>>>
>>> "This email with attachments is solely for the use of the individual or
>> entity to which it is addressed. It may contain confidential or privileged
>> information. If you are not the addressee, please notify the sender and
>> delete this message and all attachments from your files."
>>
>>
>>
>> --
>> Claus Ibsen
>> -
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
>>
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Deploy custom Camel code on Apache Karaf

[Jean-Baptiste Onofré]

Hi,

If you don't run in Karaf, that won't work because you are in two
different JVM: the one executing your Main, the one for Karaf.

direct endpoints are visible only in the same JVM and for direct it's in
the same CamelContext ! If you want to communicate between two routes
from different camel context (still in the same JVM), you have to use
direct-vm.

If you try to execute your Main in Karaf (by dropping the jar in deploy
folder), it's what I understood, that won't work.
To do that, you have to use exec in Karaf or create a bundle with a
activator (acting as kind of main).

It would be easier to actually expose a concrete endpoint (as we do in
example with jetty for instance).

Regards
JB

On 07/10/2019 09:14, Kirti Arora wrote:
> Hi,
> 
> I'm trying to expose endpoint from the main() method using
> producerTemplate.requestBody().
> 
> I have two classes; one is main from which I'm requesting an endpoint and
> another one(SimpleRouteBuilder) to configure
> the route.
> 
> public class MainClass {
> 
> public static void main(String args[]) {
> SimpleRouteBuilder routeBuilder = new SimpleRouteBuilder();
> CamelContext ctx = new DefaultCamelContext();
> try {
> ctx.addRoutes(routeBuilder);
> ctx.start();
> 
> ProducerTemplate producerTemplate = ctx.createProducerTemplate();
> String response =
> producerTemplate.requestBody("direct:start", "", String.class);
> System.out.println(response);
> Thread.sleep(5 * 1000);
> ctx.stop();
> }
> catch (Exception e) {
> e.printStackTrace();
> }
> }
> }
> 
> 
> 
> public class SimpleRouteBuilder extends RouteBuilder {
> 
> @Override
> public void configure() {
> from("direct:start").setHeader(Exchange.HTTP_METHOD, simple("GET"))
>         .to("http://dummy.restapiexample.com/api/v1/employees;);
> }
> }
> 
> Thanks, Kirti Arora
> 
> 
> On Mon, Oct 7, 2019 at 11:43 AM Jean-Baptiste Onofré 
> wrote:
> 
>> Hi,
>>
>> Your route looks weird to me.
>>
>> What's the direct:start trigger ?
>> What do you do with the reply ?
>>
>> For instance, a valid testing route would be:
>>
>> from("timer:foo?period=5000").to("...").log("Received ${body}")
>>
>> Or at least expose an endpoint as a bridge (as we do in the Karaf example).
>>
>> Regards
>> JB
>>
>> On 07/10/2019 07:49, Kirti Arora wrote:
>>> Hi Jean and Francois,
>>>
>>> Thanks for the reply :)
>>>
>>> I have already seen the examples and successfully execute the one given
>> in
>>> /apache-karaf/examples/karaf-camel-example/karaf-camel-example-java
>>>  directory.
>>>
>>> But when I'm trying to put my own camel code, I'm not able to call the
>>> route endpoint.
>>>
>>> For eg. I want to hit the below mentioned URL
>>>
>>> from("direct:start")
>>> .setHeader(Exchange.HTTP_METHOD, simple("GET"))
>>> .to("http://dummy.restapiexample.com/api/v1/employees;);
>>>
>>> How can I do this?
>>> Thanks,
>>> Kirti Arora
>>>
>>>
>>> On Sat, Oct 5, 2019 at 5:11 PM Jean-Baptiste Onofré 
>> wrote:
>>>
>>>> Hi,
>>>>
>>>> you can take a look on the examples here:
>>>>
>>>>
>> https://github.com/apache/karaf/tree/master/examples/karaf-camel-example
>>>>
>>>> You have an example using blueprint DSL, an example using Java DSL. I'm
>>>> adding SCR package.
>>>>
>>>> If you have any question, please let me know.
>>>>
>>>> Regards
>>>> JB
>>>>
>>>> On 04/10/2019 14:22, Kirti Arora wrote:
>>>>> Hi,
>>>>>
>>>>> I'm trying to deploy my camel code(Java) on Apache Karaf. I had put my
>>>>> camel code bundle to deploy directory of Karaf but not able to find
>>>> routes
>>>>> available in the code, also not able to request the endpoints.
>>>>>
>>>>> Can someone please guide me, how can I deploy camel code on Apache
>> Karaf?
>>>>> It would be very helpful if someone can provide me an example.
>>>>>
>>>>> Thanks,
>>>>> Kirti Arora
>>>>>
>>>>
>>>> --
>>>> Jean-Baptiste Onofré
>>>> jbono...@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>
>>
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Deploy custom Camel code on Apache Karaf

[Jean-Baptiste Onofré]

Hi,

Your route looks weird to me.

What's the direct:start trigger ?
What do you do with the reply ?

For instance, a valid testing route would be:

from("timer:foo?period=5000").to("...").log("Received ${body}")

Or at least expose an endpoint as a bridge (as we do in the Karaf example).

Regards
JB

On 07/10/2019 07:49, Kirti Arora wrote:
> Hi Jean and Francois,
> 
> Thanks for the reply :)
> 
> I have already seen the examples and successfully execute the one given in
> /apache-karaf/examples/karaf-camel-example/karaf-camel-example-java
>  directory.
> 
> But when I'm trying to put my own camel code, I'm not able to call the
> route endpoint.
> 
> For eg. I want to hit the below mentioned URL
> 
> from("direct:start")
> .setHeader(Exchange.HTTP_METHOD, simple("GET"))
> .to("http://dummy.restapiexample.com/api/v1/employees;);
> 
> How can I do this?
> Thanks,
> Kirti Arora
> 
> 
> On Sat, Oct 5, 2019 at 5:11 PM Jean-Baptiste Onofré  wrote:
> 
>> Hi,
>>
>> you can take a look on the examples here:
>>
>> https://github.com/apache/karaf/tree/master/examples/karaf-camel-example
>>
>> You have an example using blueprint DSL, an example using Java DSL. I'm
>> adding SCR package.
>>
>> If you have any question, please let me know.
>>
>> Regards
>> JB
>>
>> On 04/10/2019 14:22, Kirti Arora wrote:
>>> Hi,
>>>
>>> I'm trying to deploy my camel code(Java) on Apache Karaf. I had put my
>>> camel code bundle to deploy directory of Karaf but not able to find
>> routes
>>> available in the code, also not able to request the endpoints.
>>>
>>> Can someone please guide me, how can I deploy camel code on Apache Karaf?
>>> It would be very helpful if someone can provide me an example.
>>>
>>> Thanks,
>>> Kirti Arora
>>>
>>
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Best approach to deploy camel code as standalone application

[Jean-Baptiste Onofré]

Hi,

camel-gson is missing.

If you use dynamic/standard distribution, you have to do feature:install
camel-gson, or add this as boot feature.

If you use static/immutable distribution, you have to add camel-gson
feature in your pom.xml (in the karaf-maven-plugin configuration).

Regards
JB

On 04/10/2019 15:31, Jaiprakash Mewada wrote:
> Hi Team,
> 
> I have created stand alone program in Karaf with Camel code. Somewhere in
> my program, I am using gson to marshal-unmarshal the data. When I am trying
> to start my application with this command: "bundle:start
> mvn:co.hotwax/CamelApplication/1.0.0-SNAPSHOT", I am getting below error.
> 
> *Error executing command: Error executing command on bundles: Error
> starting bundle 96: Unable to resolve
> co.hotwax.debug-utils.CamelApplication [96](R 96.0): missing requirement
> [co.hotwax.debug-utils.CamelApplication [96](R 96.0)] osgi.wiring.package;
> (&(osgi.wiring.package=com.google.gson)(version>=2.8.0)(!(version>=3.0.0)))
> Unresolved requirements: [[co.hotwax.debug-utils.CamelApplication [96](R
> 96.0)] osgi.wiring.package;
> (&(osgi.wiring.package=com.google.gson)(version>=2.8.0)(!(version>=3.0.0)))]*
> 
> Can someone please guide me to understand this error, what exactly it means.
> 
> *Note*: When I am removing the gson code, then program is getting started
> successfully.
> 
> 
> On Thu, Sep 26, 2019 at 9:45 AM Jean-Baptiste Onofré 
> wrote:
> 
>> Hi,
>>
>> As side note, you can run Camel/Ofbiz applications (all together) in
>> Karaf standalone/static distribution:
>>
>> http://blog.nanthrax.net/?p=893
>>
>> Regards
>> JB
>>
>> On 25/09/2019 12:39, Jaiprakash Mewada wrote:
>>> Hi Team,
>>>
>>> I am beginner in Apache Camel. I have ofbiz code running on different
>> jvm.
>>> I want Camel code to be running on different jvm. I need to send the data
>>> from ofbiz to third party using camel's route.
>>>
>>> It looks like I need to run standalone application of Camel. Can someone
>>> please guide me, what is the best possible way to implement this ?
>>>
>>> And If I implement separate standalone application, then how would I call
>>> the code of Camel from ofbiz which is running on different jvm ?
>>>
>>
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
> 
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Deploy custom Camel code on Apache Karaf

[Jean-Baptiste Onofré]

Hi,

you can take a look on the examples here:

https://github.com/apache/karaf/tree/master/examples/karaf-camel-example

You have an example using blueprint DSL, an example using Java DSL. I'm
adding SCR package.

If you have any question, please let me know.

Regards
JB

On 04/10/2019 14:22, Kirti Arora wrote:
> Hi,
> 
> I'm trying to deploy my camel code(Java) on Apache Karaf. I had put my
> camel code bundle to deploy directory of Karaf but not able to find routes
> available in the code, also not able to request the endpoints.
> 
> Can someone please guide me, how can I deploy camel code on Apache Karaf?
> It would be very helpful if someone can provide me an example.
> 
> Thanks,
> Kirti Arora
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: CAMEL SCR (DEPRECATED)

[Jean-Baptiste Onofré]

It's possible to use scr to expose the CamelContext and route as
service, but it's not in Camel anymore, you have to do your own.

AFAIR, I did an example in Karaf about that (not sure it's merged, I
will check).

Regards
JB

On 03/10/2019 15:11, Elton Barbosa Rodrigues wrote:
> Hello everyone!
> 
> I took a look at https://camel.apache.org/components/2.x/scr.html, looks like 
> that the CAMEL SCR is deprecated is it?
> 
> What is the new one to replace the camel-scr deprecated?
> 
> Thanks in advance!
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: camel-influxdb/NoClassDefFoundError/Moshi

[Jean-Baptiste Onofré]

;>>>>> Il giorno mar 1 ott 2019 alle ore 16:11 David Ecker <
>>>>>>>>> da...@ecker-software.de>
>>>>>>>>>> ha scritto:
>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> I am running karaf 4.2.6 and camel 2.24.2 (OpenJDK-8, docker).
>>>>>>>>>>>
>>>>>>>>>>> Dependencies installed through feature definition automatically:
>>>>>>>>>>>
>>>>>>>>>>>
>>>> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.influxdb-java/2.14_1
>>>> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.retrofit/2.4.0_1
>>>>>>>>>>> ...
>>>>>>>>>>>
>>>>>>>>>>> I am trying to create the bean for the influxdb connection using
>>>> the
>>>>>>>>>>> FactoryBuilder but I am getting the following error:
>>>>>>>>>>>
>>>>>>>>>>> 14:08:52.673 ERROR [pipe-stop 305] Unable to start container for
>>>>>>>>>>> blueprint bundle com.ta-systeme.velocloud.VCEPathCollectorSSH/
>>>> 0.0.1.
>>>>>>>>>>> SNAPSHOT
>>>>>>>>>>> org.osgi.service.blueprint.container.ComponentDefinitionException:
>>>>>>> Error
>>>>>>>>>>> when instantiating bean infxluxDBConnection of class
>>>>>>>>>>> org.influxdb.InfluxDBFactory
>>>>>>>>>>>  at
>>>>>>>>>>>
>>>> org.apache.aries.blueprint.container.BeanRecipe.wrapAsCompDefEx(BeanRecipe.java:362)
>>>>>>>>>>> ~[68:org.apache.aries.blueprint.core:1.10.2]
>>>>>>>>>>> ...
>>>>>>>>>>> Caused by: java.lang.NoClassDefFoundError:
>>>>>>>>> com/squareup/moshi/Moshi$Builder
>>>>>>>>>>>  at
>>>>>>>>>>>
>>>> retrofit2.converter.moshi.MoshiConverterFactory.create(MoshiConverterFactory.java:48)
>>>>>>>>>>> ~[?:?]
>>>>>>>>>>>  at
>>>>>>> org.influxdb.impl.InfluxDBImpl.(InfluxDBImpl.java:169)
>>>>>>>>> ~[?:?]
>>>>>>>>>>>  at
>>>>>>> org.influxdb.impl.InfluxDBImpl.(InfluxDBImpl.java:123)
>>>>>>>>> ~[?:?]
>>>>>>>>>>>  at
>>>>>>> org.influxdb.impl.InfluxDBImpl.(InfluxDBImpl.java:187)
>>>>>>>>> ~[?:?]
>>>>>>>>>>>  at
>>>>>>> org.influxdb.InfluxDBFactory.connect(InfluxDBFactory.java:30)
>>>>>>>>>>> ~[?:?]
>>>>>>>>>>> 
>>>>>>>>>>>
>>>>>>>>>>> Any idea what I am doing wrong?
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> David
>>>>>>>>>>>
>>>>>>>>>>>
>>>>
>>
> 
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Best approach to deploy camel code as standalone application

[Jean-Baptiste Onofré]

Hi,

As side note, you can run Camel/Ofbiz applications (all together) in
Karaf standalone/static distribution:

http://blog.nanthrax.net/?p=893

Regards
JB

On 25/09/2019 12:39, Jaiprakash Mewada wrote:
> Hi Team,
> 
> I am beginner in Apache Camel. I have ofbiz code running on different jvm.
> I want Camel code to be running on different jvm. I need to send the data
> from ofbiz to third party using camel's route.
> 
> It looks like I need to run standalone application of Camel. Can someone
> please guide me, what is the best possible way to implement this ?
> 
> And If I implement separate standalone application, then how would I call
> the code of Camel from ofbiz which is running on different jvm ?
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: JMS pub/sub (using Camel) performance issue with MQ in XA transactions

[Jean-Baptiste Onofré]

Hi,

What about using pure ACK mode ?

You can see an example with queue (same can be applied to topic) here:
http://blog.nanthrax.net/?p=820

My point is: do you need XA as AFAIU you are using only JMS as resource
(XA is required when you want to use the same transaction with different
backends like JMS and database for instance) ?

Regards
JB

On 03/09/2019 19:03, Benoit Fortin wrote:
> We have a java application doing JMS subscriptions that is using Camel as
> its JMS provider.
> 
> The application is subscribing to a topic using XA. It consumes 1 message
> in the queue, and then closes the XA transaction (each message is part of
> an XA transaction). Then the application re-attaches itself to the topic to
> start over the same process for each message.
> 
> When there are no messages to process, the client waits for 45 seconds
> (which is the XA transaction timeout) before closing the request and the XA
> transaction and starting a new iteration.
> 
> I have analyzed how this process is actually being done using a tcpdump,
> and here is what I found:
> 
> ——
> 
> MQ Client --[XA_START]--> MQ Server
> 
> MQ Client <--[XA_START_REPLY]-- MQ Server
> 
> 
> MQ Client --[SPI (SUBSCRIBE)]--> MQ Server
> 
> MQ Client <--[SPI REPLY]-- MQ Server
> 
> 
> MQ Client --[REQUEST_MSGS]--> MQ Server
> 
> MQ Client --[REQUEST_MSGS]--> MQ Server
> 
> MQ Client <--[NOTIFICATION]-- MQ Server
> 
> 
> MQ Client --[MQCLOSE]--> MQ Server
> 
> MQ Client <--[MQCLOSE_REPLY]-- MQ Server
> 
> 
> MQ Client --[XA_END]--> MQ Server
> 
> MQ Client <--[XA_END_REPLY]-- MQ Server
> 
> 
> MQ Client --[XA_COMMIT]--> MQ Server
> 
> MQ Client <--[XA_COMMIT_REPLY]-- MQ Server
> 
> ——
> 
> This is process is on a durable subscription, so each of the iterations
> (even when there is no message to consume) ends up generating I/O on the MQ
> server (I think, mostly on the SYSTEM.DURABLE.SUBSCRIBER.QUEUE queue, where
> MQ keeps trace of its subscribers).
> 
> Having a somewhat high number of subscribers doing this process, the MQ
> server ends up I/O bound, with +4000 IOPS on the MQ logs disks (even
> outside of business hours, when there are no messages to consume). This
> process also consumes ~3 CPU outside of business hours.
> 
> I am a bit puzzled that using XA on pub/sub scales so bad, and I am
> wondering if there is any way to implement this solution without doing so
> much subscribe operations.
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Code of calling rest service is not working

[Jean-Baptiste Onofré]

You can also use camel-cxfrs for rest server and/or client.

Regards
JB

Le 29 juil. 2019 à 15:36, à 15:36, Omar Al-Safi  a écrit:
>I am new to Camel as well, I was figuring things on the way :). First
>you
>need to use a REST component, you can use the REST DSL
>, however this is only a DSL
>not a
>actual http server, you will need to include an http server component
>as
>well (e.g:  camel-netty4-http, camel-restlet, camel-spark-rest ..etc),
>once
>you included it, you will need to tell Camel to use the specified
>component
>through the configuration RouteBuilder
>(e.g: restConfiguration().component("spark-rest").port(8000);). Also in
>your above example, the JVM will terminate immediately, and hence Camel
>will stop immediately. Therefore you need to either use the Main class
>that
>is shipped in Camel Core (example
>)
>or keep the JVM running indefinitely by adding
>(Thread.sleep(Integer.MAX_VALUE);)
>
>You can take a look here for an example:
>https://www.codepile.net/pile/p4dDJd4x
>
>Please note I also included the camel-spark-rest component in the POM
>file
>as well.
>
>On Mon, 29 Jul 2019 at 14:06, Jaiprakash Mewada <
>jaiprakash.mew...@hotwaxsystems.com> wrote:
>
>> Hi Team,
>>
>> I am beginner in apache camel. I want to make to rest call but not
>able to
>> get expected result. Can someone help me, what exact change I need to
>do in
>> below code in order to receive the json response.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *import org.apache.camel.CamelContext;import
>> org.apache.camel.ConsumerTemplate;import
>org.apache.camel.Exchange;import
>> org.apache.camel.Processor;import
>org.apache.camel.ProducerTemplate;import
>> org.apache.camel.builder.RouteBuilder;import
>> org.apache.camel.impl.DefaultCamelContext;public class
>> CamelHelloWorldExample { public static void main(String[] args)
>throws
>> Exception { CamelContext context = new DefaultCamelContext();
>> context.setTracing(true); context.addRoutes(new RouteBuilder() {
>@Override
>> public void configure() throws Exception {
>System.out.println("---Start
>> of RouteBuilder---");
>> from("direct:start").setHeader(Exchange.HTTP_METHOD, simple("GET"))
>> .to("http://dummy.restapiexample.com/api/v1/employee/330
>> ").process(new
>> Processor() { public void process(Exchange exchange) throws Exception
>{
>> System.out.println(exchange.getIn().getBody(String.class)); } } )
>> .to("seda:end"); System.out.println("---End of
>> RouteBuilder---"); } } ); context.start(); ProducerTemplate
>> prodTemp = context.createProducerTemplate();
>> prodTemp.sendBody("direct:start", "Hello"); ConsumerTemplate consTemp
>=
>> context.createConsumerTemplate(); String msg =
>> consTemp.receiveBody("seda:end", String.class);
>System.out.println(msg);
>> }}*
>>
>> --
>> *Thanks & Regards,*
>> *Jaiprakash Mewada*
>> Senior Enterprise Software Engineer
>>
>> *HotWax Systems*
>>

Re: R: Checkout tag using Git component

[Jean-Baptiste Onofré]

I don't think it's big deal.

The "classic" approach is to clone the repo and then checkout on tag:

git clone https://gitbox.apache.org/repos/asf/camel
git checkout 

Regards
JB

On 02/01/2019 00:17, Andrea Cosentino wrote:
> Probably it has to be implemented. Can you please create an enhancement 
> request on Camel JIRA?
> Thanks
> 
> Inviato da Yahoo Mail su Android 
>  
>   Il lun, 31 dic, 2018 alle 20:05, Shultz, Dmitry 
> ha scritto:   Hi All,
> 
> I'm using Git component to work with a Git repo. Trying to check out some 
> specific tag (like here 
> https://stackoverflow.com/questions/791959/download-a-specific-tag-with-git)
> Not sure, but it seems like the 'checkout' operation is not supported yet.
> Do I have to use the JGit API for this or there is some other way to do it 
> using camel-git?
> 
> Cheers and Happy New Year!
> 
> Dmitry  
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Replacement for Tracer?

[Jean-Baptiste Onofré]

I did a command while ago and tracer support in Karaf Decanter.

I think I forgot to merge on new branches.

Regards
JB

Le 13 août 2018 à 19:20, à 19:20, Quinn Stevenson  
a écrit:
>The docs also refer to a Karaf command to control the tracer - I can’t
>find that either.
>
>> On Aug 13, 2018, at 11:04 AM, Quinn Stevenson
> wrote:
>>
>> OK - is there a way to configure the BacklogTracer to log the
>messages to the log file the way that the Tracer does?  I can’t seem to
>find an example for that, and my customers use the Tracer for debugging
>routes during development - so I’d like to be able to give them a
>non-deprecated alternative to the Tracer.
>>
>>
>>
>>> On Aug 13, 2018, at 10:15 AM, Claus Ibsen 
>wrote:
>>>
>>> Hi
>>>
>>> BacklogTracer or some better implementation we will do in the future
>>> (Camel 3 etc).
>>>
>>>
>>> On Mon, Aug 13, 2018 at 6:03 PM, Quinn Stevenson
>>>  wrote:
 The Tracer is marked as deprecated, but I can’t seem to find
>anything on a replacement.  What will be replacing Tracer?



>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>>

Re: Parsing unstructured Text in Camel

[Jean-Baptiste Onofré]

Hi Jan

You can always use a custom processor for that.

Regards
JB⁣​

On Nov 25, 2016, 08:16, at 08:16, Jan Bernhardt  wrote:
>Hi Camel Users,
>
>
>is there any component which helps me to parse plain text? Not JSON,
>XML or CSV.
>
>
>My use case is that I receive an E-Mail with multiple keywords in the
>Subject as well as in the body.
>
>I could not find any component that would help me to parse certain
>values from my multiline plaintext.
>
>
>I need something like freemarker but the other way around. Getting the
>fulltext and parsing certain values from this text (for example with
>regex).
>
>
>Any help would be much appreciated.
>
>
>Many thanks
>
>Jan

Re: Zip all files available in folder - synchronously

[Jean-Baptiste Onofré]

Hi Arpit,

The aggregate should work for that. All depends on the "stopping condition".

Regards
JB

On 10/31/2016 11:04 PM, Goyal, Arpit wrote:

Hi Colleagues,

I want to read all file and aggregate into one single zip, but the batch 
consumer always run in different thread. What needs to be done additionally to 
get the response synchronously?

Regards,
Arpit.

   DefaultCamelContext c = new DefaultCamelContext();
try {
  c.addRoutes(new RouteBuilder() {

@Override
public void configure() throws Exception {
  
from("direct:start").from("file:/tmp/wiretap/6443391d-196a-4c75-b2f8-9c0696025b56/?include=.*=true=2500")
  .aggregate(body(), new 
CustomZipAggregationStrategy()).completionFromBatchConsumer().to("file:/tmp/wiretap/aggregate");
}
  });

  ProducerTemplate template = c.createProducerTemplate();
  c.start();
  template.start();
  template.requestBody("direct:start", "BEGIN"); //synchronously response 
on completion of zip construction...
} finally {
  c.stop();
}




--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Release of the first beta of a Camel component for Petals ESB

[Jean-Baptiste Onofré]

Hi Victor,

I guess that you meant Camel 2.12.x (not 5.12.x ;)).

Thanks for the update !

Regards
JB

On 05/22/2015 11:04 AM, Victor NOËL wrote:

Hi,

Just for your information, we released yesterday version 4.3 of the
Petals ESB that includes our first beta of a service engine for Apache
Camel:
http://petals.ow2.org/index.html

In a few words, you can now deploy Camel routes into the service bus and
make them consumes and provides Petal services (JBI).

If you are interested, there is the documentation of the service engine
here:
https://doc.petalslink.com/display/petalscomponents/Petals-SE-Camel+0.5.0-SNAPSHOT


Unfortunately, Petals 4.3 is using Java 6 so we had to settle for Camel
5.12.x, but the next version of Petals (v5) will use Java 7.

Thanks for your help until now :)

Victor @ Linagora


--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Camel M2M gateway project

[Jean-Baptiste Onofré]

Cool, thanks Henryk !

Regards
JB

On 03/03/2015 09:36 PM, Henryk Konsek wrote:

Hi,

For those interested in the Internet Of Things and M2M - I started a
small project called Camel M2M gateway [1]. I want it to be the
landing page for the Camel enthusiast interesting in putting Camel
into small-medium processing devices like Raspberry Pi, BeagleBone
Black and so forth.

This is also a place where I plan to put my benchmarks code and
results (starting by the end of this week).

You're more then welcome to participate! :)

Cheers.

[1] https://github.com/hekonsek/camel-m2m-gateway



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: WARN org.apache.sshd.client.session.ClientSessionImpl - Exception caught org.apache.sshd.common.SshException: MAC Error

[Jean-Baptiste Onofré]

Hi Gary,

this error is a bug in sshd 0.9.0. It has been fixed in 0.10.0.

Which Camel version are you using ?
Camel 2.13.3 uses sshd 0.10.1 (including the fix).

Regards
JB

On 03/02/2015 11:27 PM, Gary wrote:

org.apache.sshd.common.SshException: MAC Error


--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Can i get the Operation name from camel.

[Jean-Baptiste Onofré]

Hi Frank,

it depends the data format that you use on the CXF endpoint.

Using the default data format (Message), you can retrieve the operation 
name from the CxfConstants.OPERATION_NAME header:


String operation = 
(String)exchange.getIn().getHeader(CxfConstants.OPERATION_NAME);


Regards
JB

On 03/03/2015 09:27 AM, Frankiboy wrote:

Im using CXF, im would like to log the operation name.

Is there a easy way to get the operation name, from the exchange or ?

Frank



--
View this message in context: 
http://camel.465427.n5.nabble.com/Can-i-get-the-Operation-name-from-camel-tp5763459.html
Sent from the Camel - Users mailing list archive at Nabble.com.



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Can i get the Operation name from camel.

[Jean-Baptiste Onofré]

it's what I said (sorry if I'm not clear): CXF_Message/Payload/POJO is 
OK, not Message.


Regards
JB

On 03/03/2015 11:02 AM, Frankiboy wrote:

Nt route starts like this:

 from(cxf:bean:hubws?dataFormat=MESSAGE).streamCaching


This give me null in the operation name...

   Message in = exchange.getIn();

String operation = (String)in.getHeader(CxfConstants.OPERATION_NAME);

Maybe becouse the dataFomat is MESSAGE ?

Frank



--
View this message in context: 
http://camel.465427.n5.nabble.com/Can-i-get-the-Operation-name-from-camel-tp5763459p5763471.html
Sent from the Camel - Users mailing list archive at Nabble.com.



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Can i get the Operation name from camel.

[Jean-Baptiste Onofré]

Yes, it's not what I said ?
If not, sorry about that (too much things in the same time ;)).

Regards
JB

On 03/03/2015 11:11 AM, Morgan Hautman wrote:

Jb,

Sorry to correct you but the default dataFormat is POJO.

Regards,
Morgan

On 3/03/2015 10:22, Jean-Baptiste Onofré wrote:

Hi Frank,

it depends the data format that you use on the CXF endpoint.

Using the default data format (Message), you can retrieve the
operation name from the CxfConstants.OPERATION_NAME header:

String operation =
(String)exchange.getIn().getHeader(CxfConstants.OPERATION_NAME);

Regards
JB

On 03/03/2015 09:27 AM, Frankiboy wrote:

Im using CXF, im would like to log the operation name.

Is there a easy way to get the operation name, from the exchange or ?

Frank



--
View this message in context:
http://camel.465427.n5.nabble.com/Can-i-get-the-Operation-name-from-camel-tp5763459.html

Sent from the Camel - Users mailing list archive at Nabble.com.







--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: WARN org.apache.sshd.client.session.ClientSessionImpl - Exception caught org.apache.sshd.common.SshException: MAC Error

[Jean-Baptiste Onofré]

Maybe you can paste on pastebin or gist ?

Regards
JB

On 03/02/2015 10:08 PM, Gary wrote:

Hey Jean, can you/I upload a file here I took a trace dump. there are
several errors I am focusing on this one right now :). thanks



--
View this message in context: 
http://camel.465427.n5.nabble.com/WARN-org-apache-sshd-client-session-ClientSessionImpl-Exception-caught-org-apache-sshd-common-SshExcr-tp5763429p5763433.html
Sent from the Camel - Users mailing list archive at Nabble.com.



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: WARN org.apache.sshd.client.session.ClientSessionImpl - Exception caught org.apache.sshd.common.SshException: MAC Error

[Jean-Baptiste Onofré]

Hi Gary,

do you have the full stack trace of the SshException ?

Thanks,
Regards
JB

On 03/02/2015 09:39 PM, Gary wrote:

Help!

What is causing this message - intermittently throughout the day I get this
and it hangs my processes, or actually terminates the Fuse console

WARN org.apache.sshd.client.session.ClientSessionImpl - Exception caught
org.apache.sshd.common.SshException: MAC Error


I can't find much on why and what to do about this.

thanks!!!



--
View this message in context: 
http://camel.465427.n5.nabble.com/WARN-org-apache-sshd-client-session-ClientSessionImpl-Exception-caught-org-apache-sshd-common-SshExcr-tp5763429.html
Sent from the Camel - Users mailing list archive at Nabble.com.



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: How to import camel in a java application program

[Jean-Baptiste Onofré]

A NoClassDefFound is more related to classloader issue than class not found. In 
which container are you running your camel route ?
RegardsJB


Sent from my Samsung device

 Original message 
From: Morgan Hautman morgan.haut...@gmail.com 
Date: 26/02/2015  10:10  (GMT+01:00) 
To: users@camel.apache.org 
Subject: Re: How to import camel in a java application program 

Hi,

If you're using maven,

dependency
 groupIdorg.apache.httpcomponents/groupId
 artifactIdhttpclient/artifactId
 version4.4/version
/dependency


On 26/02/2015 10:03, imranrazakhan wrote:
 Hi, I used same example but its giving following error

 public void configure() {
   
   from(jetty:http://localhost:8181/mytestservice;).process(
   new Processor() {
   @Override
   public void process(Exchange exchange) 
 throws Exception {
   String message = 
 exchange.getIn().getBody(String.class);
   System.out.println(Hello Mr : 
 + message);
   
 exchange.getOut().setBody(Hello world Mr  + message);
   }
   });
   }

 Exception in thread main java.lang.NoClassDefFoundError:
 org/apache/commons/httpclient/HttpConnectionManager
  at java.lang.Class.getDeclaredConstructors0(Native Method)
  at java.lang.Class.privateGetDeclaredConstructors(Unknown Source)
  at java.lang.Class.getConstructor0(Unknown Source)
  at java.lang.Class.newInstance(Unknown Source)
  at
 org.apache.camel.util.ObjectHelper.newInstance(ObjectHelper.java:1258)

 Above mentioned jars are in my class-path

 Manifest-Version: 1.0
 Main-Class: com.my.test.jetty.MainApp
 Class-path: camel-core-2.13.1.jar
   slf4j-api-1.6.6.jar
   log4j-1.2.17.jar
   slf4j-log4j12-1.7.7.jar
   camel-spring-2.13.1.jar
   camel-jetty-2.13.1.jar
   camel-http-2.13.1.jar
   camel-test-2.13.1.jar




 --
 View this message in context: 
 http://camel.465427.n5.nabble.com/How-to-import-camel-in-a-java-HTTP-server-application-program-tp471924p5763196.html
 Sent from the Camel - Users mailing list archive at Nabble.com.

RE: [HEADS UP] - camel-scr for OSGi with pure Java in Camel 2.15

[Jean-Baptiste Onofré]

Hi Claude

Thanks for the update. I will take a look ASAP. 

Regards
JB


Sent from my Samsung Galaxy smartphone.


 Original message 
From: Claus Ibsen claus.ib...@gmail.com 
Date:09/11/2014  09:42  (GMT+01:00) 
To: users@camel.apache.org 
Cc:  
Subject: [HEADS UP] - camel-scr for OSGi with pure Java in Camel 2.15 

Hi

There is a great contribution for a new camel-scr module that allows
end users to use OSGi declarative services instead of spring-dm /
blueprint.

The code has just been pushed to master branch, but there is still
some work to finish and polish the code.

But I wanted to bring this to attention, so we can have more eyes on
this - especially for the OSGi folks.

The JIRA ticket is, with some bullets to look at:
https://issues.apache.org/jira/browse/CAMEL-7997

And the code is in the camel-scr module. And there is a camel-scr
feature to install the module.





-- 
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/