[jira] [Updated] (CAMEL-19727) okhttp client - Align to use a single version
[ https://issues.apache.org/jira/browse/CAMEL-19727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19727: Priority: Minor (was: Major) > okhttp client - Align to use a single version > - > > Key: CAMEL-19727 > URL: https://issues.apache.org/jira/browse/CAMEL-19727 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Claus Ibsen >Priority: Minor > > There are both v3 and v4 (v4 is kotlin, and v3 is java). > We should try to align transitive dependencies to a single version if > possible. > Also we should try to remove okhttp client if possible -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20093) camel-catalog: duplicated code
[ https://issues.apache.org/jira/browse/CAMEL-20093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851620#comment-17851620 ] Claus Ibsen commented on CAMEL-20093: - Is there more work on this > camel-catalog: duplicated code > -- > > Key: CAMEL-20093 > URL: https://issues.apache.org/jira/browse/CAMEL-20093 > Project: Camel > Issue Type: Improvement > Components: camel-catalog >Affects Versions: 4.1.0, 4.2.0 >Reporter: Otavio Rodolfo Piske >Assignee: Nikita_Konovalov >Priority: Minor > Labels: help-wanted > Fix For: 4.x > > > There's a pretty large amount of duplicated code within camel-catalog. It > would be good to clean it up, create common components, helpers an utilities > that serve all of the code in there. > As an additional improvement, documenting the code and ensuring it's easy to > maintain would be good as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20195) Components with mixed jetty versions
[
https://issues.apache.org/jira/browse/CAMEL-20195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20195:
Priority: Minor (was: Major)
> Components with mixed jetty versions
>
>
> Key: CAMEL-20195
> URL: https://issues.apache.org/jira/browse/CAMEL-20195
> Project: Camel
> Issue Type: Dependency upgrade
>Reporter: Federico Mariani
>Priority: Minor
> Fix For: 4.x
>
>
> The following camel spring boot components are using different jetty versions:
> camel-debezium-mysql-starter
> camel-debezium-postgres-starter
> camel-hdfs-starter
> in particular, these 3 components requires jetty 9, but the camel and spring
> boot boms overrides the jetty version to 12 therefore the dependency tree is
> like this:
> {code:java}
> [INFO] | | | | +- org.eclipse.jetty:jetty-server:jar:12.0.3:runtime
> [INFO] | | | | | +- org.eclipse.jetty:jetty-http:jar:12.0.3:runtime
> [INFO] | | | | | \- org.eclipse.jetty:jetty-io:jar:12.0.3:runtime
> [INFO] | | | | +-
> org.eclipse.jetty:jetty-servlet:jar:9.4.52.v20230823:runtime
> [INFO] | | | | | +- org.eclipse.jetty:jetty-security:jar:12.0.3:runtime
> [INFO] | | | | | \- org.eclipse.jetty:jetty-util-ajax:jar:12.0.3:runtime
> [INFO] | | | | +-
> org.eclipse.jetty:jetty-servlets:jar:9.4.52.v20230823:runtime
> [INFO] | | | | | +-
> org.eclipse.jetty:jetty-continuation:jar:9.4.52.v20230823:runtime
> [INFO] | | | | | \- org.eclipse.jetty:jetty-util:jar:12.0.3:runtime
> [INFO] | | | | +- org.eclipse.jetty:jetty-client:jar:12.0.3:runtime
> [INFO] | | | | | \-
> org.eclipse.jetty:jetty-alpn-client:jar:12.0.3:runtime
> {code}
> as you can see, jetty9 and jetty12 versions are mixed, we do not have any
> example or test for this component, but I am pretty sure it won't work, and
> most probably was not working in the past (I do not think that jetty9 was
> compatible with 11).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20195) Components with mixed jetty versions
[
https://issues.apache.org/jira/browse/CAMEL-20195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851618#comment-17851618
]
Claus Ibsen commented on CAMEL-20195:
-
I wonder if this is better on latest SB 3.3.x and Debezium
> Components with mixed jetty versions
>
>
> Key: CAMEL-20195
> URL: https://issues.apache.org/jira/browse/CAMEL-20195
> Project: Camel
> Issue Type: Dependency upgrade
>Reporter: Federico Mariani
>Priority: Major
> Fix For: 4.x
>
>
> The following camel spring boot components are using different jetty versions:
> camel-debezium-mysql-starter
> camel-debezium-postgres-starter
> camel-hdfs-starter
> in particular, these 3 components requires jetty 9, but the camel and spring
> boot boms overrides the jetty version to 12 therefore the dependency tree is
> like this:
> {code:java}
> [INFO] | | | | +- org.eclipse.jetty:jetty-server:jar:12.0.3:runtime
> [INFO] | | | | | +- org.eclipse.jetty:jetty-http:jar:12.0.3:runtime
> [INFO] | | | | | \- org.eclipse.jetty:jetty-io:jar:12.0.3:runtime
> [INFO] | | | | +-
> org.eclipse.jetty:jetty-servlet:jar:9.4.52.v20230823:runtime
> [INFO] | | | | | +- org.eclipse.jetty:jetty-security:jar:12.0.3:runtime
> [INFO] | | | | | \- org.eclipse.jetty:jetty-util-ajax:jar:12.0.3:runtime
> [INFO] | | | | +-
> org.eclipse.jetty:jetty-servlets:jar:9.4.52.v20230823:runtime
> [INFO] | | | | | +-
> org.eclipse.jetty:jetty-continuation:jar:9.4.52.v20230823:runtime
> [INFO] | | | | | \- org.eclipse.jetty:jetty-util:jar:12.0.3:runtime
> [INFO] | | | | +- org.eclipse.jetty:jetty-client:jar:12.0.3:runtime
> [INFO] | | | | | \-
> org.eclipse.jetty:jetty-alpn-client:jar:12.0.3:runtime
> {code}
> as you can see, jetty9 and jetty12 versions are mixed, we do not have any
> example or test for this component, but I am pretty sure it won't work, and
> most probably was not working in the past (I do not think that jetty9 was
> compatible with 11).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20489) camel-openapi-java - Rest configuration for servers
[ https://issues.apache.org/jira/browse/CAMEL-20489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851617#comment-17851617 ] Claus Ibsen commented on CAMEL-20489: - If you use contract first with the new openApi specification file directly then you can control the server with apiHost: 'http:myhost:1234` And you can turn it off with hostNameResolver: 'none' By default it uses the host name of the platform-http of the running Camel application > camel-openapi-java - Rest configuration for servers > --- > > Key: CAMEL-20489 > URL: https://issues.apache.org/jira/browse/CAMEL-20489 > Project: Camel > Issue Type: Improvement > Components: camel-rest-openapi >Reporter: Claus Ibsen >Priority: Minor > Fix For: 4.x > > > OpenAPI v3 has servers to configure instead of the old basePath stuff > https://swagger.io/docs/specification/api-host-and-base-path/ > We may want to adjust restConfiguration to allow to configure multiple > servers so the generated api-doc can include this. Today we can only have 1 > server due to the old v2 stuff. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20585) Camel-package-maven-plugin: generates test configurers in non-tests artifacts
[
https://issues.apache.org/jira/browse/CAMEL-20585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20585:
Issue Type: Task (was: Bug)
> Camel-package-maven-plugin: generates test configurers in non-tests artifacts
> -
>
> Key: CAMEL-20585
> URL: https://issues.apache.org/jira/browse/CAMEL-20585
> Project: Camel
> Issue Type: Task
> Components: build system, camel-package-maven-plugin
>Affects Versions: 4.5.0
>Reporter: Jiri Ondrusek
>Priority: Minor
> Fix For: 4.x
>
>
> Change
> [https://github.com/apache/camel/commit/0fb5aa31ae590eb042a1664ff18b6d5c44acc5c4#diff-8c376760c1f21c10dc4f6b051f972405cc04fc1ce9ca636a478cc5cfb8a1f51c]
> causes that for example _camel-main.jar_ contains test configurers like
> {code:java}
> org.apache.camel.main.MySecondBar, org.apache.camel.main.MySecondFoo| {code}
> As you can see
> herehttps://github.com/apache/camel/commit/0fb5aa31ae590eb042a1664ff18b6d5c44acc5c4
> different method is called.
>
> The original method was:
> {code:java}
> public static boolean updateResource(BuildContext buildContext, Path out,
> String data) {
> try {
> if (FileUtil.updateFile(out, data)) {
> refresh(buildContext, out);
> return true;
> }
> } catch (IOException e) {
> throw new IOError(e);
> }
> return false;
> {code}
> which can not create a test resource.
> Newly called method
> {code:java}
> protected boolean updateResource(Path dir, String fileName, String data) {
> boolean updated;
> updated = updateResource(buildContext, dir.resolve(fileName), data);
> if (!fileName.endsWith(".java")) {
> > Path outputDir =
> > Paths.get(project.getBuild().getOutputDirectory());
> > updated |= updateResource(buildContext,
> > outputDir.resolve(fileName), data);
> }
> return updated;
> {code}
> refreshes also resources in outputDiectorry. Therefore some test configurers
> are created during build of the artifact.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19667) camel-tracing: Context is not propagated from exchange header to OpenTelemetry Context
[
https://issues.apache.org/jira/browse/CAMEL-19667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851616#comment-17851616
]
Claus Ibsen commented on CAMEL-19667:
-
There is a new option to turn on tracing processors (camel 4.7)
https://github.com/apache/camel/blob/main/components/camel-opentelemetry/src/main/docs/opentelemetry.adoc#configuration
> camel-tracing: Context is not propagated from exchange header to
> OpenTelemetry Context
> --
>
> Key: CAMEL-19667
> URL: https://issues.apache.org/jira/browse/CAMEL-19667
> Project: Camel
> Issue Type: Improvement
> Components: camel-opentelemetry, camel-tracing
>Affects Versions: 3.20.5, 3.20.6, 3.21.0, 4.0-M3
>Reporter: Roman Kvasnytskyi
>Priority: Major
> Labels: bug, opentelemetry, tracing
> Fix For: 4.x
>
> Attachments: screenshot-1.png
>
>
> I am using OpenTelemetry Agent for tracing along with
> camel-opentelemetry-starter that configures OpenTelemetryTracer for Camel
> aligned with camel-tracing.
> I see my spans for Camel inside a single trace, but after control is passed
> to the Processor process method next spans are disassociated from the trace
> and are created in the separate trace.
> The tracing context does not seem to get propagated, and the resulting spans
> end up being disassociated. For example:
> {code:java}
> from("timer:tick?period=5s)
> .process("myProcessor");
> {code}
> {code:java}
> public class MyProcessor implements Processor {
> private final HttpClient someClient = new HttpClient();
> @Override
> public void process(Exchange exchange) {
> // http client is instrumented and also produces spans
> someClient.get('/example');
> }
> }
> {code}
> This results in 2 spans. One for timer:tick & another for a client call. The
> problem is that the parent span for client calls is not set, so they appear
> as 2 distinct traces.
> My exchange headers contain traceparent header with all data which should be
> put inside the OpenTelemetry context, but they do not.
> I have come up with a workaround. The idea is trivial - get traceparent
> header if it is present in exchange, parse trace metadata from it, create a
> SpanContext object, and put it as a parent for the current OpenTelemetry
> context.
> It looks like this:
> {code:java}
> public class TraceEnrichingProcessor implements Processor {
> private final Processor delegate;
> public TraceEnrichingProcessor(Processor delegate) {
> this.delegate = delegate;
> }
> @Override
> public void process(Exchange exchange) throws Exception {
> // Get the existing traceparent header from the Exchange
> String traceparent = exchange.getIn().getHeader("traceparent",
> String.class);
> if (traceparent != null && !traceparent.isEmpty()) {
> // Extract the traceId, parentSpanId and sampleFlag
> String[] parts = traceparent.split("-");
> String traceId = parts[1];
> String parentSpanId = parts[2];
> boolean isSampled = parts[3].equals("01");
> // Create the parent SpanContext
> SpanContext parentContext = SpanContext.create(
> traceId,
> parentSpanId,
> isSampled ? TraceFlags.getSampled() : TraceFlags.getDefault(),
> TraceState.getDefault()
> );
> // Attach the parent SpanContext to the current Context
> try (Scope scope =
> Context.current().with(Span.wrap(parentContext)).makeCurrent()) {
> // Now, the current Context has the parent SpanContext
> attached,
> // and any new spans created within this scope will use it as
> their parent
>
> // Pass control to the delegate processor
> delegate.process(exchange);
> }
> } else {
> // If no traceparent header is found, just delegate without
> modifying the Context
> delegate.process(exchange);
> }
> }
> } {code}
> Inside OpenTelemetry Agent, they dropped support of Camel 3.x+, because Camel
> provides its module for tracing, and they will not help with it.
> [Link|https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/4052]
> I wonder if that can be done inside Camel to propagate context from the
> processor implicitly without manual propagation of context.
> *UPD1:* I have verified that these behaviour is consistent across Camel
> 3.20.5, 3.20.6, 3.21.0 and 4.0.0-RC1
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20776) Camel-kinesis: Listing shard before every record request will increase extra latency
[ https://issues.apache.org/jira/browse/CAMEL-20776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851612#comment-17851612 ] Claus Ibsen commented on CAMEL-20776: - Did you send a PR ? > Camel-kinesis: Listing shard before every record request will increase extra > latency > > > Key: CAMEL-20776 > URL: https://issues.apache.org/jira/browse/CAMEL-20776 > Project: Camel > Issue Type: Improvement > Components: camel-aws2-kinesis >Reporter: Fan Yang >Priority: Minor > > Each time when camel kinesis connector requests records, it gets shard list > first. This will increase E2E latency for each message. In most scenario, > shard list won't change frequently. So, it's unnecessary to get shar list > before every data request. We can start a thread to monitor the shard change. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20776) Camel-kinesis: Listing shard before every record request will increase extra latency
[ https://issues.apache.org/jira/browse/CAMEL-20776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20776: Fix Version/s: 4.x > Camel-kinesis: Listing shard before every record request will increase extra > latency > > > Key: CAMEL-20776 > URL: https://issues.apache.org/jira/browse/CAMEL-20776 > Project: Camel > Issue Type: Improvement > Components: camel-aws2-kinesis >Reporter: Fan Yang >Priority: Minor > Fix For: 4.x > > > Each time when camel kinesis connector requests records, it gets shard list > first. This will increase E2E latency for each message. In most scenario, > shard list won't change frequently. So, it's unnecessary to get shar list > before every data request. We can start a thread to monitor the shard change. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20722) camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs
[ https://issues.apache.org/jira/browse/CAMEL-20722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851611#comment-17851611 ] Claus Ibsen commented on CAMEL-20722: - Thanks [~jvsingh] for all the help with the camel-kafka :) > camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs > --- > > Key: CAMEL-20722 > URL: https://issues.apache.org/jira/browse/CAMEL-20722 > Project: Camel > Issue Type: Task > Components: camel-kafka >Affects Versions: 4.4.1, 4.5.0 >Reporter: Otavio Rodolfo Piske >Assignee: Jang-Vijay Singh >Priority: Major > Labels: help-wanted > Fix For: 4.x > > Attachments: build-log.txt > > > All the tests named KafkaBreakOnFirst.*IT are unreliable when running on the > CI. They fail often, sometimes in multiple archs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18962) camel-as2 - AS2Consumer always accepts unencrpted/unsigned data
[ https://issues.apache.org/jira/browse/CAMEL-18962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-18962: --- Assignee: Jono Morris > camel-as2 - AS2Consumer always accepts unencrpted/unsigned data > --- > > Key: CAMEL-18962 > URL: https://issues.apache.org/jira/browse/CAMEL-18962 > Project: Camel > Issue Type: Improvement > Components: camel-as2 >Reporter: dennis lucero >Assignee: Jono Morris >Priority: Minor > > When setting up an AS2Cosumer (server) security is important. Thus in mind > AS2 should use encryption and signing to verify the incoming data before > processing it (or supplying the message for further processing). That assures > that the originator of the data is a trusted party. > Camel AS2 consumer accepts encrypted and signed data and at least decryption > is working. > *Problem* > The problem is that the consumer also accepts unencrypted data. So even if I > only want to receive encrpyted data from a trusted party, some third party > disguised as the trused party, could send a malicious unencrypted payload > and the server would just accept and process it. > For example sending plain data with the content type "application/edifact" is > always accepted. > *Possible solution* > The consumer should be configurable what content type is allowed. Also the > already existing producer-parameter "as2MessageStructure" may be used for > that purpose. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18962) camel-as2 - AS2Consumer always accepts unencrpted/unsigned data
[ https://issues.apache.org/jira/browse/CAMEL-18962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18962: Fix Version/s: 4.7.0 > camel-as2 - AS2Consumer always accepts unencrpted/unsigned data > --- > > Key: CAMEL-18962 > URL: https://issues.apache.org/jira/browse/CAMEL-18962 > Project: Camel > Issue Type: Improvement > Components: camel-as2 >Reporter: dennis lucero >Assignee: Jono Morris >Priority: Minor > Fix For: 4.7.0 > > > When setting up an AS2Cosumer (server) security is important. Thus in mind > AS2 should use encryption and signing to verify the incoming data before > processing it (or supplying the message for further processing). That assures > that the originator of the data is a trusted party. > Camel AS2 consumer accepts encrypted and signed data and at least decryption > is working. > *Problem* > The problem is that the consumer also accepts unencrypted data. So even if I > only want to receive encrpyted data from a trusted party, some third party > disguised as the trused party, could send a malicious unencrypted payload > and the server would just accept and process it. > For example sending plain data with the content type "application/edifact" is > always accepted. > *Possible solution* > The consumer should be configurable what content type is allowed. Also the > already existing producer-parameter "as2MessageStructure" may be used for > that purpose. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20827) Add endpoint service location to aws, azure and google componentd
Claus Ibsen created CAMEL-20827: --- Summary: Add endpoint service location to aws, azure and google componentd Key: CAMEL-20827 URL: https://issues.apache.org/jira/browse/CAMEL-20827 Project: Camel Issue Type: New Feature Reporter: Claus Ibsen Assignee: Andrea Cosentino Fix For: 4.7.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20798) camel-tracing - Add servername to more decorators
[ https://issues.apache.org/jira/browse/CAMEL-20798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20798. - Resolution: Fixed Created ticket for cloud components > camel-tracing - Add servername to more decorators > - > > Key: CAMEL-20798 > URL: https://issues.apache.org/jira/browse/CAMEL-20798 > Project: Camel > Issue Type: Improvement > Components: camel-tracing >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.7.0 > > > There is a tag for SERVER_ADDRESS which we can enrich for more of the > decorators. > > Some like JMS is harder as the JMS broker is configured specific such as > ActiveMQ has the brokerURL on the activemq class. > Kafka has boostrapServers etc. > We may add some SPI interface that a component can implemented, and then we > can call it via an endpoint, and then we can use the logic in the component > to return the server address. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18546) camel-core - HostedService - To mark a consumer as a Camel hosted service
[ https://issues.apache.org/jira/browse/CAMEL-18546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18546. - Resolution: Fixed > camel-core - HostedService - To mark a consumer as a Camel hosted service > - > > Key: CAMEL-18546 > URL: https://issues.apache.org/jira/browse/CAMEL-18546 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.7.0 > > > A few components hosts a service exclusive in Camel such as HTTP/TCP based > from cxf > from platform-http > from servlet > from netty (not in client mode) > from mina > from mllp > from jetty > There may be a few others. > Its not the same as > from file > from jms > from kafka > As these are camel consumer that reacts on events from another "service", eg > JMS broker or Kafka broker. > If we have an API/SPI to mark a consumer as being a HostedConsumer (or come > up with a better name). Then we can collect service information, such as > - name > - protocol > - ur to call the service > - additional metadata > - api schema (optional) > Then we can make camel-core able to detect all its consumers that are hosted, > and be able to expose this so its easier for tooling etc to gather a list of > services. > There is something related to this in RestRegistry in camel-core but that was > for RESTful hosted service only. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18546) camel-core - HostedService - To mark a consumer as a Camel hosted service
[ https://issues.apache.org/jira/browse/CAMEL-18546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849998#comment-17849998 ] Claus Ibsen edited comment on CAMEL-18546 at 6/3/24 11:01 AM: -- TODO: Consider using ServiceRegistry API or some similar concept to have an API to lookup the services *DONE* TODO: Attach more details such as unique service ids, route ids, etc to be able to link to which routes is using what services. *DONE* was (Author: davsclaus): TODO: Consider using ServiceRegistry API or some similar concept to have an API to lookup the services *DONE* TODO: Attach more details such as unique service ids, route ids, etc to be able to link to which routes is using what services. > camel-core - HostedService - To mark a consumer as a Camel hosted service > - > > Key: CAMEL-18546 > URL: https://issues.apache.org/jira/browse/CAMEL-18546 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.7.0 > > > A few components hosts a service exclusive in Camel such as HTTP/TCP based > from cxf > from platform-http > from servlet > from netty (not in client mode) > from mina > from mllp > from jetty > There may be a few others. > Its not the same as > from file > from jms > from kafka > As these are camel consumer that reacts on events from another "service", eg > JMS broker or Kafka broker. > If we have an API/SPI to mark a consumer as being a HostedConsumer (or come > up with a better name). Then we can collect service information, such as > - name > - protocol > - ur to call the service > - additional metadata > - api schema (optional) > Then we can make camel-core able to detect all its consumers that are hosted, > and be able to expose this so its easier for tooling etc to gather a list of > services. > There is something related to this in RestRegistry in camel-core but that was > for RESTful hosted service only. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19985) camel-smooks - Add component for Smooks for EDI data mapping
[ https://issues.apache.org/jira/browse/CAMEL-19985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19985. - Resolution: Fixed > camel-smooks - Add component for Smooks for EDI data mapping > > > Key: CAMEL-19985 > URL: https://issues.apache.org/jira/browse/CAMEL-19985 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 4.7.0 > > > This project is now ASF2 licensed > https://github.com/smooks/smooks > We used to have a camel-smooks component (camel-extra) in v1 many years ago. > We should add this component again, so users can use smooks for EDI data > mapping -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20805) CamelAzureServiceBus headers missing since upgrading to camel-azure-servicebus-4.4.2
[
https://issues.apache.org/jira/browse/CAMEL-20805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20805.
-
Resolution: Duplicate
> CamelAzureServiceBus headers missing since upgrading to
> camel-azure-servicebus-4.4.2
>
>
> Key: CAMEL-20805
> URL: https://issues.apache.org/jira/browse/CAMEL-20805
> Project: Camel
> Issue Type: Bug
> Components: camel-azure
>Affects Versions: 4.4.2
> Environment: Oracle EL8
> java-latest-openjdk-22.0.1.0.8-1.rolling.el8.x86_64
> Camel 4.4.2 Embedded in ActiveMQ 6.1.2
>Reporter: JJ
>Priority: Minor
> Labels: help-wanted
>
> I have a connection to an Azure service bus queue defined in xml
> {code:xml}
>
>
>
>
>
>
> class="org.apache.camel.component.azure.servicebus.ServiceBusComponent">
>
> class="org.apache.camel.component.azure.servicebus.ServiceBusConfiguration">
>
>
> value="elexon-iris.servicebus.windows.net" />
>
>
>
> {code}
> Using camel-azure-servicebus-4.4.1 I get the following headers returned for
> each message:
> {code:java}
> {"expires"=>"0", "CamelAzureServiceBusEnqueuedSequenceNumber"=>"10655170",
> "destination"=>"/topic/IRIS-Elexon",
> "CamelAzureServiceBusDeliveryCount"=>"0",
> "ack"=>"ID:bravo-43103-1716763678894-2:59",
> "CamelAzureServiceBusSubject"=>"MELS",
> "subscription"=>"4b0062c6-48be-4cb2-abce85d1481b3401", "priority"=>"4",
> "CamelAzureServiceBusSequenceNumber"=>"7955951",
> "CamelAzureServiceBusMessageId"=>"MELS_202405262248_85602.json",
> "message-id"=>"ID:bravo-43103-1716763678894-10:1:3:1:1272",
> "persistent"=>"true", "timestamp"=>"1716763744004",
> "CamelAzureServiceBusLockToken"=>"64179600-27db-48ed-be93-eb19ebe0f66b"}{code}
>
> But when I change to camel-azure-servicebus-4.4.2 the only headers I get are:
> {code:java}
> {"expires"=>"0", "destination"=>"/topic/IRIS-Elexon",
> "ack"=>"ID:bravo-34173-1716750388709-2:15634",
> "subscription"=>"16b02d1f-40df-4f31-b538738618f91316", "priority"=>"4",
> "message-id"=>"ID:bravo-34173-1716750388709-10:1:5:1:43221",
> "persistent"=>"true", "source_file_name"=>"MELS_202405262245_85595.json",
> "timestamp"=>"1716763562372"} {code}
> How do I get the CamelAzureServiceBus headers back? I filter on those within
> a processing script so this is a rather breaking change.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20826) The camel-package-maven-plugin:generate mvn goal does not produce reproducible jandex.idx files
[
https://issues.apache.org/jira/browse/CAMEL-20826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20826.
-
Resolution: Fixed
> The camel-package-maven-plugin:generate mvn goal does not produce
> reproducible jandex.idx files
> ---
>
> Key: CAMEL-20826
> URL: https://issues.apache.org/jira/browse/CAMEL-20826
> Project: Camel
> Issue Type: Task
> Components: build system
>Reporter: Hiram R. Chirino
>Assignee: Hiram R. Chirino
>Priority: Major
> Fix For: 4.7.0
>
>
> I’m testing on two machines, (osx jdk HotSpot 22.0.1+8-16), and (linux , jdk
> Red Hat 21.0.3+9).. in the {{/camel/core/camel-util}} dir of the main branch.
> When I run:
> {{mvn clean process-classes && sha256sum target/classes/META-INF/jandex.idx}}
> on both I get different sha signatures. But if I run something that should
> be equivalent:
> {{mvn clean compile io.smallrye:jandex-maven-plugin:3.1.7:jandex && sha256sum
> target/classes/META-INF/jandex.idx}}
> then I get the same sha.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20826) The camel-package-maven-plugin:generate mvn goal does not produce reproducible jandex.idx files
[
https://issues.apache.org/jira/browse/CAMEL-20826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20826:
Issue Type: Task (was: New Feature)
> The camel-package-maven-plugin:generate mvn goal does not produce
> reproducible jandex.idx files
> ---
>
> Key: CAMEL-20826
> URL: https://issues.apache.org/jira/browse/CAMEL-20826
> Project: Camel
> Issue Type: Task
> Components: build system
>Reporter: Hiram R. Chirino
>Assignee: Hiram R. Chirino
>Priority: Major
> Fix For: 4.7.0
>
>
> I’m testing on two machines, (osx jdk HotSpot 22.0.1+8-16), and (linux , jdk
> Red Hat 21.0.3+9).. in the {{/camel/core/camel-util}} dir of the main branch.
> When I run:
> {{mvn clean process-classes && sha256sum target/classes/META-INF/jandex.idx}}
> on both I get different sha signatures. But if I run something that should
> be equivalent:
> {{mvn clean compile io.smallrye:jandex-maven-plugin:3.1.7:jandex && sha256sum
> target/classes/META-INF/jandex.idx}}
> then I get the same sha.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20826) The camel-package-maven-plugin:generate mvn goal does not produce reproducible jandex.idx files
[
https://issues.apache.org/jira/browse/CAMEL-20826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20826:
Component/s: build system
> The camel-package-maven-plugin:generate mvn goal does not produce
> reproducible jandex.idx files
> ---
>
> Key: CAMEL-20826
> URL: https://issues.apache.org/jira/browse/CAMEL-20826
> Project: Camel
> Issue Type: New Feature
> Components: build system
>Reporter: Hiram R. Chirino
>Priority: Major
> Fix For: 4.7.0
>
>
> I’m testing on two machines, (osx jdk HotSpot 22.0.1+8-16), and (linux , jdk
> Red Hat 21.0.3+9).. in the {{/camel/core/camel-util}} dir of the main branch.
> When I run:
> {{mvn clean process-classes && sha256sum target/classes/META-INF/jandex.idx}}
> on both I get different sha signatures. But if I run something that should
> be equivalent:
> {{mvn clean compile io.smallrye:jandex-maven-plugin:3.1.7:jandex && sha256sum
> target/classes/META-INF/jandex.idx}}
> then I get the same sha.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20826) The camel-package-maven-plugin:generate mvn goal does not produce reproducible jandex.idx files
[
https://issues.apache.org/jira/browse/CAMEL-20826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20826:
Fix Version/s: 4.7.0
> The camel-package-maven-plugin:generate mvn goal does not produce
> reproducible jandex.idx files
> ---
>
> Key: CAMEL-20826
> URL: https://issues.apache.org/jira/browse/CAMEL-20826
> Project: Camel
> Issue Type: New Feature
>Reporter: Hiram R. Chirino
>Priority: Major
> Fix For: 4.7.0
>
>
> I’m testing on two machines, (osx jdk HotSpot 22.0.1+8-16), and (linux , jdk
> Red Hat 21.0.3+9).. in the {{/camel/core/camel-util}} dir of the main branch.
> When I run:
> {{mvn clean process-classes && sha256sum target/classes/META-INF/jandex.idx}}
> on both I get different sha signatures. But if I run something that should
> be equivalent:
> {{mvn clean compile io.smallrye:jandex-maven-plugin:3.1.7:jandex && sha256sum
> target/classes/META-INF/jandex.idx}}
> then I get the same sha.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20826) The camel-package-maven-plugin:generate mvn goal does not produce reproducible jandex.idx files
[
https://issues.apache.org/jira/browse/CAMEL-20826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-20826:
---
Assignee: Hiram R. Chirino
> The camel-package-maven-plugin:generate mvn goal does not produce
> reproducible jandex.idx files
> ---
>
> Key: CAMEL-20826
> URL: https://issues.apache.org/jira/browse/CAMEL-20826
> Project: Camel
> Issue Type: New Feature
> Components: build system
>Reporter: Hiram R. Chirino
>Assignee: Hiram R. Chirino
>Priority: Major
> Fix For: 4.7.0
>
>
> I’m testing on two machines, (osx jdk HotSpot 22.0.1+8-16), and (linux , jdk
> Red Hat 21.0.3+9).. in the {{/camel/core/camel-util}} dir of the main branch.
> When I run:
> {{mvn clean process-classes && sha256sum target/classes/META-INF/jandex.idx}}
> on both I get different sha signatures. But if I run something that should
> be equivalent:
> {{mvn clean compile io.smallrye:jandex-maven-plugin:3.1.7:jandex && sha256sum
> target/classes/META-INF/jandex.idx}}
> then I get the same sha.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20812) camel-netty-http: hostnameVerification option not used
[
https://issues.apache.org/jira/browse/CAMEL-20812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20812.
-
Resolution: Fixed
> camel-netty-http: hostnameVerification option not used
> --
>
> Key: CAMEL-20812
> URL: https://issues.apache.org/jira/browse/CAMEL-20812
> Project: Camel
> Issue Type: Bug
> Components: camel-netty-http
> Environment: Camel 3.x
> Java 11
>Reporter: Björn Pettersson
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.4.3, 4.7.0
>
>
> I was trying to set query parameter hostnameVerification=true, in netty-http
> component, but it would not take effect.
> After some fault-finding it turns out that the implementation of
> hostnameVerification is in DefaultClientInitializerFactory (which is used by
> default in the netty component). However, in the netty-http component,
> HttpClientInitializerFactory is used by default, which does not use the
> hostnameVerification option.
> A workaround solution was to override HttpClientInitializerFactory:
> {code:java}
> public class HttpsClientInitializerFactory extends
> HttpClientInitializerFactory {
> [constructors removed]
> @Override
> protected void initChannel(Channel ch) throws Exception {
> super.initChannel(ch);
> if (configuration.isHostnameVerification()) {
> ChannelHandler handler = ch.pipeline().get("ssl");
> SSLEngine engine = ((SslHandler)handler).engine();
> SSLParameters sslParams = engine.getSSLParameters();
> sslParams.setEndpointIdentificationAlgorithm("HTTPS");
> engine.setSSLParameters(sslParams);
> }
> }
> }{code}
> The hostnameVerification option is documented in both netty and netty-http
> components and it seems odd that it would require a custom
> ClientInitializerFactory.
> A possible solution would be to re-use the implementation from
> DefaultClientInitializerFactory in HttpClientInitializerFactory.
> Only tested in Camel 3.x but dont see any changes affecting this since
> implementation in CAMEL-16315
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20805) CamelAzureServiceBus headers missing since upgrading to camel-azure-servicebus-4.4.2
[
https://issues.apache.org/jira/browse/CAMEL-20805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20805:
Priority: Minor (was: Blocker)
> CamelAzureServiceBus headers missing since upgrading to
> camel-azure-servicebus-4.4.2
>
>
> Key: CAMEL-20805
> URL: https://issues.apache.org/jira/browse/CAMEL-20805
> Project: Camel
> Issue Type: Bug
> Components: camel-azure
>Affects Versions: 4.4.2
> Environment: Oracle EL8
> java-latest-openjdk-22.0.1.0.8-1.rolling.el8.x86_64
> Camel 4.4.2 Embedded in ActiveMQ 6.1.2
>Reporter: JJ
>Priority: Minor
> Labels: help-wanted
>
> I have a connection to an Azure service bus queue defined in xml
> {code:xml}
>
>
>
>
>
>
> class="org.apache.camel.component.azure.servicebus.ServiceBusComponent">
>
> class="org.apache.camel.component.azure.servicebus.ServiceBusConfiguration">
>
>
> value="elexon-iris.servicebus.windows.net" />
>
>
>
> {code}
> Using camel-azure-servicebus-4.4.1 I get the following headers returned for
> each message:
> {code:java}
> {"expires"=>"0", "CamelAzureServiceBusEnqueuedSequenceNumber"=>"10655170",
> "destination"=>"/topic/IRIS-Elexon",
> "CamelAzureServiceBusDeliveryCount"=>"0",
> "ack"=>"ID:bravo-43103-1716763678894-2:59",
> "CamelAzureServiceBusSubject"=>"MELS",
> "subscription"=>"4b0062c6-48be-4cb2-abce85d1481b3401", "priority"=>"4",
> "CamelAzureServiceBusSequenceNumber"=>"7955951",
> "CamelAzureServiceBusMessageId"=>"MELS_202405262248_85602.json",
> "message-id"=>"ID:bravo-43103-1716763678894-10:1:3:1:1272",
> "persistent"=>"true", "timestamp"=>"1716763744004",
> "CamelAzureServiceBusLockToken"=>"64179600-27db-48ed-be93-eb19ebe0f66b"}{code}
>
> But when I change to camel-azure-servicebus-4.4.2 the only headers I get are:
> {code:java}
> {"expires"=>"0", "destination"=>"/topic/IRIS-Elexon",
> "ack"=>"ID:bravo-34173-1716750388709-2:15634",
> "subscription"=>"16b02d1f-40df-4f31-b538738618f91316", "priority"=>"4",
> "message-id"=>"ID:bravo-34173-1716750388709-10:1:5:1:43221",
> "persistent"=>"true", "source_file_name"=>"MELS_202405262245_85595.json",
> "timestamp"=>"1716763562372"} {code}
> How do I get the CamelAzureServiceBus headers back? I filter on those within
> a processing script so this is a rather breaking change.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20781) camel-spring-boot - Upgrade to SB 3.1.12
[ https://issues.apache.org/jira/browse/CAMEL-20781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20781. - Resolution: Fixed > camel-spring-boot - Upgrade to SB 3.1.12 > > > Key: CAMEL-20781 > URL: https://issues.apache.org/jira/browse/CAMEL-20781 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0.6 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20781) camel-spring-boot - Upgrade to SB 3.1.12
[ https://issues.apache.org/jira/browse/CAMEL-20781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20781: --- Assignee: Claus Ibsen > camel-spring-boot - Upgrade to SB 3.1.12 > > > Key: CAMEL-20781 > URL: https://issues.apache.org/jira/browse/CAMEL-20781 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0.6 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20780) camel-spring-boot - Upgrade to SB 3.2.6
[ https://issues.apache.org/jira/browse/CAMEL-20780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20780. - Resolution: Fixed > camel-spring-boot - Upgrade to SB 3.2.6 > --- > > Key: CAMEL-20780 > URL: https://issues.apache.org/jira/browse/CAMEL-20780 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.4.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20780) camel-spring-boot - Upgrade to SB 3.2.6
[ https://issues.apache.org/jira/browse/CAMEL-20780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20780: --- Assignee: Claus Ibsen > camel-spring-boot - Upgrade to SB 3.2.6 > --- > > Key: CAMEL-20780 > URL: https://issues.apache.org/jira/browse/CAMEL-20780 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.4.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20819) camel-jbang - Reload mode with supervising route controller does not reload routes
[ https://issues.apache.org/jira/browse/CAMEL-20819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20819: Fix Version/s: 4.4.3 > camel-jbang - Reload mode with supervising route controller does not reload > routes > -- > > Key: CAMEL-20819 > URL: https://issues.apache.org/jira/browse/CAMEL-20819 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 4.6.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.4.3, 4.7.0 > > > camel-kamelets-examples/jbang/hello-yaml main❯ camel run hello.camel.yaml > --dev --prop=camel.routecontroller.enabled=true > > Does not reload route on change due to using supervised -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20820) camel-core - Duplicate JMX MBean operation for resource endpoints
[ https://issues.apache.org/jira/browse/CAMEL-20820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20820: Fix Version/s: 4.4.3 > camel-core - Duplicate JMX MBean operation for resource endpoints > - > > Key: CAMEL-20820 > URL: https://issues.apache.org/jira/browse/CAMEL-20820 > Project: Camel > Issue Type: Bug > Components: camel-core, jmx >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.4.3, 4.7.0 > > > Reported on user mailing list -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20812) camel-netty-http: hostnameVerification option not used
[
https://issues.apache.org/jira/browse/CAMEL-20812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20812:
Fix Version/s: 4.4.3
> camel-netty-http: hostnameVerification option not used
> --
>
> Key: CAMEL-20812
> URL: https://issues.apache.org/jira/browse/CAMEL-20812
> Project: Camel
> Issue Type: Bug
> Components: camel-netty-http
> Environment: Camel 3.x
> Java 11
>Reporter: Björn Pettersson
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.4.3, 4.7.0
>
>
> I was trying to set query parameter hostnameVerification=true, in netty-http
> component, but it would not take effect.
> After some fault-finding it turns out that the implementation of
> hostnameVerification is in DefaultClientInitializerFactory (which is used by
> default in the netty component). However, in the netty-http component,
> HttpClientInitializerFactory is used by default, which does not use the
> hostnameVerification option.
> A workaround solution was to override HttpClientInitializerFactory:
> {code:java}
> public class HttpsClientInitializerFactory extends
> HttpClientInitializerFactory {
> [constructors removed]
> @Override
> protected void initChannel(Channel ch) throws Exception {
> super.initChannel(ch);
> if (configuration.isHostnameVerification()) {
> ChannelHandler handler = ch.pipeline().get("ssl");
> SSLEngine engine = ((SslHandler)handler).engine();
> SSLParameters sslParams = engine.getSSLParameters();
> sslParams.setEndpointIdentificationAlgorithm("HTTPS");
> engine.setSSLParameters(sslParams);
> }
> }
> }{code}
> The hostnameVerification option is documented in both netty and netty-http
> components and it seems odd that it would require a custom
> ClientInitializerFactory.
> A possible solution would be to re-use the implementation from
> DefaultClientInitializerFactory in HttpClientInitializerFactory.
> Only tested in Camel 3.x but dont see any changes affecting this since
> implementation in CAMEL-16315
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20825) camel-rest - Contract first for api-doc should include the spec
[
https://issues.apache.org/jira/browse/CAMEL-20825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20825.
-
Resolution: Fixed
This was not implemented before
> camel-rest - Contract first for api-doc should include the spec
> ---
>
> Key: CAMEL-20825
> URL: https://issues.apache.org/jira/browse/CAMEL-20825
> Project: Camel
> Issue Type: Improvement
> Components: camel-rest-openapi
>Affects Versions: 4.6.0
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.7.0
>
>
> It returns an empty path sections
> {code:java}
> {openapi: "3.0.0",info: { },servers: [{url: "http://0.0.0.0"}],paths: { }}
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20825) camel-rest - Contract first for api-doc should include the spec
[
https://issues.apache.org/jira/browse/CAMEL-20825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20825:
Issue Type: Improvement (was: Bug)
> camel-rest - Contract first for api-doc should include the spec
> ---
>
> Key: CAMEL-20825
> URL: https://issues.apache.org/jira/browse/CAMEL-20825
> Project: Camel
> Issue Type: Improvement
> Components: camel-rest-openapi
>Affects Versions: 4.6.0
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.7.0
>
>
> It returns an empty path sections
> {code:java}
> {openapi: "3.0.0",info: { },servers: [{url: "http://0.0.0.0"}],paths: { }}
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20825) camel-rest - Contract first for api-doc should include the spec
[
https://issues.apache.org/jira/browse/CAMEL-20825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20825:
Issue Type: New Feature (was: Improvement)
> camel-rest - Contract first for api-doc should include the spec
> ---
>
> Key: CAMEL-20825
> URL: https://issues.apache.org/jira/browse/CAMEL-20825
> Project: Camel
> Issue Type: New Feature
> Components: camel-rest-openapi
>Affects Versions: 4.6.0
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.7.0
>
>
> It returns an empty path sections
> {code:java}
> {openapi: "3.0.0",info: { },servers: [{url: "http://0.0.0.0"}],paths: { }}
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20825) camel-rest - Contract first for api-doc should include the spec
Claus Ibsen created CAMEL-20825:
---
Summary: camel-rest - Contract first for api-doc should include
the spec
Key: CAMEL-20825
URL: https://issues.apache.org/jira/browse/CAMEL-20825
Project: Camel
Issue Type: Bug
Components: camel-rest-openapi
Affects Versions: 4.6.0
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 4.7.0
It returns an empty path sections
{code:java}
{openapi: "3.0.0",info: { },servers: [{url: "http://0.0.0.0"}],paths: { }}
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20824) camel-core - Backlog tracer should include internal exchange properties
[ https://issues.apache.org/jira/browse/CAMEL-20824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20824. - Resolution: Fixed > camel-core - Backlog tracer should include internal exchange properties > --- > > Key: CAMEL-20824 > URL: https://issues.apache.org/jira/browse/CAMEL-20824 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.7.0 > > > This helps during debugging as you can see internal details such as batch > sizes and whatnot -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20824) camel-core - Backlog tracer should include internal exchange properties
Claus Ibsen created CAMEL-20824: --- Summary: camel-core - Backlog tracer should include internal exchange properties Key: CAMEL-20824 URL: https://issues.apache.org/jira/browse/CAMEL-20824 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 4.7.0 This helps during debugging as you can see internal details such as batch sizes and whatnot -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20823) camel-smb component polling doesn't account for directories
[
https://issues.apache.org/jira/browse/CAMEL-20823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20823.
-
Resolution: Fixed
> camel-smb component polling doesn't account for directories
> ---
>
> Key: CAMEL-20823
> URL: https://issues.apache.org/jira/browse/CAMEL-20823
> Project: Camel
> Issue Type: Bug
>Reporter: Thomas Cunningham
>Assignee: Thomas Cunningham
>Priority: Major
> Fix For: 4.7.0
>
>
> Getting the following error polling an SMB share that contains directories -
> I think we can do a check for folders and filter them out.
> {code:java}
> 2024-05-31T14:11:47.357-04:00 WARN 70410 --- [68.1.35:445/src]
> o.a.camel.component.smb.SmbConsumer : Failed polling endpoint:
> smb://192.168.1.35:445/src?password=xx=xx. Will try again at
> next poll. Caused by: [com.hierynomus.mssmb2.SMBApiException -
> STATUS_FILE_IS_A_DIRECTORY (0xc0ba): Create failed for
> \\192.168.1.35\src\System Volume Information]
> com.hierynomus.mssmb2.SMBApiException: STATUS_FILE_IS_A_DIRECTORY
> (0xc0ba): Create failed for \\192.168.1.35\src\System Volume Information
> at com.hierynomus.smbj.share.Share.receive(Share.java:380)
> ~[smbj-0.13.0.jar:0.13.0]at
> com.hierynomus.smbj.share.Share.sendReceive(Share.java:359)
> ~[smbj-0.13.0.jar:0.13.0]at
> com.hierynomus.smbj.share.Share.createFile(Share.java:156)
> ~[smbj-0.13.0.jar:0.13.0] at
> com.hierynomus.smbj.share.DiskShare.createFileAndResolve(DiskShare.java:75)
> ~[smbj-0.13.0.jar:0.13.0]at
> com.hierynomus.smbj.share.DiskShare.access$100(DiskShare.java:55)
> ~[smbj-0.13.0.jar:0.13.0] at
> com.hierynomus.smbj.share.DiskShare$2.apply(DiskShare.java:109)
> ~[smbj-0.13.0.jar:0.13.0]at
> com.hierynomus.smbj.share.DiskShare$2.apply(DiskShare.java:105)
> ~[smbj-0.13.0.jar:0.13.0]at
> com.hierynomus.smbj.paths.PathResolver$1.resolve(PathResolver.java:32)
> ~[smbj-0.13.0.jar:0.13.0] at
> com.hierynomus.smbj.paths.SymlinkPathResolver.resolve(SymlinkPathResolver.java:62)
> ~[smbj-0.13.0.jar:0.13.0] at
> com.hierynomus.smbj.share.DiskShare.resolveAndCreateFile(DiskShare.java:105)
> ~[smbj-0.13.0.jar:0.13.0] at
> com.hierynomus.smbj.share.DiskShare.open(DiskShare.java:65)
> ~[smbj-0.13.0.jar:0.13.0]at
> com.hierynomus.smbj.share.DiskShare.openFile(DiskShare.java:169)
> ~[smbj-0.13.0.jar:0.13.0] at
> org.apache.camel.component.smb.SmbConsumer.poll(SmbConsumer.java:75)
> ~[camel-smb-4.7.0-SNAPSHOT.jar:4.7.0-SNAPSHOT] at
> org.apache.camel.support.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:205)
> ~[camel-support-4.7.0-SNAPSHOT.jar:4.7.0-SNAPSHOT] at
> org.apache.camel.support.ScheduledPollConsumer.run(ScheduledPollConsumer.java:119)
> ~[camel-support-4.7.0-SNAPSHOT.jar:4.7.0-SNAPSHOT]at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
> ~[na:na] at
> java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:358)
> ~[na:na] at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
> ~[na:na]at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
> ~[na:na] at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
> ~[na:na] at java.base/java.lang.Thread.run(Thread.java:1583) ~[na:na]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20823) camel-smb component polling doesn't account for directories
[
https://issues.apache.org/jira/browse/CAMEL-20823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20823:
Fix Version/s: 4.7.0
> camel-smb component polling doesn't account for directories
> ---
>
> Key: CAMEL-20823
> URL: https://issues.apache.org/jira/browse/CAMEL-20823
> Project: Camel
> Issue Type: Bug
>Reporter: Thomas Cunningham
>Assignee: Thomas Cunningham
>Priority: Major
> Fix For: 4.7.0
>
>
> Getting the following error polling an SMB share that contains directories -
> I think we can do a check for folders and filter them out.
> {code:java}
> 2024-05-31T14:11:47.357-04:00 WARN 70410 --- [68.1.35:445/src]
> o.a.camel.component.smb.SmbConsumer : Failed polling endpoint:
> smb://192.168.1.35:445/src?password=xx=xx. Will try again at
> next poll. Caused by: [com.hierynomus.mssmb2.SMBApiException -
> STATUS_FILE_IS_A_DIRECTORY (0xc0ba): Create failed for
> \\192.168.1.35\src\System Volume Information]
> com.hierynomus.mssmb2.SMBApiException: STATUS_FILE_IS_A_DIRECTORY
> (0xc0ba): Create failed for \\192.168.1.35\src\System Volume Information
> at com.hierynomus.smbj.share.Share.receive(Share.java:380)
> ~[smbj-0.13.0.jar:0.13.0]at
> com.hierynomus.smbj.share.Share.sendReceive(Share.java:359)
> ~[smbj-0.13.0.jar:0.13.0]at
> com.hierynomus.smbj.share.Share.createFile(Share.java:156)
> ~[smbj-0.13.0.jar:0.13.0] at
> com.hierynomus.smbj.share.DiskShare.createFileAndResolve(DiskShare.java:75)
> ~[smbj-0.13.0.jar:0.13.0]at
> com.hierynomus.smbj.share.DiskShare.access$100(DiskShare.java:55)
> ~[smbj-0.13.0.jar:0.13.0] at
> com.hierynomus.smbj.share.DiskShare$2.apply(DiskShare.java:109)
> ~[smbj-0.13.0.jar:0.13.0]at
> com.hierynomus.smbj.share.DiskShare$2.apply(DiskShare.java:105)
> ~[smbj-0.13.0.jar:0.13.0]at
> com.hierynomus.smbj.paths.PathResolver$1.resolve(PathResolver.java:32)
> ~[smbj-0.13.0.jar:0.13.0] at
> com.hierynomus.smbj.paths.SymlinkPathResolver.resolve(SymlinkPathResolver.java:62)
> ~[smbj-0.13.0.jar:0.13.0] at
> com.hierynomus.smbj.share.DiskShare.resolveAndCreateFile(DiskShare.java:105)
> ~[smbj-0.13.0.jar:0.13.0] at
> com.hierynomus.smbj.share.DiskShare.open(DiskShare.java:65)
> ~[smbj-0.13.0.jar:0.13.0]at
> com.hierynomus.smbj.share.DiskShare.openFile(DiskShare.java:169)
> ~[smbj-0.13.0.jar:0.13.0] at
> org.apache.camel.component.smb.SmbConsumer.poll(SmbConsumer.java:75)
> ~[camel-smb-4.7.0-SNAPSHOT.jar:4.7.0-SNAPSHOT] at
> org.apache.camel.support.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:205)
> ~[camel-support-4.7.0-SNAPSHOT.jar:4.7.0-SNAPSHOT] at
> org.apache.camel.support.ScheduledPollConsumer.run(ScheduledPollConsumer.java:119)
> ~[camel-support-4.7.0-SNAPSHOT.jar:4.7.0-SNAPSHOT]at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
> ~[na:na] at
> java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:358)
> ~[na:na] at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
> ~[na:na]at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
> ~[na:na] at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
> ~[na:na] at java.base/java.lang.Thread.run(Thread.java:1583) ~[na:na]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20822) camel-langchain4j-chat - implement tool capabilities
[
https://issues.apache.org/jira/browse/CAMEL-20822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20822:
Fix Version/s: 4.7.0
> camel-langchain4j-chat - implement tool capabilities
>
>
> Key: CAMEL-20822
> URL: https://issues.apache.org/jira/browse/CAMEL-20822
> Project: Camel
> Issue Type: New Feature
> Components: camel-ai
>Reporter: Federico Mariani
>Assignee: Federico Mariani
>Priority: Major
> Fix For: 4.7.0
>
>
> Implement OpenAI Tool capabilities, so that camel consumer route can be used
> as Tool logic ala:
> {code:java}
> from("langchain4j-chat:chatId").to("sql:SELECT name FROM users WHERE id =
> :#id") {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20812) camel-netty-http: hostnameVerification option not used
[
https://issues.apache.org/jira/browse/CAMEL-20812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851095#comment-17851095
]
Claus Ibsen commented on CAMEL-20812:
-
You are welcome to take a look at this PR
https://github.com/apache/camel/pull/14294
> camel-netty-http: hostnameVerification option not used
> --
>
> Key: CAMEL-20812
> URL: https://issues.apache.org/jira/browse/CAMEL-20812
> Project: Camel
> Issue Type: Bug
> Components: camel-netty-http
> Environment: Camel 3.x
> Java 11
>Reporter: Björn Pettersson
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.7.0
>
>
> I was trying to set query parameter hostnameVerification=true, in netty-http
> component, but it would not take effect.
> After some fault-finding it turns out that the implementation of
> hostnameVerification is in DefaultClientInitializerFactory (which is used by
> default in the netty component). However, in the netty-http component,
> HttpClientInitializerFactory is used by default, which does not use the
> hostnameVerification option.
> A workaround solution was to override HttpClientInitializerFactory:
> {code:java}
> public class HttpsClientInitializerFactory extends
> HttpClientInitializerFactory {
> [constructors removed]
> @Override
> protected void initChannel(Channel ch) throws Exception {
> super.initChannel(ch);
> if (configuration.isHostnameVerification()) {
> ChannelHandler handler = ch.pipeline().get("ssl");
> SSLEngine engine = ((SslHandler)handler).engine();
> SSLParameters sslParams = engine.getSSLParameters();
> sslParams.setEndpointIdentificationAlgorithm("HTTPS");
> engine.setSSLParameters(sslParams);
> }
> }
> }{code}
> The hostnameVerification option is documented in both netty and netty-http
> components and it seems odd that it would require a custom
> ClientInitializerFactory.
> A possible solution would be to re-use the implementation from
> DefaultClientInitializerFactory in HttpClientInitializerFactory.
> Only tested in Camel 3.x but dont see any changes affecting this since
> implementation in CAMEL-16315
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20812) camel-netty-http: hostnameVerification option not used
[
https://issues.apache.org/jira/browse/CAMEL-20812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-20812:
---
Assignee: Claus Ibsen
> camel-netty-http: hostnameVerification option not used
> --
>
> Key: CAMEL-20812
> URL: https://issues.apache.org/jira/browse/CAMEL-20812
> Project: Camel
> Issue Type: Bug
> Components: camel-netty-http
> Environment: Camel 3.x
> Java 11
>Reporter: Björn Pettersson
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.7.0
>
>
> I was trying to set query parameter hostnameVerification=true, in netty-http
> component, but it would not take effect.
> After some fault-finding it turns out that the implementation of
> hostnameVerification is in DefaultClientInitializerFactory (which is used by
> default in the netty component). However, in the netty-http component,
> HttpClientInitializerFactory is used by default, which does not use the
> hostnameVerification option.
> A workaround solution was to override HttpClientInitializerFactory:
> {code:java}
> public class HttpsClientInitializerFactory extends
> HttpClientInitializerFactory {
> [constructors removed]
> @Override
> protected void initChannel(Channel ch) throws Exception {
> super.initChannel(ch);
> if (configuration.isHostnameVerification()) {
> ChannelHandler handler = ch.pipeline().get("ssl");
> SSLEngine engine = ((SslHandler)handler).engine();
> SSLParameters sslParams = engine.getSSLParameters();
> sslParams.setEndpointIdentificationAlgorithm("HTTPS");
> engine.setSSLParameters(sslParams);
> }
> }
> }{code}
> The hostnameVerification option is documented in both netty and netty-http
> components and it seems odd that it would require a custom
> ClientInitializerFactory.
> A possible solution would be to re-use the implementation from
> DefaultClientInitializerFactory in HttpClientInitializerFactory.
> Only tested in Camel 3.x but dont see any changes affecting this since
> implementation in CAMEL-16315
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20812) camel-netty-http: hostnameVerification option not used
[
https://issues.apache.org/jira/browse/CAMEL-20812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20812:
Fix Version/s: 4.7.0
(was: 4.x)
> camel-netty-http: hostnameVerification option not used
> --
>
> Key: CAMEL-20812
> URL: https://issues.apache.org/jira/browse/CAMEL-20812
> Project: Camel
> Issue Type: Bug
> Components: camel-netty-http
> Environment: Camel 3.x
> Java 11
>Reporter: Björn Pettersson
>Priority: Minor
> Fix For: 4.7.0
>
>
> I was trying to set query parameter hostnameVerification=true, in netty-http
> component, but it would not take effect.
> After some fault-finding it turns out that the implementation of
> hostnameVerification is in DefaultClientInitializerFactory (which is used by
> default in the netty component). However, in the netty-http component,
> HttpClientInitializerFactory is used by default, which does not use the
> hostnameVerification option.
> A workaround solution was to override HttpClientInitializerFactory:
> {code:java}
> public class HttpsClientInitializerFactory extends
> HttpClientInitializerFactory {
> [constructors removed]
> @Override
> protected void initChannel(Channel ch) throws Exception {
> super.initChannel(ch);
> if (configuration.isHostnameVerification()) {
> ChannelHandler handler = ch.pipeline().get("ssl");
> SSLEngine engine = ((SslHandler)handler).engine();
> SSLParameters sslParams = engine.getSSLParameters();
> sslParams.setEndpointIdentificationAlgorithm("HTTPS");
> engine.setSSLParameters(sslParams);
> }
> }
> }{code}
> The hostnameVerification option is documented in both netty and netty-http
> components and it seems odd that it would require a custom
> ClientInitializerFactory.
> A possible solution would be to re-use the implementation from
> DefaultClientInitializerFactory in HttpClientInitializerFactory.
> Only tested in Camel 3.x but dont see any changes affecting this since
> implementation in CAMEL-16315
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20806) ProducerCache may reference producers from stopped endpoints
[
https://issues.apache.org/jira/browse/CAMEL-20806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20806.
-
Resolution: Information Provided
If you build your own multitenant Camel app server then you are responsible for
house keeping routes / endpoints and whatever you do.
> ProducerCache may reference producers from stopped endpoints
>
>
> Key: CAMEL-20806
> URL: https://issues.apache.org/jira/browse/CAMEL-20806
> Project: Camel
> Issue Type: Wish
> Components: camel-core
>Affects Versions: 4.4.1
>Reporter: Lars Storm (Systematic)
>Priority: Minor
>
> *Problem in short:*
> The DefaultProducerCache created from .toD(...) in a route may reference
> producers created from endpoints that have been stopped.
> Specifically the endpoint may have been stopped from
> camelContext.removeEndpoint(...)
> *Proposal:*
> ProducerCaches should be notified when an endpoint is stopped. The
> ProducerCache may then find and evict the leaked producer.
> *Use case:*
> In some cases we create a n endpoint (e.g. CxfEndpoint) programmatically per
> tenant (Multi-tenant setup) and store the endpoint in a non-Camel cache. The
> endpoint is then passed on to a Camel route on request.
> The endpoint is then dynamically used in a .toD(...)
> However the local cache may decide to stop the endpoint due to changes
> performed in tenant properties and create a new one. e.g. changing the
> endpoint url or similar.
> In that case the TenantEndpointCache removes the current endpoint the camel
> context and creates a new one which is added to the context.
> Example route code:
> {noformat}
> .setProperty("endpoint").method(TenantEndpointCache.class, "createEndpoint")
> .toD("${exchangeProperty.endpoint}"){noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20821) camel-opentelemetry - Add traceProcessors boolean option
[ https://issues.apache.org/jira/browse/CAMEL-20821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20821. - Assignee: Claus Ibsen Resolution: Fixed > camel-opentelemetry - Add traceProcessors boolean option > > > Key: CAMEL-20821 > URL: https://issues.apache.org/jira/browse/CAMEL-20821 > Project: Camel > Issue Type: Improvement > Components: camel-opentelemetry >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.7.0 > > > To make it easy to enable tracing every processor in its own span -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20821) camel-opentelemetry - Add traceProcessors boolean option
[ https://issues.apache.org/jira/browse/CAMEL-20821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851050#comment-17851050 ] Claus Ibsen commented on CAMEL-20821: - https://github.com/apache/camel-spring-boot/pull/1157 > camel-opentelemetry - Add traceProcessors boolean option > > > Key: CAMEL-20821 > URL: https://issues.apache.org/jira/browse/CAMEL-20821 > Project: Camel > Issue Type: Improvement > Components: camel-opentelemetry >Reporter: Claus Ibsen >Priority: Minor > Fix For: 4.7.0 > > > To make it easy to enable tracing every processor in its own span -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20821) camel-opentelemetry - Add traceProcessors boolean option
Claus Ibsen created CAMEL-20821: --- Summary: camel-opentelemetry - Add traceProcessors boolean option Key: CAMEL-20821 URL: https://issues.apache.org/jira/browse/CAMEL-20821 Project: Camel Issue Type: Improvement Components: camel-opentelemetry Reporter: Claus Ibsen Fix For: 4.7.0 To make it easy to enable tracing every processor in its own span -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20820) camel-core - Duplicate JMX MBean operation for resource endpoints
[ https://issues.apache.org/jira/browse/CAMEL-20820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20820. - Resolution: Fixed > camel-core - Duplicate JMX MBean operation for resource endpoints > - > > Key: CAMEL-20820 > URL: https://issues.apache.org/jira/browse/CAMEL-20820 > Project: Camel > Issue Type: Bug > Components: camel-core, jmx >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.7.0 > > > Reported on user mailing list -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20820) camel-core - Duplicate JMX MBean operation for resource endpoints
[ https://issues.apache.org/jira/browse/CAMEL-20820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20820: --- Assignee: Claus Ibsen > camel-core - Duplicate JMX MBean operation for resource endpoints > - > > Key: CAMEL-20820 > URL: https://issues.apache.org/jira/browse/CAMEL-20820 > Project: Camel > Issue Type: Bug > Components: camel-core, jmx >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.7.0 > > > Reported on user mailing list -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20820) camel-core - Duplicate JMX MBean operation for resource endpoints
Claus Ibsen created CAMEL-20820: --- Summary: camel-core - Duplicate JMX MBean operation for resource endpoints Key: CAMEL-20820 URL: https://issues.apache.org/jira/browse/CAMEL-20820 Project: Camel Issue Type: Bug Components: camel-core, jmx Reporter: Claus Ibsen Fix For: 4.7.0 Reported on user mailing list -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20819) camel-jbang - Reload mode with supervising route controller does not reload routes
[ https://issues.apache.org/jira/browse/CAMEL-20819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20819. - Resolution: Fixed > camel-jbang - Reload mode with supervising route controller does not reload > routes > -- > > Key: CAMEL-20819 > URL: https://issues.apache.org/jira/browse/CAMEL-20819 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 4.6.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.7.0 > > > camel-kamelets-examples/jbang/hello-yaml main❯ camel run hello.camel.yaml > --dev --prop=camel.routecontroller.enabled=true > > Does not reload route on change due to using supervised -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20802) Velocity shows error when using ${headers}
[
https://issues.apache.org/jira/browse/CAMEL-20802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20802.
-
Resolution: Cannot Reproduce
> Velocity shows error when using ${headers}
> --
>
> Key: CAMEL-20802
> URL: https://issues.apache.org/jira/browse/CAMEL-20802
> Project: Camel
> Issue Type: Bug
> Components: camel-velocity
>Affects Versions: 4.6.0
>Reporter: Raymond
>Priority: Minor
> Attachments: main-xml.zip
>
>
> In Camel 3 (3.20.8) I have the following route:
> {code:java}
>
>
>
> ${headers}
>
>
> uri="log:foo//?skipBodyLineSeparator=falsemultiline=trueshowHeaders=falseshowBody=trueshowBodyType=trueshowFiles=trueshowException=falseshowStackTrace=falseshowCaughtException=false"/>
> {code}
> Then I get an output like this:
> {code:java}
> {Accept=text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7,
> Accept-Encoding=gzip, deflate, br, zstd,
> Accept-Language=nl-NL,nl;q=0.9,en-US;q=0.8,en;q=0.7,
> breadcrumbId=7FE304808A5EF7B-8538,
> CamelServletContextPath=/regressiontests/Velocity,
> CamelVelocityTemplate=(this Map), ComponentInitTime=1716561470224,
> Connection=close, Cookie=_ga=GA1.1.1085399545.1665049218;
> _ga_J0TKN8HXSY=GS1.1.1715979059.148.0.1715979059.0.0.0;
> nPT0%3D--35c503a9ecbf1d3922b78a7289ee8eb8f80e1d36, Host=assimbly-test:9001,
> sec-ch-ua="Google Chrome";v="125", "Chromium";v="125", "Not.A/Brand";v="24",
> sec-ch-ua-mobile=?0, sec-ch-ua-platform="Windows", Sec-Fetch-Dest=document,
> Sec-Fetch-Mode=navigate, Sec-Fetch-Site=none, Sec-Fetch-User=?1,
> Upgrade-Insecure-Requests=1, User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64;
> x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36}
> {code}
> However when running the route with Camel 4 (using 4.6.0 on JDK21) I get the
> following error:
> {code:java}
> java.lang.StackOverflowError: null
> at
> java.base/java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:806)
> at java.base/java.lang.StringBuffer.append(StringBuffer.java:425)
> at java.base/java.io.StringWriter.write(StringWriter.java:79)
> at org.apache.camel.util.json.Jsoner.serialize(Jsoner.java:963)
> at org.apache.camel.util.json.Jsoner.serialize(Jsoner.java:1004)
> at org.apache.camel.util.json.Jsoner.serialize(Jsoner.java:1006)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20466) camel-core - Rest DSL to be inlined by default to avoid clutter up list of routes
[ https://issues.apache.org/jira/browse/CAMEL-20466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850941#comment-17850941 ] Claus Ibsen commented on CAMEL-20466: - Thanks adding a note to the rest-dsl docs > camel-core - Rest DSL to be inlined by default to avoid clutter up list of > routes > - > > Key: CAMEL-20466 > URL: https://issues.apache.org/jira/browse/CAMEL-20466 > Project: Camel > Issue Type: Improvement > Components: camel-core, rest >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.5.0 > > > When using rest-dsl you have 1 route per rest verb (GET, POST etc) and then > another route that it typically call via direct. > There is an inlined = true option you can use to make this a single route. We > should make this the default. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-19985) camel-smooks - Add component for Smooks for EDI data mapping
[ https://issues.apache.org/jira/browse/CAMEL-19985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-19985: --- Assignee: Claus Ibsen > camel-smooks - Add component for Smooks for EDI data mapping > > > Key: CAMEL-19985 > URL: https://issues.apache.org/jira/browse/CAMEL-19985 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 4.7.0 > > > This project is now ASF2 licensed > https://github.com/smooks/smooks > We used to have a camel-smooks component (camel-extra) in v1 many years ago. > We should add this component again, so users can use smooks for EDI data > mapping -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19985) camel-smooks - Add component for Smooks for EDI data mapping
[ https://issues.apache.org/jira/browse/CAMEL-19985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19985: Fix Version/s: 4.7.0 (was: 4.x) > camel-smooks - Add component for Smooks for EDI data mapping > > > Key: CAMEL-19985 > URL: https://issues.apache.org/jira/browse/CAMEL-19985 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 4.7.0 > > > This project is now ASF2 licensed > https://github.com/smooks/smooks > We used to have a camel-smooks component (camel-extra) in v1 many years ago. > We should add this component again, so users can use smooks for EDI data > mapping -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20818) camel-yaml-dsl - errorHandler does not have id field as all other YAML elements
[
https://issues.apache.org/jira/browse/CAMEL-20818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20818.
-
Resolution: Fixed
> camel-yaml-dsl - errorHandler does not have id field as all other YAML
> elements
> ---
>
> Key: CAMEL-20818
> URL: https://issues.apache.org/jira/browse/CAMEL-20818
> Project: Camel
> Issue Type: Bug
> Components: camel-yaml-dsl
>Affects Versions: 4.6.0
>Reporter: Marat Gubaidullin
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.7.0
>
>
> The following code
> {code:java}
> - route:
> id: route-b877
> nodePrefixId: route-899
> errorHandler:
> id: errorHandler-f8ae
> deadLetterChannel:
> id: deadLetterChannel-b6bf
> deadLetterUri: log:dlq
> from:
> id: from-4e1e
> uri: timer
> parameters:
> timerName: test
> steps:
> - log:
> id: log-d948
> message: Hello
> {code}
> throws
>
> {code:java}
> Unsupported field: id
> in file:demo.camel.yaml, line 5, column 11:
> id: errorHandler-f8ae
> ^
> at
> org.apache.camel.dsl.yaml.deserializers.ErrorHandlerDeserializer.construct(ErrorHandlerDeserializer.java:123)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20818) camel-yaml-dsl - errorHandler does not have id field as all other YAML elements
[
https://issues.apache.org/jira/browse/CAMEL-20818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20818:
Summary: camel-yaml-dsl - errorHandler does not have id field as all other
YAML elements (was: errorHandler does not have id field as all other YAML
elements)
> camel-yaml-dsl - errorHandler does not have id field as all other YAML
> elements
> ---
>
> Key: CAMEL-20818
> URL: https://issues.apache.org/jira/browse/CAMEL-20818
> Project: Camel
> Issue Type: Bug
> Components: camel-yaml-dsl
>Affects Versions: 4.6.0
>Reporter: Marat Gubaidullin
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.7.0
>
>
> The following code
> {code:java}
> - route:
> id: route-b877
> nodePrefixId: route-899
> errorHandler:
> id: errorHandler-f8ae
> deadLetterChannel:
> id: deadLetterChannel-b6bf
> deadLetterUri: log:dlq
> from:
> id: from-4e1e
> uri: timer
> parameters:
> timerName: test
> steps:
> - log:
> id: log-d948
> message: Hello
> {code}
> throws
>
> {code:java}
> Unsupported field: id
> in file:demo.camel.yaml, line 5, column 11:
> id: errorHandler-f8ae
> ^
> at
> org.apache.camel.dsl.yaml.deserializers.ErrorHandlerDeserializer.construct(ErrorHandlerDeserializer.java:123)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20818) errorHandler does not have id field as all other YAML elements
[
https://issues.apache.org/jira/browse/CAMEL-20818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-20818:
---
Assignee: Claus Ibsen
> errorHandler does not have id field as all other YAML elements
> --
>
> Key: CAMEL-20818
> URL: https://issues.apache.org/jira/browse/CAMEL-20818
> Project: Camel
> Issue Type: Bug
> Components: camel-yaml-dsl
>Affects Versions: 4.6.0
>Reporter: Marat Gubaidullin
>Assignee: Claus Ibsen
>Priority: Minor
>
> The following code
> {code:java}
> - route:
> id: route-b877
> nodePrefixId: route-899
> errorHandler:
> id: errorHandler-f8ae
> deadLetterChannel:
> id: deadLetterChannel-b6bf
> deadLetterUri: log:dlq
> from:
> id: from-4e1e
> uri: timer
> parameters:
> timerName: test
> steps:
> - log:
> id: log-d948
> message: Hello
> {code}
> throws
>
> {code:java}
> Unsupported field: id
> in file:demo.camel.yaml, line 5, column 11:
> id: errorHandler-f8ae
> ^
> at
> org.apache.camel.dsl.yaml.deserializers.ErrorHandlerDeserializer.construct(ErrorHandlerDeserializer.java:123)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20818) errorHandler does not have id field as all other YAML elements
[
https://issues.apache.org/jira/browse/CAMEL-20818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20818:
Fix Version/s: 4.7.0
> errorHandler does not have id field as all other YAML elements
> --
>
> Key: CAMEL-20818
> URL: https://issues.apache.org/jira/browse/CAMEL-20818
> Project: Camel
> Issue Type: Bug
> Components: camel-yaml-dsl
>Affects Versions: 4.6.0
>Reporter: Marat Gubaidullin
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.7.0
>
>
> The following code
> {code:java}
> - route:
> id: route-b877
> nodePrefixId: route-899
> errorHandler:
> id: errorHandler-f8ae
> deadLetterChannel:
> id: deadLetterChannel-b6bf
> deadLetterUri: log:dlq
> from:
> id: from-4e1e
> uri: timer
> parameters:
> timerName: test
> steps:
> - log:
> id: log-d948
> message: Hello
> {code}
> throws
>
> {code:java}
> Unsupported field: id
> in file:demo.camel.yaml, line 5, column 11:
> id: errorHandler-f8ae
> ^
> at
> org.apache.camel.dsl.yaml.deserializers.ErrorHandlerDeserializer.construct(ErrorHandlerDeserializer.java:123)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20819) camel-jbang - Reload mode with supervising route controller does not reload routes
Claus Ibsen created CAMEL-20819: --- Summary: camel-jbang - Reload mode with supervising route controller does not reload routes Key: CAMEL-20819 URL: https://issues.apache.org/jira/browse/CAMEL-20819 Project: Camel Issue Type: Bug Components: camel-jbang Affects Versions: 4.6.0 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 4.7.0 camel-kamelets-examples/jbang/hello-yaml main❯ camel run hello.camel.yaml --dev --prop=camel.routecontroller.enabled=true Does not reload route on change due to using supervised -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18546) camel-core - HostedService - To mark a consumer as a Camel hosted service
[ https://issues.apache.org/jira/browse/CAMEL-18546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849998#comment-17849998 ] Claus Ibsen edited comment on CAMEL-18546 at 5/30/24 1:23 PM: -- TODO: Consider using ServiceRegistry API or some similar concept to have an API to lookup the services *DONE* TODO: Attach more details such as unique service ids, route ids, etc to be able to link to which routes is using what services. was (Author: davsclaus): TODO: Consider using ServiceRegistry API or some similar concept to have an API to lookup the services TODO: Attach more details such as unique service ids, route ids, etc to be able to link to which routes is using what services. > camel-core - HostedService - To mark a consumer as a Camel hosted service > - > > Key: CAMEL-18546 > URL: https://issues.apache.org/jira/browse/CAMEL-18546 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.7.0 > > > A few components hosts a service exclusive in Camel such as HTTP/TCP based > from cxf > from platform-http > from servlet > from netty (not in client mode) > from mina > from mllp > from jetty > There may be a few others. > Its not the same as > from file > from jms > from kafka > As these are camel consumer that reacts on events from another "service", eg > JMS broker or Kafka broker. > If we have an API/SPI to mark a consumer as being a HostedConsumer (or come > up with a better name). Then we can collect service information, such as > - name > - protocol > - ur to call the service > - additional metadata > - api schema (optional) > Then we can make camel-core able to detect all its consumers that are hosted, > and be able to expose this so its easier for tooling etc to gather a list of > services. > There is something related to this in RestRegistry in camel-core but that was > for RESTful hosted service only. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20817) camel-core - PluginManager should ensure plugins gets started
[ https://issues.apache.org/jira/browse/CAMEL-20817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20817: Priority: Minor (was: Major) > camel-core - PluginManager should ensure plugins gets started > - > > Key: CAMEL-20817 > URL: https://issues.apache.org/jira/browse/CAMEL-20817 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Priority: Minor > Fix For: 4.x > > > When using PluginManager then the plugins can be added but these plugins are > not started when camel starts and thus they can be in invalid state. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20816) Camel-JBang: Export to quarkus does not honor quarkusGroupId setting
[
https://issues.apache.org/jira/browse/CAMEL-20816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20816:
Priority: Minor (was: Major)
> Camel-JBang: Export to quarkus does not honor quarkusGroupId setting
>
>
> Key: CAMEL-20816
> URL: https://issues.apache.org/jira/browse/CAMEL-20816
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
> Environment: camel jbang 4.6.0
>Reporter: Andrej Vano
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.7.0
>
>
> I want to export the integration as a quarkus maven project using jbang
> There is an option to specify quarkusGroupId, however there is
> {{io.quarkus.platform}} hardcoded
> [here|https://github.com/apache/camel/blob/main/dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/common/CatalogLoader.java#L170]
> that causes an issue when I want to use a downstream quarkus version.
> This works on {{camel-4.5.x}} branch as there is a [catch
> block|https://github.com/apache/camel/blob/camel-4.5.x/dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/common/CatalogLoader.java#L215]
> that ignores that exception
> Steps to reproduce:
> - jbang app install --force camel@apache/camel/main
> - camel init test.yaml --directory=/tmp/app
> - camel export --runtime quarkus --gav com.test:example:1.0
> --quarkus-group-id com.redhat.quarkus.platform --quarkus-version
> 3.8.4.SP1-redhat-1 --dir /tmp/export /tmp/app/test.yaml
> {code}
> camel export --runtime quarkus --gav com.test:example:1.0 --quarkus-group-id
> com.redhat.quarkus.platform --quarkus-version 3.8.4.SP1-redhat-1 --dir
> /tmp/export /tmp/app/test.yaml
> Generating fresh run data
> Exporting as Quarkus project to: /tmp/export
> org.apache.camel.main.download.DownloadException: Cannot resolve dependencies
> in https://repo1.maven.org/maven2, https://repo.maven.apache.org/maven2,
> https://maven.repository.redhat.com/ga,
> https://maven.repository.redhat.com/earlyaccess/all,
> https://indy.psi.redhat.com/api/content/maven/group/builds-untested+shared-imports/,
> https://indy.psi.redhat.com/api/content/maven/hosted/temporary-builds/,
> https://repository.engineering.redhat.com/nexus/repository/jboss-qa-releases/,
> https://nexus.fuse-qe.eng.rdu2.redhat.com/repository/fuse-all/
> at
> org.apache.camel.main.download.MavenDependencyDownloader.resolveDependenciesViaAether(MavenDependencyDownloader.java:566)
> at
> org.apache.camel.main.download.MavenDependencyDownloader.downloadArtifact(MavenDependencyDownloader.java:338)
> at
> org.apache.camel.dsl.jbang.core.common.CatalogLoader.loadQuarkusCatalog(CatalogLoader.java:170)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.createMavenPom(ExportQuarkus.java:353)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.export(ExportQuarkus.java:121)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:138)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:57)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:239)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.doCall(Export.java:28)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2041)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2453)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2415)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2417)
> at picocli.CommandLine.execute(CommandLine.java:2170)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:165)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:61)
> at main.CamelJBang.main(CamelJBang.java:36)
> Caused by: org.apache.camel.tooling.maven.MavenResolutionException: The
> following artifacts could not be resolved:
> io.quarkus.platform:quarkus-camel-bom:pom:3.8.4.SP1-redhat-1 (absent):
> Could not find artifact
> io.quarkus.platform:quarkus-camel-bom:pom:3.8.4.SP1-redhat-1 in central
> (https://repo1.maven.org/maven2)
> at
>
[jira] [Resolved] (CAMEL-20816) Camel-JBang: Export to quarkus does not honor quarkusGroupId setting
[
https://issues.apache.org/jira/browse/CAMEL-20816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20816.
-
Resolution: Fixed
> Camel-JBang: Export to quarkus does not honor quarkusGroupId setting
>
>
> Key: CAMEL-20816
> URL: https://issues.apache.org/jira/browse/CAMEL-20816
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
> Environment: camel jbang 4.6.0
>Reporter: Andrej Vano
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.7.0
>
>
> I want to export the integration as a quarkus maven project using jbang
> There is an option to specify quarkusGroupId, however there is
> {{io.quarkus.platform}} hardcoded
> [here|https://github.com/apache/camel/blob/main/dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/common/CatalogLoader.java#L170]
> that causes an issue when I want to use a downstream quarkus version.
> This works on {{camel-4.5.x}} branch as there is a [catch
> block|https://github.com/apache/camel/blob/camel-4.5.x/dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/common/CatalogLoader.java#L215]
> that ignores that exception
> Steps to reproduce:
> - jbang app install --force camel@apache/camel/main
> - camel init test.yaml --directory=/tmp/app
> - camel export --runtime quarkus --gav com.test:example:1.0
> --quarkus-group-id com.redhat.quarkus.platform --quarkus-version
> 3.8.4.SP1-redhat-1 --dir /tmp/export /tmp/app/test.yaml
> {code}
> camel export --runtime quarkus --gav com.test:example:1.0 --quarkus-group-id
> com.redhat.quarkus.platform --quarkus-version 3.8.4.SP1-redhat-1 --dir
> /tmp/export /tmp/app/test.yaml
> Generating fresh run data
> Exporting as Quarkus project to: /tmp/export
> org.apache.camel.main.download.DownloadException: Cannot resolve dependencies
> in https://repo1.maven.org/maven2, https://repo.maven.apache.org/maven2,
> https://maven.repository.redhat.com/ga,
> https://maven.repository.redhat.com/earlyaccess/all,
> https://indy.psi.redhat.com/api/content/maven/group/builds-untested+shared-imports/,
> https://indy.psi.redhat.com/api/content/maven/hosted/temporary-builds/,
> https://repository.engineering.redhat.com/nexus/repository/jboss-qa-releases/,
> https://nexus.fuse-qe.eng.rdu2.redhat.com/repository/fuse-all/
> at
> org.apache.camel.main.download.MavenDependencyDownloader.resolveDependenciesViaAether(MavenDependencyDownloader.java:566)
> at
> org.apache.camel.main.download.MavenDependencyDownloader.downloadArtifact(MavenDependencyDownloader.java:338)
> at
> org.apache.camel.dsl.jbang.core.common.CatalogLoader.loadQuarkusCatalog(CatalogLoader.java:170)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.createMavenPom(ExportQuarkus.java:353)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.export(ExportQuarkus.java:121)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:138)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:57)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:239)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.doCall(Export.java:28)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2041)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2453)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2415)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2417)
> at picocli.CommandLine.execute(CommandLine.java:2170)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:165)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:61)
> at main.CamelJBang.main(CamelJBang.java:36)
> Caused by: org.apache.camel.tooling.maven.MavenResolutionException: The
> following artifacts could not be resolved:
> io.quarkus.platform:quarkus-camel-bom:pom:3.8.4.SP1-redhat-1 (absent):
> Could not find artifact
> io.quarkus.platform:quarkus-camel-bom:pom:3.8.4.SP1-redhat-1 in central
> (https://repo1.maven.org/maven2)
> at
>
[jira] [Reopened] (CAMEL-20816) Camel-JBang: Export to quarkus does not honor quarkusGroupId setting
[
https://issues.apache.org/jira/browse/CAMEL-20816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reopened CAMEL-20816:
-
Assignee: Claus Ibsen
I took a look and added back to ignore download catalog errors and to use the
custom group id
> Camel-JBang: Export to quarkus does not honor quarkusGroupId setting
>
>
> Key: CAMEL-20816
> URL: https://issues.apache.org/jira/browse/CAMEL-20816
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
> Environment: camel jbang 4.6.0
>Reporter: Andrej Vano
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.7.0
>
>
> I want to export the integration as a quarkus maven project using jbang
> There is an option to specify quarkusGroupId, however there is
> {{io.quarkus.platform}} hardcoded
> [here|https://github.com/apache/camel/blob/main/dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/common/CatalogLoader.java#L170]
> that causes an issue when I want to use a downstream quarkus version.
> This works on {{camel-4.5.x}} branch as there is a [catch
> block|https://github.com/apache/camel/blob/camel-4.5.x/dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/common/CatalogLoader.java#L215]
> that ignores that exception
> Steps to reproduce:
> - jbang app install --force camel@apache/camel/main
> - camel init test.yaml --directory=/tmp/app
> - camel export --runtime quarkus --gav com.test:example:1.0
> --quarkus-group-id com.redhat.quarkus.platform --quarkus-version
> 3.8.4.SP1-redhat-1 --dir /tmp/export /tmp/app/test.yaml
> {code}
> camel export --runtime quarkus --gav com.test:example:1.0 --quarkus-group-id
> com.redhat.quarkus.platform --quarkus-version 3.8.4.SP1-redhat-1 --dir
> /tmp/export /tmp/app/test.yaml
> Generating fresh run data
> Exporting as Quarkus project to: /tmp/export
> org.apache.camel.main.download.DownloadException: Cannot resolve dependencies
> in https://repo1.maven.org/maven2, https://repo.maven.apache.org/maven2,
> https://maven.repository.redhat.com/ga,
> https://maven.repository.redhat.com/earlyaccess/all,
> https://indy.psi.redhat.com/api/content/maven/group/builds-untested+shared-imports/,
> https://indy.psi.redhat.com/api/content/maven/hosted/temporary-builds/,
> https://repository.engineering.redhat.com/nexus/repository/jboss-qa-releases/,
> https://nexus.fuse-qe.eng.rdu2.redhat.com/repository/fuse-all/
> at
> org.apache.camel.main.download.MavenDependencyDownloader.resolveDependenciesViaAether(MavenDependencyDownloader.java:566)
> at
> org.apache.camel.main.download.MavenDependencyDownloader.downloadArtifact(MavenDependencyDownloader.java:338)
> at
> org.apache.camel.dsl.jbang.core.common.CatalogLoader.loadQuarkusCatalog(CatalogLoader.java:170)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.createMavenPom(ExportQuarkus.java:353)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.export(ExportQuarkus.java:121)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:138)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:57)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:239)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.doCall(Export.java:28)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2041)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2453)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2415)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2417)
> at picocli.CommandLine.execute(CommandLine.java:2170)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:165)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:61)
> at main.CamelJBang.main(CamelJBang.java:36)
> Caused by: org.apache.camel.tooling.maven.MavenResolutionException: The
> following artifacts could not be resolved:
> io.quarkus.platform:quarkus-camel-bom:pom:3.8.4.SP1-redhat-1 (absent):
> Could not find artifact
> io.quarkus.platform:quarkus-camel-bom:pom:3.8.4.SP1-redhat-1 in central
> (https://repo1.maven.org/maven2)
[jira] [Updated] (CAMEL-20816) Camel-JBang: Export to quarkus does not honor quarkusGroupId setting
[
https://issues.apache.org/jira/browse/CAMEL-20816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20816:
Fix Version/s: 4.7.0
> Camel-JBang: Export to quarkus does not honor quarkusGroupId setting
>
>
> Key: CAMEL-20816
> URL: https://issues.apache.org/jira/browse/CAMEL-20816
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
> Environment: camel jbang 4.6.0
>Reporter: Andrej Vano
>Priority: Major
> Fix For: 4.7.0
>
>
> I want to export the integration as a quarkus maven project using jbang
> There is an option to specify quarkusGroupId, however there is
> {{io.quarkus.platform}} hardcoded
> [here|https://github.com/apache/camel/blob/main/dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/common/CatalogLoader.java#L170]
> that causes an issue when I want to use a downstream quarkus version.
> This works on {{camel-4.5.x}} branch as there is a [catch
> block|https://github.com/apache/camel/blob/camel-4.5.x/dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/common/CatalogLoader.java#L215]
> that ignores that exception
> Steps to reproduce:
> - jbang app install --force camel@apache/camel/main
> - camel init test.yaml --directory=/tmp/app
> - camel export --runtime quarkus --gav com.test:example:1.0
> --quarkus-group-id com.redhat.quarkus.platform --quarkus-version
> 3.8.4.SP1-redhat-1 --dir /tmp/export /tmp/app/test.yaml
> {code}
> camel export --runtime quarkus --gav com.test:example:1.0 --quarkus-group-id
> com.redhat.quarkus.platform --quarkus-version 3.8.4.SP1-redhat-1 --dir
> /tmp/export /tmp/app/test.yaml
> Generating fresh run data
> Exporting as Quarkus project to: /tmp/export
> org.apache.camel.main.download.DownloadException: Cannot resolve dependencies
> in https://repo1.maven.org/maven2, https://repo.maven.apache.org/maven2,
> https://maven.repository.redhat.com/ga,
> https://maven.repository.redhat.com/earlyaccess/all,
> https://indy.psi.redhat.com/api/content/maven/group/builds-untested+shared-imports/,
> https://indy.psi.redhat.com/api/content/maven/hosted/temporary-builds/,
> https://repository.engineering.redhat.com/nexus/repository/jboss-qa-releases/,
> https://nexus.fuse-qe.eng.rdu2.redhat.com/repository/fuse-all/
> at
> org.apache.camel.main.download.MavenDependencyDownloader.resolveDependenciesViaAether(MavenDependencyDownloader.java:566)
> at
> org.apache.camel.main.download.MavenDependencyDownloader.downloadArtifact(MavenDependencyDownloader.java:338)
> at
> org.apache.camel.dsl.jbang.core.common.CatalogLoader.loadQuarkusCatalog(CatalogLoader.java:170)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.createMavenPom(ExportQuarkus.java:353)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.export(ExportQuarkus.java:121)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:138)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:57)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:239)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.doCall(Export.java:28)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2041)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2453)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2415)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2417)
> at picocli.CommandLine.execute(CommandLine.java:2170)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:165)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:61)
> at main.CamelJBang.main(CamelJBang.java:36)
> Caused by: org.apache.camel.tooling.maven.MavenResolutionException: The
> following artifacts could not be resolved:
> io.quarkus.platform:quarkus-camel-bom:pom:3.8.4.SP1-redhat-1 (absent):
> Could not find artifact
> io.quarkus.platform:quarkus-camel-bom:pom:3.8.4.SP1-redhat-1 in central
> (https://repo1.maven.org/maven2)
> at
> org.apache.camel.tooling.maven.MavenDownloaderImpl.resolveArtifacts(MavenDownloaderImpl.java:480)
> at
>
[jira] [Resolved] (CAMEL-20816) Camel-JBang: Export to quarkus does not honor quarkusGroupId setting
[
https://issues.apache.org/jira/browse/CAMEL-20816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20816.
-
Resolution: Invalid
Report this to the vendor of that commercial product. This is community only.
> Camel-JBang: Export to quarkus does not honor quarkusGroupId setting
>
>
> Key: CAMEL-20816
> URL: https://issues.apache.org/jira/browse/CAMEL-20816
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
> Environment: camel jbang 4.6.0
>Reporter: Andrej Vano
>Priority: Major
>
> I want to export the integration as a quarkus maven project using jbang
> There is an option to specify quarkusGroupId, however there is
> {{io.quarkus.platform}} hardcoded
> [here|https://github.com/apache/camel/blob/main/dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/common/CatalogLoader.java#L170]
> that causes an issue when I want to use a downstream quarkus version.
> This works on {{camel-4.5.x}} branch as there is a [catch
> block|https://github.com/apache/camel/blob/camel-4.5.x/dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/common/CatalogLoader.java#L215]
> that ignores that exception
> Steps to reproduce:
> - jbang app install --force camel@apache/camel/main
> - camel init test.yaml --directory=/tmp/app
> - camel export --runtime quarkus --gav com.test:example:1.0
> --quarkus-group-id com.redhat.quarkus.platform --quarkus-version
> 3.8.4.SP1-redhat-1 --dir /tmp/export /tmp/app/test.yaml
> {code}
> camel export --runtime quarkus --gav com.test:example:1.0 --quarkus-group-id
> com.redhat.quarkus.platform --quarkus-version 3.8.4.SP1-redhat-1 --dir
> /tmp/export /tmp/app/test.yaml
> Generating fresh run data
> Exporting as Quarkus project to: /tmp/export
> org.apache.camel.main.download.DownloadException: Cannot resolve dependencies
> in https://repo1.maven.org/maven2, https://repo.maven.apache.org/maven2,
> https://maven.repository.redhat.com/ga,
> https://maven.repository.redhat.com/earlyaccess/all,
> https://indy.psi.redhat.com/api/content/maven/group/builds-untested+shared-imports/,
> https://indy.psi.redhat.com/api/content/maven/hosted/temporary-builds/,
> https://repository.engineering.redhat.com/nexus/repository/jboss-qa-releases/,
> https://nexus.fuse-qe.eng.rdu2.redhat.com/repository/fuse-all/
> at
> org.apache.camel.main.download.MavenDependencyDownloader.resolveDependenciesViaAether(MavenDependencyDownloader.java:566)
> at
> org.apache.camel.main.download.MavenDependencyDownloader.downloadArtifact(MavenDependencyDownloader.java:338)
> at
> org.apache.camel.dsl.jbang.core.common.CatalogLoader.loadQuarkusCatalog(CatalogLoader.java:170)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.createMavenPom(ExportQuarkus.java:353)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.export(ExportQuarkus.java:121)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:138)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:57)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:239)
> at
> org.apache.camel.dsl.jbang.core.commands.Export.doCall(Export.java:28)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2041)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2453)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2415)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2417)
> at picocli.CommandLine.execute(CommandLine.java:2170)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:165)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:61)
> at main.CamelJBang.main(CamelJBang.java:36)
> Caused by: org.apache.camel.tooling.maven.MavenResolutionException: The
> following artifacts could not be resolved:
> io.quarkus.platform:quarkus-camel-bom:pom:3.8.4.SP1-redhat-1 (absent):
> Could not find artifact
> io.quarkus.platform:quarkus-camel-bom:pom:3.8.4.SP1-redhat-1 in central
> (https://repo1.maven.org/maven2)
> at
>
[jira] [Created] (CAMEL-20817) camel-core - PluginManager should ensure plugins gets started
Claus Ibsen created CAMEL-20817: --- Summary: camel-core - PluginManager should ensure plugins gets started Key: CAMEL-20817 URL: https://issues.apache.org/jira/browse/CAMEL-20817 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Fix For: 4.x When using PluginManager then the plugins can be added but these plugins are not started when camel starts and thus they can be in invalid state. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20815) exchange.getVariable does not get Global variables in custom processor
[
https://issues.apache.org/jira/browse/CAMEL-20815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20815.
-
Resolution: Fixed
> exchange.getVariable does not get Global variables in custom processor
> --
>
> Key: CAMEL-20815
> URL: https://issues.apache.org/jira/browse/CAMEL-20815
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.6.0
>Reporter: Marat Gubaidullin
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.7.0
>
>
> This one does not work in custom processor:
> {code:java}
> Object val1 = exchange.getVariable("global:testVar"); {code}
> This one works fine:
> {code:java}
> Object val2 = exchange.getContext().getVariable("testVar"); {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20815) exchange.getVariable does not get Global variables in custom processor
[
https://issues.apache.org/jira/browse/CAMEL-20815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20815:
Fix Version/s: 4.7.0
> exchange.getVariable does not get Global variables in custom processor
> --
>
> Key: CAMEL-20815
> URL: https://issues.apache.org/jira/browse/CAMEL-20815
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.6.0
>Reporter: Marat Gubaidullin
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.7.0
>
>
> This one does not work in custom processor:
> {code:java}
> Object val1 = exchange.getVariable("global:testVar"); {code}
> This one works fine:
> {code:java}
> Object val2 = exchange.getContext().getVariable("testVar"); {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (CAMEL-20815) exchange.getVariable does not get Global variables in custom processor
[
https://issues.apache.org/jira/browse/CAMEL-20815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reopened CAMEL-20815:
-
Assignee: Claus Ibsen
The doc was wrong, but lets make it possible via exchange anyway since then it
better fits the docs and makes it possible to work with variables both global
and exchange scoped everywhere
> exchange.getVariable does not get Global variables in custom processor
> --
>
> Key: CAMEL-20815
> URL: https://issues.apache.org/jira/browse/CAMEL-20815
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.6.0
>Reporter: Marat Gubaidullin
>Assignee: Claus Ibsen
>Priority: Minor
>
> This one does not work in custom processor:
> {code:java}
> Object val1 = exchange.getVariable("global:testVar"); {code}
> This one works fine:
> {code:java}
> Object val2 = exchange.getContext().getVariable("testVar"); {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20788) Use another protobuf-maven-plugin
[ https://issues.apache.org/jira/browse/CAMEL-20788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20788: Fix Version/s: 4.7.0 (was: 4.x) > Use another protobuf-maven-plugin > - > > Key: CAMEL-20788 > URL: https://issues.apache.org/jira/browse/CAMEL-20788 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-salesforce >Reporter: Claus Ibsen >Assignee: Craig Ziesman >Priority: Major > Fix For: 4.7.0 > > > The [https://www.xolstice.org/protobuf-maven-plugin] is not maintained > anymore and last release is from 2018. > We can use this instead > [https://github.com/ascopes/protobuf-maven-plugin] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20815) exchange.getVariable does not get Global variables in custom processor
[
https://issues.apache.org/jira/browse/CAMEL-20815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850458#comment-17850458
]
Claus Ibsen edited comment on CAMEL-20815 at 5/29/24 6:35 PM:
--
That is not a bug, the getVariable on exchange is only for exchange scoped
variables.
See the javadoc of the APIs
was (Author: davsclaus):
That is not a bug, the getVariable on exchange is only for exchange scoped
variables.
> exchange.getVariable does not get Global variables in custom processor
> --
>
> Key: CAMEL-20815
> URL: https://issues.apache.org/jira/browse/CAMEL-20815
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.6.0
>Reporter: Marat Gubaidullin
>Priority: Minor
>
> This one does not work in custom processor:
> {code:java}
> Object val1 = exchange.getVariable("global:testVar"); {code}
> This one works fine:
> {code:java}
> Object val2 = exchange.getContext().getVariable("testVar"); {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20815) exchange.getVariable does not get Global variables in custom processor
[
https://issues.apache.org/jira/browse/CAMEL-20815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20815.
-
Resolution: Not A Bug
> exchange.getVariable does not get Global variables in custom processor
> --
>
> Key: CAMEL-20815
> URL: https://issues.apache.org/jira/browse/CAMEL-20815
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.6.0
>Reporter: Marat Gubaidullin
>Priority: Minor
>
> This one does not work in custom processor:
> {code:java}
> Object val1 = exchange.getVariable("global:testVar"); {code}
> This one works fine:
> {code:java}
> Object val2 = exchange.getContext().getVariable("testVar"); {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20815) exchange.getVariable does not get Global variables in custom processor
[
https://issues.apache.org/jira/browse/CAMEL-20815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850459#comment-17850459
]
Claus Ibsen commented on CAMEL-20815:
-
You can also use
ExchangeHelper.getVariable method that would support the repo id syntax
> exchange.getVariable does not get Global variables in custom processor
> --
>
> Key: CAMEL-20815
> URL: https://issues.apache.org/jira/browse/CAMEL-20815
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.6.0
>Reporter: Marat Gubaidullin
>Priority: Minor
>
> This one does not work in custom processor:
> {code:java}
> Object val1 = exchange.getVariable("global:testVar"); {code}
> This one works fine:
> {code:java}
> Object val2 = exchange.getContext().getVariable("testVar"); {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20810) camel-jbang - Add camel get platform-http command
[ https://issues.apache.org/jira/browse/CAMEL-20810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20810. - Resolution: Fixed > camel-jbang - Add camel get platform-http command > - > > Key: CAMEL-20810 > URL: https://issues.apache.org/jira/browse/CAMEL-20810 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.7.0 > > > We should add a command to dump the known http endpoints in platform-http. > We can name it camel get platform-http or camel get http > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20810) camel-jbang - Add camel get platform-http command
[ https://issues.apache.org/jira/browse/CAMEL-20810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20810: --- Assignee: Claus Ibsen > camel-jbang - Add camel get platform-http command > - > > Key: CAMEL-20810 > URL: https://issues.apache.org/jira/browse/CAMEL-20810 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.7.0 > > > We should add a command to dump the known http endpoints in platform-http. > We can name it camel get platform-http or camel get http > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20807) Wrong list of spring boor ptoperties in tokenize language
[ https://issues.apache.org/jira/browse/CAMEL-20807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850301#comment-17850301 ] Claus Ibsen commented on CAMEL-20807: - the tokenizer is in core module and then the website has some javascript code to write that table and thus it grabs everything > Wrong list of spring boor ptoperties in tokenize language > - > > Key: CAMEL-20807 > URL: https://issues.apache.org/jira/browse/CAMEL-20807 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Luca Burgazzoli >Priority: Minor > Attachments: image-2024-05-27-15-15-17-133.png > > > The list of spring boot properties listed in > [https://camel.apache.org/components/next/languages/tokenize-language.html] > does not seems to be right as it includes a number of unrelated properties > i.e. from camel-main: > !image-2024-05-27-15-15-17-133.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20799) camel-catalog - Model schema for setHeaders and setVariables does not include array of element
[ https://issues.apache.org/jira/browse/CAMEL-20799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20799. - Resolution: Fixed > camel-catalog - Model schema for setHeaders and setVariables does not include > array of element > -- > > Key: CAMEL-20799 > URL: https://issues.apache.org/jira/browse/CAMEL-20799 > Project: Camel > Issue Type: Bug > Components: camel-catalog >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.7.0 > > > array of headers is missing in setHeader.json > > similar for setVariables -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20799) camel-catalog - Model schema for setHeaders and setVariables does not include array of element
[ https://issues.apache.org/jira/browse/CAMEL-20799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20799: --- Assignee: Claus Ibsen > camel-catalog - Model schema for setHeaders and setVariables does not include > array of element > -- > > Key: CAMEL-20799 > URL: https://issues.apache.org/jira/browse/CAMEL-20799 > Project: Camel > Issue Type: Bug > Components: camel-catalog >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.7.0 > > > array of headers is missing in setHeader.json > > similar for setVariables -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20799) camel-catalog - Model schema for setHeaders and setVariables does not include array of element
[ https://issues.apache.org/jira/browse/CAMEL-20799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20799: Fix Version/s: 4.7.0 (was: 4.x) > camel-catalog - Model schema for setHeaders and setVariables does not include > array of element > -- > > Key: CAMEL-20799 > URL: https://issues.apache.org/jira/browse/CAMEL-20799 > Project: Camel > Issue Type: Bug > Components: camel-catalog >Reporter: Claus Ibsen >Priority: Minor > Fix For: 4.7.0 > > > array of headers is missing in setHeader.json > > similar for setVariables -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20808) camel-etcd - Setting endpoint should be tooling friendly
[ https://issues.apache.org/jira/browse/CAMEL-20808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20808. - Resolution: Fixed > camel-etcd - Setting endpoint should be tooling friendly > > > Key: CAMEL-20808 > URL: https://issues.apache.org/jira/browse/CAMEL-20808 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.7.0 > > > Its a string[] but lets use string with multi values seperated by comma, like > we do elsewhere -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20808) camel-etcd - Setting endpoint should be tooling friendly
[ https://issues.apache.org/jira/browse/CAMEL-20808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20808: --- Assignee: Claus Ibsen > camel-etcd - Setting endpoint should be tooling friendly > > > Key: CAMEL-20808 > URL: https://issues.apache.org/jira/browse/CAMEL-20808 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.7.0 > > > Its a string[] but lets use string with multi values seperated by comma, like > we do elsewhere -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20788) Use another protobuf-maven-plugin
[ https://issues.apache.org/jira/browse/CAMEL-20788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850261#comment-17850261 ] Claus Ibsen commented on CAMEL-20788: - Do we only use this in salesfore or is there other components that use the old plugin which should also be upgraded > Use another protobuf-maven-plugin > - > > Key: CAMEL-20788 > URL: https://issues.apache.org/jira/browse/CAMEL-20788 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-salesforce >Reporter: Claus Ibsen >Assignee: Craig Ziesman >Priority: Major > Fix For: 4.x > > > The [https://www.xolstice.org/protobuf-maven-plugin] is not maintained > anymore and last release is from 2018. > We can use this instead > [https://github.com/ascopes/protobuf-maven-plugin] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20807) Wrong list of spring boor ptoperties in tokenize language
[ https://issues.apache.org/jira/browse/CAMEL-20807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20807: Issue Type: Task (was: Bug) > Wrong list of spring boor ptoperties in tokenize language > - > > Key: CAMEL-20807 > URL: https://issues.apache.org/jira/browse/CAMEL-20807 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Luca Burgazzoli >Priority: Minor > Attachments: image-2024-05-27-15-15-17-133.png > > > The list of spring boot properties listed in > [https://camel.apache.org/components/next/languages/tokenize-language.html] > does not seems to be right as it includes a number of unrelated properties > i.e. from camel-main: > !image-2024-05-27-15-15-17-133.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20779) camel-spring-boot - Upgrade to SB 3.3.0
[ https://issues.apache.org/jira/browse/CAMEL-20779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20779. - Resolution: Fixed > camel-spring-boot - Upgrade to SB 3.3.0 > --- > > Key: CAMEL-20779 > URL: https://issues.apache.org/jira/browse/CAMEL-20779 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Federico Mariani >Priority: Major > Fix For: 4.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20812) camel-netty-http: hostnameVerification option not used
[
https://issues.apache.org/jira/browse/CAMEL-20812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20812:
Fix Version/s: 4.x
> camel-netty-http: hostnameVerification option not used
> --
>
> Key: CAMEL-20812
> URL: https://issues.apache.org/jira/browse/CAMEL-20812
> Project: Camel
> Issue Type: Bug
> Components: camel-netty-http
> Environment: Camel 3.x
> Java 11
>Reporter: Björn Pettersson
>Priority: Minor
> Fix For: 4.x
>
>
> I was trying to set query parameter hostnameVerification=true, in netty-http
> component, but it would not take effect.
> After some fault-finding it turns out that the implementation of
> hostnameVerification is in DefaultClientInitializerFactory (which is used by
> default in the netty component). However, in the netty-http component,
> HttpClientInitializerFactory is used by default, which does not use the
> hostnameVerification option.
> A workaround solution was to override HttpClientInitializerFactory:
> {code:java}
> public class HttpsClientInitializerFactory extends
> HttpClientInitializerFactory {
> [constructors removed]
> @Override
> protected void initChannel(Channel ch) throws Exception {
> super.initChannel(ch);
> if (configuration.isHostnameVerification()) {
> ChannelHandler handler = ch.pipeline().get("ssl");
> SSLEngine engine = ((SslHandler)handler).engine();
> SSLParameters sslParams = engine.getSSLParameters();
> sslParams.setEndpointIdentificationAlgorithm("HTTPS");
> engine.setSSLParameters(sslParams);
> }
> }
> }{code}
> The hostnameVerification option is documented in both netty and netty-http
> components and it seems odd that it would require a custom
> ClientInitializerFactory.
> A possible solution would be to re-use the implementation from
> DefaultClientInitializerFactory in HttpClientInitializerFactory.
> Only tested in Camel 3.x but dont see any changes affecting this since
> implementation in CAMEL-16315
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20812) camel-netty-http: hostnameVerification option not used
[
https://issues.apache.org/jira/browse/CAMEL-20812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20812:
Priority: Minor (was: Major)
> camel-netty-http: hostnameVerification option not used
> --
>
> Key: CAMEL-20812
> URL: https://issues.apache.org/jira/browse/CAMEL-20812
> Project: Camel
> Issue Type: Bug
> Components: camel-netty-http
> Environment: Camel 3.x
> Java 11
>Reporter: Björn Pettersson
>Priority: Minor
>
> I was trying to set query parameter hostnameVerification=true, in netty-http
> component, but it would not take effect.
> After some fault-finding it turns out that the implementation of
> hostnameVerification is in DefaultClientInitializerFactory (which is used by
> default in the netty component). However, in the netty-http component,
> HttpClientInitializerFactory is used by default, which does not use the
> hostnameVerification option.
> A workaround solution was to override HttpClientInitializerFactory:
> {code:java}
> public class HttpsClientInitializerFactory extends
> HttpClientInitializerFactory {
> [constructors removed]
> @Override
> protected void initChannel(Channel ch) throws Exception {
> super.initChannel(ch);
> if (configuration.isHostnameVerification()) {
> ChannelHandler handler = ch.pipeline().get("ssl");
> SSLEngine engine = ((SslHandler)handler).engine();
> SSLParameters sslParams = engine.getSSLParameters();
> sslParams.setEndpointIdentificationAlgorithm("HTTPS");
> engine.setSSLParameters(sslParams);
> }
> }
> }{code}
> The hostnameVerification option is documented in both netty and netty-http
> components and it seems odd that it would require a custom
> ClientInitializerFactory.
> A possible solution would be to re-use the implementation from
> DefaultClientInitializerFactory in HttpClientInitializerFactory.
> Only tested in Camel 3.x but dont see any changes affecting this since
> implementation in CAMEL-16315
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20798) camel-tracing - Add servername to more decorators
[ https://issues.apache.org/jira/browse/CAMEL-20798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1784#comment-1784 ] Claus Ibsen commented on CAMEL-20798: - TODO: add service location for cloud components (aws, google and azure) > camel-tracing - Add servername to more decorators > - > > Key: CAMEL-20798 > URL: https://issues.apache.org/jira/browse/CAMEL-20798 > Project: Camel > Issue Type: Improvement > Components: camel-tracing >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.7.0 > > > There is a tag for SERVER_ADDRESS which we can enrich for more of the > decorators. > > Some like JMS is harder as the JMS broker is configured specific such as > ActiveMQ has the brokerURL on the activemq class. > Kafka has boostrapServers etc. > We may add some SPI interface that a component can implemented, and then we > can call it via an endpoint, and then we can use the logic in the component > to return the server address. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18546) camel-core - HostedService - To mark a consumer as a Camel hosted service
[ https://issues.apache.org/jira/browse/CAMEL-18546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849998#comment-17849998 ] Claus Ibsen commented on CAMEL-18546: - TODO: Consider using ServiceRegistry API or some similar concept to have an API to lookup the services TODO: Attach more details such as unique service ids, route ids, etc to be able to link to which routes is using what services. > camel-core - HostedService - To mark a consumer as a Camel hosted service > - > > Key: CAMEL-18546 > URL: https://issues.apache.org/jira/browse/CAMEL-18546 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.7.0 > > > A few components hosts a service exclusive in Camel such as HTTP/TCP based > from cxf > from platform-http > from servlet > from netty (not in client mode) > from mina > from mllp > from jetty > There may be a few others. > Its not the same as > from file > from jms > from kafka > As these are camel consumer that reacts on events from another "service", eg > JMS broker or Kafka broker. > If we have an API/SPI to mark a consumer as being a HostedConsumer (or come > up with a better name). Then we can collect service information, such as > - name > - protocol > - ur to call the service > - additional metadata > - api schema (optional) > Then we can make camel-core able to detect all its consumers that are hosted, > and be able to expose this so its easier for tooling etc to gather a list of > services. > There is something related to this in RestRegistry in camel-core but that was > for RESTful hosted service only. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20798) camel-tracing - Add servername to more decorators
[ https://issues.apache.org/jira/browse/CAMEL-20798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849997#comment-17849997 ] Claus Ibsen commented on CAMEL-20798: - TODO: Add serviceLocationEnabled on default component to have it on all components. Make it eager fetch info in doStart so each component is not fetching on demand. > camel-tracing - Add servername to more decorators > - > > Key: CAMEL-20798 > URL: https://issues.apache.org/jira/browse/CAMEL-20798 > Project: Camel > Issue Type: Improvement > Components: camel-tracing >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.7.0 > > > There is a tag for SERVER_ADDRESS which we can enrich for more of the > decorators. > > Some like JMS is harder as the JMS broker is configured specific such as > ActiveMQ has the brokerURL on the activemq class. > Kafka has boostrapServers etc. > We may add some SPI interface that a component can implemented, and then we > can call it via an endpoint, and then we can use the logic in the component > to return the server address. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20798) camel-tracing - Add servername to more decorators
[ https://issues.apache.org/jira/browse/CAMEL-20798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849968#comment-17849968 ] Claus Ibsen commented on CAMEL-20798: - > A about the AWS ones, there should be an *overrideEndpoint* property you can >use to point to your compatible AWS API endpoint (as an example, that can be >used for tests or to point to a minio/cepth s3 compatible endpoint). Thanks we can add cloud information in another PR. As we need to do this specially for aws,google,azure. > camel-tracing - Add servername to more decorators > - > > Key: CAMEL-20798 > URL: https://issues.apache.org/jira/browse/CAMEL-20798 > Project: Camel > Issue Type: Improvement > Components: camel-tracing >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.7.0 > > > There is a tag for SERVER_ADDRESS which we can enrich for more of the > decorators. > > Some like JMS is harder as the JMS broker is configured specific such as > ActiveMQ has the brokerURL on the activemq class. > Kafka has boostrapServers etc. > We may add some SPI interface that a component can implemented, and then we > can call it via an endpoint, and then we can use the logic in the component > to return the server address. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20811) Netty Http secure failure
[
https://issues.apache.org/jira/browse/CAMEL-20811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849966#comment-17849966
]
Claus Ibsen commented on CAMEL-20811:
-
Optional property to load the key store resource from a uri. By default the
class path is used, otherwise
the uri needs to be specified. For example to use file path as a resource, the
prefix file is needed (file:/path/to/keystore).
In some cases, the resource is omitted as the key store is provided by other
means.
> Netty Http secure failure
> -
>
> Key: CAMEL-20811
> URL: https://issues.apache.org/jira/browse/CAMEL-20811
> Project: Camel
> Issue Type: Bug
>Affects Versions: 4.2.0, 4.4.1
>Reporter: Pasquale Congiusti
>Priority: Major
>
> Hello, I'm reporting here a problem we've noticed in a Camel K route example
> using Netty Http component [1]:
> The following route:
> {code}
>@Override
>public void configure() throws Exception {
> registerSslContextParameter();
>
> from("netty-http:https://0.0.0.0:8443/hello?sslContextParameters=#sslContextParameters=true;)
> .transform().constant("Hello Secure World");
>}
>private void registerSslContextParameter() throws Exception {
> KeyStoreParameters ksp = new KeyStoreParameters();
> ksp.setResource("/tmp/ssl/keystore.jks");
> ksp.setPassword("changeit");
> KeyManagersParameters kmp = new KeyManagersParameters();
> kmp.setKeyPassword("changeit");
> kmp.setKeyStore(ksp);
> KeyStoreParameters tsp = new KeyStoreParameters();
> tsp.setResource("/tmp/ssl/truststore.jks");
> tsp.setPassword("changeit");
> TrustManagersParameters tmp = new TrustManagersParameters();
> tmp.setKeyStore(tsp);
> SSLContextParameters sslContextParameters = new SSLContextParameters();
> sslContextParameters.setKeyManagers(kmp);
> sslContextParameters.setTrustManagers(tmp);
> this.getContext().getRegistry().bind("sslContextParameters",
> sslContextParameters);
>}
> {code}
> Is not working with Camel version 4 (tested with Camel 4.2 and 4.4.1), whilst
> it is working with Camel 3 (3.20.1). The error reported is:
> {code}
> [1] Caused by: java.io.IOException: Could not open /etc/ssl/keystore.jks as a
> file, class path resource, or URL.
> [1] at
> org.apache.camel.support.jsse.JsseParameters.resolveResource(JsseParameters.java:120)
> [1] at
> org.apache.camel.support.jsse.KeyStoreParameters.createKeyStore(KeyStoreParameters.java:192)
> [1] at
> org.apache.camel.support.jsse.KeyManagersParameters.createKeyManagers(KeyManagersParameters.java:102)
> [1] at
> org.apache.camel.support.jsse.SSLContextParameters.createSSLContext(SSLContextParameters.java:269)
> [1] at
> org.apache.camel.component.netty.http.HttpServerInitializerFactory.createSSLContext(HttpServerInitializerFactory.java:148)
> [1] at
> org.apache.camel.component.netty.http.HttpServerInitializerFactory.(HttpServerInitializerFactory.java:63)
> {code}
> Mind that the files are available and the error is the same changing the
> location of the certificates. It seems that it fails to read those files for
> some reason.
> [1] https://github.com/apache/camel-k/issues/5546
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20810) camel-jbang - Add camel get platform-http command
Claus Ibsen created CAMEL-20810: --- Summary: camel-jbang - Add camel get platform-http command Key: CAMEL-20810 URL: https://issues.apache.org/jira/browse/CAMEL-20810 Project: Camel Issue Type: Improvement Components: camel-jbang Reporter: Claus Ibsen Fix For: 4.7.0 We should add a command to dump the known http endpoints in platform-http. We can name it camel get platform-http or camel get http -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20798) camel-tracing - Add servername to more decorators
[ https://issues.apache.org/jira/browse/CAMEL-20798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849508#comment-17849508 ] Claus Ibsen edited comment on CAMEL-20798 at 5/28/24 10:10 AM: --- TODO: API for getting address - EndpointLocationAddress *DONE* TODO: Use API in many components *DONE* TODO: SQL and JMS/AMQP need extra code to find out url to database/broker *DONE* TODO: Make EndpointLocationAddress able to determine if hosted vs not-hosted for consumers (special for camel-mina/camel-netty/camel-mllp and a few others) *DONE* TODO: JMX mbean *DONE* TODO: jbang command *DONE* TODO: camel-tracer to use this information *DONE* was (Author: davsclaus): TODO: API for getting address - EndpointLocationAddress *DONE* TODO: Use API in many components *DONE* TODO: SQL and JMS/AMQP need extra code to find out url to database/broker TODO: Make EndpointLocationAddress able to determine if hosted vs not-hosted for consumers (special for camel-mina/camel-netty/camel-mllp and a few others) *DONE* TODO: JMX mbean *DONE* TODO: jbang command *DONE* TODO: camel-tracer to use this information *DONE* > camel-tracing - Add servername to more decorators > - > > Key: CAMEL-20798 > URL: https://issues.apache.org/jira/browse/CAMEL-20798 > Project: Camel > Issue Type: Improvement > Components: camel-tracing >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.7.0 > > > There is a tag for SERVER_ADDRESS which we can enrich for more of the > decorators. > > Some like JMS is harder as the JMS broker is configured specific such as > ActiveMQ has the brokerURL on the activemq class. > Kafka has boostrapServers etc. > We may add some SPI interface that a component can implemented, and then we > can call it via an endpoint, and then we can use the logic in the component > to return the server address. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20798) camel-tracing - Add servername to more decorators
[
https://issues.apache.org/jira/browse/CAMEL-20798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849945#comment-17849945
]
Claus Ibsen commented on CAMEL-20798:
-
We can now see Artemis information as well
{code:java}
camel get service --metadata
PID NAME COMPONENT DIR PROTOCOL SERVICE METADATA
TOTAL ENDPOINT
82836 consumer jms in jms localhost:61616 username=artemis
7 jms://cheese
82836 consumer jms out jms localhost:61616 username=artemis
7 jms://cheese {code}
> camel-tracing - Add servername to more decorators
> -
>
> Key: CAMEL-20798
> URL: https://issues.apache.org/jira/browse/CAMEL-20798
> Project: Camel
> Issue Type: Improvement
> Components: camel-tracing
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.7.0
>
>
> There is a tag for SERVER_ADDRESS which we can enrich for more of the
> decorators.
>
> Some like JMS is harder as the JMS broker is configured specific such as
> ActiveMQ has the brokerURL on the activemq class.
> Kafka has boostrapServers etc.
> We may add some SPI interface that a component can implemented, and then we
> can call it via an endpoint, and then we can use the logic in the component
> to return the server address.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20798) camel-tracing - Add servername to more decorators
[ https://issues.apache.org/jira/browse/CAMEL-20798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849914#comment-17849914 ] Claus Ibsen commented on CAMEL-20798: - All the cloud components is not done. I guess for these you cannot connect to "your own AWS" so i guess the information can be limited to maybe which aws region you connect to. > camel-tracing - Add servername to more decorators > - > > Key: CAMEL-20798 > URL: https://issues.apache.org/jira/browse/CAMEL-20798 > Project: Camel > Issue Type: Improvement > Components: camel-tracing >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.7.0 > > > There is a tag for SERVER_ADDRESS which we can enrich for more of the > decorators. > > Some like JMS is harder as the JMS broker is configured specific such as > ActiveMQ has the brokerURL on the activemq class. > Kafka has boostrapServers etc. > We may add some SPI interface that a component can implemented, and then we > can call it via an endpoint, and then we can use the logic in the component > to return the server address. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20798) camel-tracing - Add servername to more decorators
[ https://issues.apache.org/jira/browse/CAMEL-20798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849513#comment-17849513 ] Claus Ibsen edited comment on CAMEL-20798 at 5/28/24 5:02 AM: -- camel-activemq camel-activemq6 camel-arangodb camel-asterisk camel-atom camel-bonita camel-cassandraql camel-cm-sms camel-coap camel-cometd camel-couchbase camel-couchdb camel-dhis2 camel-digitalocean camel-docker camel-drill camel-dropbox camel-elasticsearch camel-elasticsearch-rest-client camel-etcd3 camel-fhir camel-ftp camel-geocoder camel-github camel-graphql camel-http-common camel-infinispan camel-irc camel-ironmq camel-jira camel-jmx camel-jt400 camel-kafka camel-kubernetes camel-kudu camel-lucene camel-mail camel-milvus camel-minio camel-mllp camel-nats camel-netty camel-oaipmh camel-opensearch camel-paho camel-paho-mqtt5 camel-pgevent camel-platform-http camel-plc4x camel-printer camel-pulsar camel-qdrant camel-rocketmq camel-rss camel-sap-netweaver camel-smb camel-smpp camel-snmp camel-splunk camel-splunk-hec camel-spring-rabbitmq camel-spring-redis camel-sql camel-ssh camel-stomp camel-telegram camel-thrift camel-tracing camel-twilio camel-undertow camel-vertx camel-weather camel-web3j camel-wordpress camel-workday camel-xmpp camel-zeebe camel-zendesk camel-zookeeper was (Author: davsclaus): camel-activemq camel-activemq6 camel-arangodb camel-asterisk camel-atom camel-bonita camel-cassandraql camel-cm-sms camel-coap camel-cometd camel-couchbase camel-couchdb camel-dhis2 camel-digitalocean camel-docker camel-drill camel-dropbox camel-elasticsearch camel-elasticsearch-rest-client camel-etcd3 camel-fhir camel-ftp camel-geocoder camel-github camel-graphql camel-http-common camel-infinispan camel-irc camel-ironmq camel-jira camel-jmx camel-jt400 camel-kafka camel-kubernetes camel-kudu camel-lucene camel-mail camel-milvus camel-minio camel-mllp camel-nats camel-netty camel-oaipmh camel-opensearch camel-paho camel-paho-mqtt5 camel-pgevent camel-platform-http camel-plc4x camel-printer camel-pulsar camel-qdrant camel-rocketmq camel-rss camel-sap-netweaver camel-smb camel-smpp camel-snmp camel-splunk camel-splunk-hec camel-spring-rabbitmq camel-spring-redis camel-sql camel-ssh camel-stomp camel-telegram camel-tracing camel-vertx > camel-tracing - Add servername to more decorators > - > > Key: CAMEL-20798 > URL: https://issues.apache.org/jira/browse/CAMEL-20798 > Project: Camel > Issue Type: Improvement > Components: camel-tracing >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.7.0 > > > There is a tag for SERVER_ADDRESS which we can enrich for more of the > decorators. > > Some like JMS is harder as the JMS broker is configured specific such as > ActiveMQ has the brokerURL on the activemq class. > Kafka has boostrapServers etc. > We may add some SPI interface that a component can implemented, and then we > can call it via an endpoint, and then we can use the logic in the component > to return the server address. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20798) camel-tracing - Add servername to more decorators
[ https://issues.apache.org/jira/browse/CAMEL-20798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849513#comment-17849513 ] Claus Ibsen edited comment on CAMEL-20798 at 5/27/24 4:37 PM: -- camel-activemq camel-activemq6 camel-arangodb camel-asterisk camel-atom camel-bonita camel-cassandraql camel-cm-sms camel-coap camel-cometd camel-couchbase camel-couchdb camel-dhis2 camel-digitalocean camel-docker camel-drill camel-dropbox camel-elasticsearch camel-elasticsearch-rest-client camel-etcd3 camel-fhir camel-ftp camel-geocoder camel-github camel-graphql camel-http-common camel-infinispan camel-irc camel-ironmq camel-jira camel-jmx camel-jt400 camel-kafka camel-kubernetes camel-kudu camel-lucene camel-mail camel-milvus camel-minio camel-mllp camel-nats camel-netty camel-oaipmh camel-opensearch camel-paho camel-paho-mqtt5 camel-pgevent camel-platform-http camel-plc4x camel-printer camel-pulsar camel-qdrant camel-rocketmq camel-rss camel-sap-netweaver camel-smb camel-smpp camel-snmp camel-splunk camel-splunk-hec camel-spring-rabbitmq camel-spring-redis camel-sql camel-ssh camel-stomp camel-telegram camel-tracing camel-vertx was (Author: davsclaus): camel-activemq camel-activemq6 camel-arangodb camel-asterisk camel-bonita camel-cassandraql camel-cm-sms camel-coap camel-cometd camel-couchbase camel-couchdb camel-dhis2 camel-digitalocean camel-docker camel-drill camel-dropbox camel-elasticsearch camel-elasticsearch-rest-client camel-etcd3 camel-fhir camel-ftp camel-geocoder camel-github camel-graphql camel-http-common camel-infinispan camel-ironmq camel-kafka camel-kudu camel-lucene camel-mail camel-mllp camel-nats camel-netty camel-opensearch camel-paho camel-paho-mqtt5 camel-platform-http camel-pulsar camel-rocketmq camel-sap-netweaver camel-smb camel-smpp camel-snmp camel-splunk camel-splunk-hec camel-spring-rabbitmq camel-spring-redis camel-sql camel-ssh camel-stomp camel-tracing camel-vertx > camel-tracing - Add servername to more decorators > - > > Key: CAMEL-20798 > URL: https://issues.apache.org/jira/browse/CAMEL-20798 > Project: Camel > Issue Type: Improvement > Components: camel-tracing >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.7.0 > > > There is a tag for SERVER_ADDRESS which we can enrich for more of the > decorators. > > Some like JMS is harder as the JMS broker is configured specific such as > ActiveMQ has the brokerURL on the activemq class. > Kafka has boostrapServers etc. > We may add some SPI interface that a component can implemented, and then we > can call it via an endpoint, and then we can use the logic in the component > to return the server address. -- This message was sent by Atlassian Jira (v8.20.10#820010)
