[jira] [Commented] (CAMEL-12751) http producer - Ignore content length header
[ https://issues.apache.org/jira/browse/CAMEL-12751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16597078#comment-16597078 ] ASF GitHub Bot commented on CAMEL-12751: onderson commented on a change in pull request #2496: CAMEL-12751 - Added Content-Length Test for incorrect length. URL: https://github.com/apache/camel/pull/2496#discussion_r213907993 ## File path: camel-core/src/main/java/org/apache/camel/Exchange.java ## @@ -160,6 +160,7 @@ String HTTP_SERVLET_REQUEST= "CamelHttpServletRequest"; String HTTP_SERVLET_RESPONSE = "CamelHttpServletResponse"; +String IGNORE_CONTENT_LENGTH_HEADER = "CamelIgnoreContentLengthHeader"; Review comment: This may not be a necessary This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > http producer - Ignore content length header > > > Key: CAMEL-12751 > URL: https://issues.apache.org/jira/browse/CAMEL-12751 > Project: Camel > Issue Type: Improvement > Components: camel-http, camel-http4 >Reporter: Claus Ibsen >Priority: Major > > When doing eg REST -> HTTP etc then the REST consumer may populate the > message with Content-Length header, which gets propagated to the http > producer. We should by default ignore those existing headers and calculate > the length in the producer based on the message body, eg if string, byte[] > etc which AFAIR does today. > See nabble > http://camel.465427.n5.nabble.com/Content-Length-Header-being-used-previous-HTTP-Response-td5813376.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12751) http producer - Ignore content length header
[ https://issues.apache.org/jira/browse/CAMEL-12751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16597017#comment-16597017 ] ASF GitHub Bot commented on CAMEL-12751: bobpaulin commented on issue #2496: CAMEL-12751 - Added Content-Length Test for incorrect length. URL: https://github.com/apache/camel/pull/2496#issuecomment-417178387 Added a proposed solution. Adding ignoreContentLengthHeader that defaults to true to the HttpProducer. Not sure if adding a property was too much but seemed like a good way to allow the HttpEntityConverter to see the setting. Not sure if there might be other options. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > http producer - Ignore content length header > > > Key: CAMEL-12751 > URL: https://issues.apache.org/jira/browse/CAMEL-12751 > Project: Camel > Issue Type: Improvement > Components: camel-http, camel-http4 >Reporter: Claus Ibsen >Priority: Major > > When doing eg REST -> HTTP etc then the REST consumer may populate the > message with Content-Length header, which gets propagated to the http > producer. We should by default ignore those existing headers and calculate > the length in the producer based on the message body, eg if string, byte[] > etc which AFAIR does today. > See nabble > http://camel.465427.n5.nabble.com/Content-Length-Header-being-used-previous-HTTP-Response-td5813376.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12756) `@ConditionalOnProperty` target property with no metadata
[
https://issues.apache.org/jira/browse/CAMEL-12756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16596656#comment-16596656
]
Claus Ibsen commented on CAMEL-12756:
-
And btw all those starter JARs are auto generated as well where we generate the
java source code and some spring manifest files as well, and then for some of
them we add manually some extra code to enhance the starter.
https://github.com/apache/camel/blob/master/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/SpringBootAutoConfigurationMojo.java
... the source code generation used to be a bit simpler, but Camel has many
things not only regular components, but we do also generate some special for
some EIPs, and other types. Anyway it works really great and makes Camel run
well on SB.
> `@ConditionalOnProperty` target property with no metadata
> -
>
> Key: CAMEL-12756
> URL: https://issues.apache.org/jira/browse/CAMEL-12756
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot
>Affects Versions: 2.22.0
>Reporter: Stephane Nicoll
>Priority: Major
> Fix For: 2.23.0
>
>
> Several auto-configurations use a condition on a property that has no
> metadata. As a result, trying to use it to customize the auto-configuration
> lead to a warning in an IDE.
> The report detected the following:
>
> {noformat}
> org.apache.camel.model.rest.springboot.RestConfigurationDefinitionAutoConfiguration
> [camel.rest.enabled]
> org.apache.camel.spring.boot.TypeConversionConfiguration
> [camel.springboot.typeConversion]
> {noformat}
> For the latter, the property in {{@ConditionalOnProperty}} must use the
> canonical format (i.e. must be {{camel.springboot.type-conversion}})
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12756) `@ConditionalOnProperty` target property with no metadata
[
https://issues.apache.org/jira/browse/CAMEL-12756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16596653#comment-16596653
]
Claus Ibsen commented on CAMEL-12756:
-
There is a maven plugin we use to parse the spring metadata json file, that we
use for
- validate if all the options have descriptions
- automatic update our readme documentation to include a section with a table
of these options
The maven plugin
https://github.com/apache/camel/blob/master/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/UpdateSpringBootAutoConfigurationReadmeMojo.java
Then the maven plugin is used in the root pom where all the starter JARs are
https://github.com/apache/camel/blob/master/platforms/spring-boot/components-starter/pom.xml#L88
We have not yet turned on the fail to true (it logs WARN) as there was 1
component that was not ready yet .. but I think we have since fixed that and
can enable it by default.
And the component docs such as the AWS Kinesis component has this table
auto-generated
https://github.com/apache/camel/blob/master/components/camel-aws/src/main/docs/aws-kinesis-component.adoc#spring-boot-auto-configuration
> `@ConditionalOnProperty` target property with no metadata
> -
>
> Key: CAMEL-12756
> URL: https://issues.apache.org/jira/browse/CAMEL-12756
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot
>Affects Versions: 2.22.0
>Reporter: Stephane Nicoll
>Priority: Major
> Fix For: 2.23.0
>
>
> Several auto-configurations use a condition on a property that has no
> metadata. As a result, trying to use it to customize the auto-configuration
> lead to a warning in an IDE.
> The report detected the following:
>
> {noformat}
> org.apache.camel.model.rest.springboot.RestConfigurationDefinitionAutoConfiguration
> [camel.rest.enabled]
> org.apache.camel.spring.boot.TypeConversionConfiguration
> [camel.springboot.typeConversion]
> {noformat}
> For the latter, the property in {{@ConditionalOnProperty}} must use the
> canonical format (i.e. must be {{camel.springboot.type-conversion}})
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12764) camel-http4: basic auth no longer working when used in combination with a dynamic to
[
https://issues.apache.org/jira/browse/CAMEL-12764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pascal Schumacher updated CAMEL-12764:
--
Labels: regresion (was: )
> camel-http4: basic auth no longer working when used in combination with a
> dynamic to
>
>
> Key: CAMEL-12764
> URL: https://issues.apache.org/jira/browse/CAMEL-12764
> Project: Camel
> Issue Type: Bug
> Components: camel-http4
>Affects Versions: 2.22.0
>Reporter: Pascal Schumacher
>Priority: Major
> Labels: regresion
>
> After upgrading a Spring Boot Project from Camel 2.21.1 to Camel 2.22.0 basic
> authentication of the http4 component stopped working when it is used in
> combination with a dynamic to.
> My (slightly simplified) route:
> {code:java}
> from(inUri)
> .setHeader(Exchange.CONTENT_TYPE,
> constant(MediaType.APPLICATION_JSON_VALUE))
> .setBody(constant("{\"action\":\"signal\"}"))
> .setHeader(Exchange.HTTP_METHOD, constant(HttpMethods.PUT))
>
> .toD("http4://{{username}}:{{password}}@{{host}}:{{port}}/executions/${exchangeProperty.my_id}");
> {code}
> When I change the route and remove the dynamic to everything works fine again:
> {code:java}
> from(inUri)
> .setHeader(Exchange.CONTENT_TYPE,
> constant(MediaType.APPLICATION_JSON_VALUE))
> .setBody(constant("{\"action\":\"signal\"}"))
> .setHeader(Exchange.HTTP_METHOD, constant(HttpMethods.PUT))
> .setHeader(Exchange.HTTP_PATH, exchangeProperty("my_id"))
> .to("http4://{{username}}:{{password}}@{{host}}:{{port}}/executions/");
> {code}
> Maybe this regression was caused by CAMEL-12462?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12605) Enhance the AS2 Component to send and receive encrypted AS2 messages
[ https://issues.apache.org/jira/browse/CAMEL-12605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16596594#comment-16596594 ] ASF GitHub Bot commented on CAMEL-12605: punkhorn commented on issue #2500: [CAMEL-12605] Added test for enveloped request. URL: https://github.com/apache/camel/pull/2500#issuecomment-417025890 @oscerd can you please take a look at this? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Enhance the AS2 Component to send and receive encrypted AS2 messages > > > Key: CAMEL-12605 > URL: https://issues.apache.org/jira/browse/CAMEL-12605 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.23.0 >Reporter: William Collins >Assignee: William Collins >Priority: Major > > Enhance the AS2 Component to support encrypted AS2 messages per RFC4130 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12756) `@ConditionalOnProperty` target property with no metadata
[
https://issues.apache.org/jira/browse/CAMEL-12756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16596544#comment-16596544
]
Stephane Nicoll commented on CAMEL-12756:
-
Can you point me to the check in the build please? Quite curious how you've
implemented that.
> `@ConditionalOnProperty` target property with no metadata
> -
>
> Key: CAMEL-12756
> URL: https://issues.apache.org/jira/browse/CAMEL-12756
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot
>Affects Versions: 2.22.0
>Reporter: Stephane Nicoll
>Priority: Major
> Fix For: 2.23.0
>
>
> Several auto-configurations use a condition on a property that has no
> metadata. As a result, trying to use it to customize the auto-configuration
> lead to a warning in an IDE.
> The report detected the following:
>
> {noformat}
> org.apache.camel.model.rest.springboot.RestConfigurationDefinitionAutoConfiguration
> [camel.rest.enabled]
> org.apache.camel.spring.boot.TypeConversionConfiguration
> [camel.springboot.typeConversion]
> {noformat}
> For the latter, the property in {{@ConditionalOnProperty}} must use the
> canonical format (i.e. must be {{camel.springboot.type-conversion}})
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12756) `@ConditionalOnProperty` target property with no metadata
[
https://issues.apache.org/jira/browse/CAMEL-12756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16596540#comment-16596540
]
Claus Ibsen commented on CAMEL-12756:
-
Thanks, we will look into that canonical case. And thanks very much for
reporting.
> `@ConditionalOnProperty` target property with no metadata
> -
>
> Key: CAMEL-12756
> URL: https://issues.apache.org/jira/browse/CAMEL-12756
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot
>Affects Versions: 2.22.0
>Reporter: Stephane Nicoll
>Priority: Major
> Fix For: 2.23.0
>
>
> Several auto-configurations use a condition on a property that has no
> metadata. As a result, trying to use it to customize the auto-configuration
> lead to a warning in an IDE.
> The report detected the following:
>
> {noformat}
> org.apache.camel.model.rest.springboot.RestConfigurationDefinitionAutoConfiguration
> [camel.rest.enabled]
> org.apache.camel.spring.boot.TypeConversionConfiguration
> [camel.springboot.typeConversion]
> {noformat}
> For the latter, the property in {{@ConditionalOnProperty}} must use the
> canonical format (i.e. must be {{camel.springboot.type-conversion}})
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12756) `@ConditionalOnProperty` target property with no metadata
[
https://issues.apache.org/jira/browse/CAMEL-12756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16596484#comment-16596484
]
Stephane Nicoll commented on CAMEL-12756:
-
Not using the canonical case for {{camel.springboot.typeConversion}} is still a
problem though (please see the Javadoc of {{@ConditionalOnProperty}}.
> `@ConditionalOnProperty` target property with no metadata
> -
>
> Key: CAMEL-12756
> URL: https://issues.apache.org/jira/browse/CAMEL-12756
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot
>Affects Versions: 2.22.0
>Reporter: Stephane Nicoll
>Priority: Major
> Fix For: 2.23.0
>
>
> Several auto-configurations use a condition on a property that has no
> metadata. As a result, trying to use it to customize the auto-configuration
> lead to a warning in an IDE.
> The report detected the following:
>
> {noformat}
> org.apache.camel.model.rest.springboot.RestConfigurationDefinitionAutoConfiguration
> [camel.rest.enabled]
> org.apache.camel.spring.boot.TypeConversionConfiguration
> [camel.springboot.typeConversion]
> {noformat}
> For the latter, the property in {{@ConditionalOnProperty}} must use the
> canonical format (i.e. must be {{camel.springboot.type-conversion}})
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12756) `@ConditionalOnProperty` target property with no metadata
[
https://issues.apache.org/jira/browse/CAMEL-12756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16596478#comment-16596478
]
Stephane Nicoll commented on CAMEL-12756:
-
> When you say meta-data do you mean documentation for the given option?
Yes.
The report ran on 2.22. We didn't try on `master` so if those keys are
documented now, feel free to close this issue of course. Sorry for the noise.
> `@ConditionalOnProperty` target property with no metadata
> -
>
> Key: CAMEL-12756
> URL: https://issues.apache.org/jira/browse/CAMEL-12756
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot
>Affects Versions: 2.22.0
>Reporter: Stephane Nicoll
>Priority: Major
> Fix For: 2.23.0
>
>
> Several auto-configurations use a condition on a property that has no
> metadata. As a result, trying to use it to customize the auto-configuration
> lead to a warning in an IDE.
> The report detected the following:
>
> {noformat}
> org.apache.camel.model.rest.springboot.RestConfigurationDefinitionAutoConfiguration
> [camel.rest.enabled]
> org.apache.camel.spring.boot.TypeConversionConfiguration
> [camel.springboot.typeConversion]
> {noformat}
> For the latter, the property in {{@ConditionalOnProperty}} must use the
> canonical format (i.e. must be {{camel.springboot.type-conversion}})
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-12764) camel-http4: basic auth no longer working when used in combination with a dynamic to
Pascal Schumacher created CAMEL-12764:
-
Summary: camel-http4: basic auth no longer working when used in
combination with a dynamic to
Key: CAMEL-12764
URL: https://issues.apache.org/jira/browse/CAMEL-12764
Project: Camel
Issue Type: Bug
Components: camel-http4
Affects Versions: 2.22.0
Reporter: Pascal Schumacher
After upgrading a Spring Boot Project from Camel 2.21.1 to Camel 2.22.0 basic
authentication of the http4 component stopped working when it is used in
combination with a dynamic to.
My (slightly simplified) route:
{code:java}
from(inUri)
.setHeader(Exchange.CONTENT_TYPE,
constant(MediaType.APPLICATION_JSON_VALUE))
.setBody(constant("{\"action\":\"signal\"}"))
.setHeader(Exchange.HTTP_METHOD, constant(HttpMethods.PUT))
.toD("http4://{{username}}:{{password}}@{{host}}:{{port}}/executions/${exchangeProperty.my_id}");
{code}
When I change the route and remove the dynamic to everything works fine again:
{code:java}
from(inUri)
.setHeader(Exchange.CONTENT_TYPE,
constant(MediaType.APPLICATION_JSON_VALUE))
.setBody(constant("{\"action\":\"signal\"}"))
.setHeader(Exchange.HTTP_METHOD, constant(HttpMethods.PUT))
.setHeader(Exchange.HTTP_PATH, exchangeProperty("my_id"))
.to("http4://{{username}}:{{password}}@{{host}}:{{port}}/executions/");
{code}
Maybe this regression was caused by CAMEL-12462?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12605) Enhance the AS2 Component to send and receive encrypted AS2 messages
[ https://issues.apache.org/jira/browse/CAMEL-12605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16596469#comment-16596469 ] ASF GitHub Bot commented on CAMEL-12605: punkhorn opened a new pull request #2500: [CAMEL-12605] Added test for enveloped request. URL: https://github.com/apache/camel/pull/2500 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Enhance the AS2 Component to send and receive encrypted AS2 messages > > > Key: CAMEL-12605 > URL: https://issues.apache.org/jira/browse/CAMEL-12605 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.23.0 >Reporter: William Collins >Assignee: William Collins >Priority: Major > > Enhance the AS2 Component to support encrypted AS2 messages per RFC4130 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12605) Enhance the AS2 Component to send and receive encrypted AS2 messages
[ https://issues.apache.org/jira/browse/CAMEL-12605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16596470#comment-16596470 ] ASF GitHub Bot commented on CAMEL-12605: GitHub user punkhorn opened a pull request: https://github.com/apache/camel/pull/2500 [CAMEL-12605] Added test for enveloped request. You can merge this pull request into a Git repository by running: $ git pull https://github.com/punkhorn/camel-upstream master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/2500.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2500 commit 44b5d9347d8feec2070d0b2260771a725546729e Author: William Collins Date: 2018-08-29T15:23:32Z [CAMEL-12605] Added test for enveloped request. > Enhance the AS2 Component to send and receive encrypted AS2 messages > > > Key: CAMEL-12605 > URL: https://issues.apache.org/jira/browse/CAMEL-12605 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.23.0 >Reporter: William Collins >Assignee: William Collins >Priority: Major > > Enhance the AS2 Component to support encrypted AS2 messages per RFC4130 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12758) SOAP request causing null namespace URI in SimpleNsStreamWriter camel-cxf/woodstox
[
https://issues.apache.org/jira/browse/CAMEL-12758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16596466#comment-16596466
]
Claus Ibsen commented on CAMEL-12758:
-
Maybe you can try to provide a patch/fix - for example setting that null
namespace to an empty string as workaround.
Also if possible an unit test or sample project that is easy to run to
reproduce the issue would be good.
> SOAP request causing null namespace URI in SimpleNsStreamWriter
> camel-cxf/woodstox
> --
>
> Key: CAMEL-12758
> URL: https://issues.apache.org/jira/browse/CAMEL-12758
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
>Affects Versions: 2.22.0
>Reporter: Jürgen Fritz
>Priority: Major
>
> Getting NullPointer at
> com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace(+SimpleNsStreamWriter.java:134)+
> because parameter nsURI is null. (full stack trace below)
> First call of this method prefix=”soapenv”, nsURI=null
> Second call: prefix=”soap”,
> nsURI=="[http://schemas.xmlsoap.org/soap/envelope/]; (I changed the value of
> nsURI in the debugger in the first call to arrive here)
> In general: if I change the nsURI in the debugger to the correct value or to
> an empty string,
> the request goes through without any error.
> Same SOAP request using SOAPUI 5.4 was working with the same application
> using an older version of camel-cxf (2.12.4) under Java 1.7
> My SOAP request:
> http://schemas.xmlsoap.org/soap/envelope/];
> xmlns:tss="[http://axpo.ch/emis/v1/TimeseriesService];>
>
> MySourceSystem
>
>
>
> IN1806141130169762894
> NA
>
>
> 1234
> MW
> PT15M
>
> quantity="0.041" status="VALID"/>
> quantity="0.036" status="VALID"/>
>
>
>
>
>
>
> Error stack trace:
> com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace(+SimpleNsStreamWriter.java:134+
> 10:27:09,294 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (default
> task-118) Application
> \{http://axpo.ch/emis/v1/TimeseriesService}TimeseriesService#\{http://axpo.ch/emis/v1/TimeseriesService}send
> has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Error
> during type conversion from type:
> org.apache.camel.converter.jaxp.XMLStreamReaderInputStream to the required
> type: javax.xml.stream.XMLStreamReader with value
> [org.apache.camel.converter.jaxp.XMLStreamReaderInputStream@9c55922|mailto:org.apache.camel.converter.jaxp.XMLStreamReaderInputStream@9c55922]
> due +java.lang.NullPointerException+
> at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.checkFailure(+CxfConsumer.java:344+)
> [camel-cxf-2.22.0.jar:2.22.0]
> at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.setResponseBack(+CxfConsumer.java:318+)
> [camel-cxf-2.22.0.jar:2.22.0]
> at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.syncInvoke(+CxfConsumer.java:244+)
> [camel-cxf-2.22.0.jar:2.22.0]
> at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.invoke(+CxfConsumer.java:162+)
> [camel-cxf-2.22.0.jar:2.22.0]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(+ServiceInvokerInterceptor.java:59+)
> [cxf-core-3.2.5.jar:3.2.5]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(+Executors.java:511+)
> [rt.jar:1.8.0_144]
> at java.util.concurrent.FutureTask.run(+FutureTask.java:266+)
> [rt.jar:1.8.0_144]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$2.run(+ServiceInvokerInterceptor.java:126+)
> [cxf-core-3.2.5.jar:3.2.5]
> at
> org.apache.cxf.workqueue.SynchronousExecutor.execute(+SynchronousExecutor.java:37+)
> [cxf-core-3.2.5.jar:3.2.5]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(+ServiceInvokerInterceptor.java:131+)
> [cxf-core-3.2.5.jar:3.2.5]
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(+PhaseInterceptorChain.java:308+)
> [cxf-core-3.2.5.jar:3.2.5]
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(+ChainInitiationObserver.java:121+)
> [cxf-core-3.2.5.jar:3.2.5]
> at
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(+AbstractHTTPDestination.java:267+)
> [cxf-rt-transports-http-3.2.5.jar:3.2.5]
> at
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(+ServletController.java:234+)
> [cxf-rt-transports-http-3.2.5.jar:3.2.5]
> at
>
[jira] [Updated] (CAMEL-12762) camel-sjms - MessageProducer is not closed when using shared session
[ https://issues.apache.org/jira/browse/CAMEL-12762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-12762: Fix Version/s: 2.23.0 2.22.1 2.21.3 > camel-sjms - MessageProducer is not closed when using shared session > > > Key: CAMEL-12762 > URL: https://issues.apache.org/jira/browse/CAMEL-12762 > Project: Camel > Issue Type: Bug > Components: camel-sjms >Reporter: Daniele Fognini >Priority: Major > Fix For: 2.21.3, 2.22.1, 2.23.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12756) `@ConditionalOnProperty` target property with no metadata
[
https://issues.apache.org/jira/browse/CAMEL-12756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-12756:
Fix Version/s: 2.23.0
> `@ConditionalOnProperty` target property with no metadata
> -
>
> Key: CAMEL-12756
> URL: https://issues.apache.org/jira/browse/CAMEL-12756
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot
>Affects Versions: 2.22.0
>Reporter: Stephane Nicoll
>Priority: Major
> Fix For: 2.23.0
>
>
> Several auto-configurations use a condition on a property that has no
> metadata. As a result, trying to use it to customize the auto-configuration
> lead to a warning in an IDE.
> The report detected the following:
>
> {noformat}
> org.apache.camel.model.rest.springboot.RestConfigurationDefinitionAutoConfiguration
> [camel.rest.enabled]
> org.apache.camel.spring.boot.TypeConversionConfiguration
> [camel.springboot.typeConversion]
> {noformat}
> For the latter, the property in {{@ConditionalOnProperty}} must use the
> canonical format (i.e. must be {{camel.springboot.type-conversion}})
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12756) `@ConditionalOnProperty` target property with no metadata
[
https://issues.apache.org/jira/browse/CAMEL-12756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16596460#comment-16596460
]
Claus Ibsen commented on CAMEL-12756:
-
When you say meta-data do you mean documentation for the given option?
We have since the 2.20.0 release for 2.23.0 added documentation for all the
spring boot auto configuration options, and there is a check in the build of
the project that validates we have documentation for all of them.
> `@ConditionalOnProperty` target property with no metadata
> -
>
> Key: CAMEL-12756
> URL: https://issues.apache.org/jira/browse/CAMEL-12756
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot
>Affects Versions: 2.22.0
>Reporter: Stephane Nicoll
>Priority: Major
> Fix For: 2.23.0
>
>
> Several auto-configurations use a condition on a property that has no
> metadata. As a result, trying to use it to customize the auto-configuration
> lead to a warning in an IDE.
> The report detected the following:
>
> {noformat}
> org.apache.camel.model.rest.springboot.RestConfigurationDefinitionAutoConfiguration
> [camel.rest.enabled]
> org.apache.camel.spring.boot.TypeConversionConfiguration
> [camel.springboot.typeConversion]
> {noformat}
> For the latter, the property in {{@ConditionalOnProperty}} must use the
> canonical format (i.e. must be {{camel.springboot.type-conversion}})
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12762) camel-sjms - MessageProducer is not closed when using shared session
[ https://issues.apache.org/jira/browse/CAMEL-12762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-12762: Summary: camel-sjms - MessageProducer is not closed when using shared session (was: MessageProducer is not closed when using shared session) > camel-sjms - MessageProducer is not closed when using shared session > > > Key: CAMEL-12762 > URL: https://issues.apache.org/jira/browse/CAMEL-12762 > Project: Camel > Issue Type: Bug > Components: camel-sjms >Reporter: Daniele Fognini >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12758) SOAP request causing null namespace URI in SimpleNsStreamWriter camel-cxf/woodstox
[
https://issues.apache.org/jira/browse/CAMEL-12758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-12758:
Priority: Major (was: Critical)
> SOAP request causing null namespace URI in SimpleNsStreamWriter
> camel-cxf/woodstox
> --
>
> Key: CAMEL-12758
> URL: https://issues.apache.org/jira/browse/CAMEL-12758
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
>Affects Versions: 2.22.0
>Reporter: Jürgen Fritz
>Priority: Major
>
> Getting NullPointer at
> com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace(+SimpleNsStreamWriter.java:134)+
> because parameter nsURI is null. (full stack trace below)
> First call of this method prefix=”soapenv”, nsURI=null
> Second call: prefix=”soap”,
> nsURI=="[http://schemas.xmlsoap.org/soap/envelope/]; (I changed the value of
> nsURI in the debugger in the first call to arrive here)
> In general: if I change the nsURI in the debugger to the correct value or to
> an empty string,
> the request goes through without any error.
> Same SOAP request using SOAPUI 5.4 was working with the same application
> using an older version of camel-cxf (2.12.4) under Java 1.7
> My SOAP request:
> http://schemas.xmlsoap.org/soap/envelope/];
> xmlns:tss="[http://axpo.ch/emis/v1/TimeseriesService];>
>
> MySourceSystem
>
>
>
> IN1806141130169762894
> NA
>
>
> 1234
> MW
> PT15M
>
> quantity="0.041" status="VALID"/>
> quantity="0.036" status="VALID"/>
>
>
>
>
>
>
> Error stack trace:
> com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace(+SimpleNsStreamWriter.java:134+
> 10:27:09,294 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (default
> task-118) Application
> \{http://axpo.ch/emis/v1/TimeseriesService}TimeseriesService#\{http://axpo.ch/emis/v1/TimeseriesService}send
> has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Error
> during type conversion from type:
> org.apache.camel.converter.jaxp.XMLStreamReaderInputStream to the required
> type: javax.xml.stream.XMLStreamReader with value
> [org.apache.camel.converter.jaxp.XMLStreamReaderInputStream@9c55922|mailto:org.apache.camel.converter.jaxp.XMLStreamReaderInputStream@9c55922]
> due +java.lang.NullPointerException+
> at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.checkFailure(+CxfConsumer.java:344+)
> [camel-cxf-2.22.0.jar:2.22.0]
> at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.setResponseBack(+CxfConsumer.java:318+)
> [camel-cxf-2.22.0.jar:2.22.0]
> at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.syncInvoke(+CxfConsumer.java:244+)
> [camel-cxf-2.22.0.jar:2.22.0]
> at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.invoke(+CxfConsumer.java:162+)
> [camel-cxf-2.22.0.jar:2.22.0]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(+ServiceInvokerInterceptor.java:59+)
> [cxf-core-3.2.5.jar:3.2.5]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(+Executors.java:511+)
> [rt.jar:1.8.0_144]
> at java.util.concurrent.FutureTask.run(+FutureTask.java:266+)
> [rt.jar:1.8.0_144]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$2.run(+ServiceInvokerInterceptor.java:126+)
> [cxf-core-3.2.5.jar:3.2.5]
> at
> org.apache.cxf.workqueue.SynchronousExecutor.execute(+SynchronousExecutor.java:37+)
> [cxf-core-3.2.5.jar:3.2.5]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(+ServiceInvokerInterceptor.java:131+)
> [cxf-core-3.2.5.jar:3.2.5]
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(+PhaseInterceptorChain.java:308+)
> [cxf-core-3.2.5.jar:3.2.5]
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(+ChainInitiationObserver.java:121+)
> [cxf-core-3.2.5.jar:3.2.5]
> at
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(+AbstractHTTPDestination.java:267+)
> [cxf-rt-transports-http-3.2.5.jar:3.2.5]
> at
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(+ServletController.java:234+)
> [cxf-rt-transports-http-3.2.5.jar:3.2.5]
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(+ServletController.java:208+)
> [cxf-rt-transports-http-3.2.5.jar:3.2.5]
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(+ServletController.java:160+)
>
[jira] [Commented] (CAMEL-12721) camel-zipkin - Add support for easy enabling of logging integration
[
https://issues.apache.org/jira/browse/CAMEL-12721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16596448#comment-16596448
]
ASF GitHub Bot commented on CAMEL-12721:
davsclaus commented on a change in pull request #2497: CAMEL-12721:camel-zipkin
- Add support for easy enabling of logging i…
URL: https://github.com/apache/camel/pull/2497#discussion_r213719263
##
File path:
components/camel-zipkin/src/main/java/org/apache/camel/zipkin/ZipkinTracer.java
##
@@ -583,9 +588,12 @@ private void clientRequest(Tracing brave, String
serviceName, ExchangeSendingEve
TraceContext context = span.context();
String traceId = "" + context.traceIdString();
String spanId = "" + context.spanId();
+MDC.put("traceId", traceId);
Review comment:
Beware that some of the code you added with MDC.put are only executed if you
have DEBUG logging, so you need to move this outside, or fix it in another way.
This happens in a few places in this source file.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> camel-zipkin - Add support for easy enabling of logging integration
> ---
>
> Key: CAMEL-12721
> URL: https://issues.apache.org/jira/browse/CAMEL-12721
> Project: Camel
> Issue Type: New Feature
> Components: camel-zipkin
>Affects Versions: 2.22.0
>Reporter: Claus Ibsen
>Priority: Major
> Fix For: 2.23.0
>
>
> We should make it easier to turn on MDC logging via slf4j
> https://github.com/openzipkin/brave/tree/master/context/slf4j
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12721) camel-zipkin - Add support for easy enabling of logging integration
[
https://issues.apache.org/jira/browse/CAMEL-12721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16596449#comment-16596449
]
ASF GitHub Bot commented on CAMEL-12721:
davsclaus commented on a change in pull request #2497: CAMEL-12721:camel-zipkin
- Add support for easy enabling of logging i…
URL: https://github.com/apache/camel/pull/2497#discussion_r213718956
##
File path:
components/camel-zipkin/src/main/java/org/apache/camel/zipkin/ZipkinTracer.java
##
@@ -535,6 +538,8 @@ private void createTracingForService(String pattern,
String serviceName) {
private Tracing newTracing(String serviceName) {
return Tracing.newBuilder()
+.currentTraceContext(ThreadLocalCurrentTraceContext.newBuilder()
+.addScopeDecorator(MDCScopeDecorator.create()).build())
Review comment:
We should add an option to turn on|off this MDC scope decorator
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> camel-zipkin - Add support for easy enabling of logging integration
> ---
>
> Key: CAMEL-12721
> URL: https://issues.apache.org/jira/browse/CAMEL-12721
> Project: Camel
> Issue Type: New Feature
> Components: camel-zipkin
>Affects Versions: 2.22.0
>Reporter: Claus Ibsen
>Priority: Major
> Fix For: 2.23.0
>
>
> We should make it easier to turn on MDC logging via slf4j
> https://github.com/openzipkin/brave/tree/master/context/slf4j
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-12763) Improve the logic to related the consumer to the producer in the direct component
Guillaume Nodet created CAMEL-12763: --- Summary: Improve the logic to related the consumer to the producer in the direct component Key: CAMEL-12763 URL: https://issues.apache.org/jira/browse/CAMEL-12763 Project: Camel Issue Type: Improvement Reporter: Guillaume Nodet Assignee: Guillaume Nodet The endpoint cache has been introduced since the logic was written, removing the need to keep a global map of consumers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12762) MessageProducer is not closed when using shared session
[ https://issues.apache.org/jira/browse/CAMEL-12762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16596372#comment-16596372 ] ASF GitHub Bot commented on CAMEL-12762: GitHub user fogninid opened a pull request: https://github.com/apache/camel/pull/2498 CAMEL-12762: close JMS producer You can merge this pull request into a Git repository by running: $ git pull https://github.com/fogninid/camel master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/2498.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2498 commit e4de63b4fe82b4dae914bdb9661456ad4c700d53 Author: Daniele Fognini Date: 2018-08-27T13:41:18Z CAMEL-12762: close JMS producer > MessageProducer is not closed when using shared session > --- > > Key: CAMEL-12762 > URL: https://issues.apache.org/jira/browse/CAMEL-12762 > Project: Camel > Issue Type: Bug > Components: camel-sjms >Reporter: Daniele Fognini >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12762) MessageProducer is not closed when using shared session
[ https://issues.apache.org/jira/browse/CAMEL-12762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16596371#comment-16596371 ] ASF GitHub Bot commented on CAMEL-12762: fogninid opened a new pull request #2498: CAMEL-12762: close JMS producer URL: https://github.com/apache/camel/pull/2498 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > MessageProducer is not closed when using shared session > --- > > Key: CAMEL-12762 > URL: https://issues.apache.org/jira/browse/CAMEL-12762 > Project: Camel > Issue Type: Bug > Components: camel-sjms >Reporter: Daniele Fognini >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12721) camel-zipkin - Add support for easy enabling of logging integration
[ https://issues.apache.org/jira/browse/CAMEL-12721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16596339#comment-16596339 ] ASF GitHub Bot commented on CAMEL-12721: ramu11 opened a new pull request #2497: CAMEL-12721:camel-zipkin - Add support for easy enabling of logging i… URL: https://github.com/apache/camel/pull/2497 CAMEL-12721:camel-zipkin - Add support for easy enabling of logging integration This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > camel-zipkin - Add support for easy enabling of logging integration > --- > > Key: CAMEL-12721 > URL: https://issues.apache.org/jira/browse/CAMEL-12721 > Project: Camel > Issue Type: New Feature > Components: camel-zipkin >Affects Versions: 2.22.0 >Reporter: Claus Ibsen >Priority: Major > Fix For: 2.23.0 > > > We should make it easier to turn on MDC logging via slf4j > https://github.com/openzipkin/brave/tree/master/context/slf4j -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12721) camel-zipkin - Add support for easy enabling of logging integration
[ https://issues.apache.org/jira/browse/CAMEL-12721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16596340#comment-16596340 ] ASF GitHub Bot commented on CAMEL-12721: GitHub user ramu11 opened a pull request: https://github.com/apache/camel/pull/2497 CAMEL-12721:camel-zipkin - Add support for easy enabling of logging i… CAMEL-12721:camel-zipkin - Add support for easy enabling of logging integration You can merge this pull request into a Git repository by running: $ git pull https://github.com/ramu11/camel master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/2497.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2497 commit 4e0aab855e8a1f586360dec83d236489f122ce71 Author: Ramu Date: 2018-08-29T13:39:24Z CAMEL-12721:camel-zipkin - Add support for easy enabling of logging integration > camel-zipkin - Add support for easy enabling of logging integration > --- > > Key: CAMEL-12721 > URL: https://issues.apache.org/jira/browse/CAMEL-12721 > Project: Camel > Issue Type: New Feature > Components: camel-zipkin >Affects Versions: 2.22.0 >Reporter: Claus Ibsen >Priority: Major > Fix For: 2.23.0 > > > We should make it easier to turn on MDC logging via slf4j > https://github.com/openzipkin/brave/tree/master/context/slf4j -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12762) MessageProducer is not closed when using shared session
Daniele Fognini created CAMEL-12762: --- Summary: MessageProducer is not closed when using shared session Key: CAMEL-12762 URL: https://issues.apache.org/jira/browse/CAMEL-12762 Project: Camel Issue Type: Bug Components: camel-sjms Reporter: Daniele Fognini -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12761) Upgrade to JUnit 4
Guillaume Nodet created CAMEL-12761: --- Summary: Upgrade to JUnit 4 Key: CAMEL-12761 URL: https://issues.apache.org/jira/browse/CAMEL-12761 Project: Camel Issue Type: Improvement Reporter: Guillaume Nodet Assignee: Guillaume Nodet -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12598) camel-tooling for code quality checks and anti-patterns
[ https://issues.apache.org/jira/browse/CAMEL-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16596131#comment-16596131 ] Claus Ibsen commented on CAMEL-12598: - Working on the seda/direct names check > camel-tooling for code quality checks and anti-patterns > --- > > Key: CAMEL-12598 > URL: https://issues.apache.org/jira/browse/CAMEL-12598 > Project: Camel > Issue Type: New Feature > Components: tooling >Reporter: Claus Ibsen >Priority: Major > > We have the camel-maven tooling that can do some scan of your project source > code and report mis configured endpoints, and do route coverage reports etc. > It may be nice to gather a list of anti-patterns and other quality checks for > Camel applications that can be commonly used. And then we can see if we can > build more tooling to check for this. > Here is a few on top of my head (not thought for a long time) > > - You could build a check for using deprecated options / components etc. > *DONE* > > - Also you can maybe check for too many in a content based router EIP. > (like too many if ... elseif ... in java) > > - And maybe also if a route has too many EIPs (eg its too long). > > - Also if a has a single endpoint, then its better to use > which is optimized for a single endpoint. And also has some extra juice > for http endpoints. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12605) Enhance the AS2 Component to send and receive encrypted AS2 messages
[ https://issues.apache.org/jira/browse/CAMEL-12605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16595979#comment-16595979 ] ASF GitHub Bot commented on CAMEL-12605: oscerd commented on issue #2495: [CAMEL-12605] Integrated encryption logic into component. URL: https://github.com/apache/camel/pull/2495#issuecomment-416839830 Thanks for the PR. Merged on master. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Enhance the AS2 Component to send and receive encrypted AS2 messages > > > Key: CAMEL-12605 > URL: https://issues.apache.org/jira/browse/CAMEL-12605 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.23.0 >Reporter: William Collins >Assignee: William Collins >Priority: Major > > Enhance the AS2 Component to support encrypted AS2 messages per RFC4130 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12605) Enhance the AS2 Component to send and receive encrypted AS2 messages
[
https://issues.apache.org/jira/browse/CAMEL-12605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16595980#comment-16595980
]
ASF GitHub Bot commented on CAMEL-12605:
oscerd closed pull request #2495: [CAMEL-12605] Integrated encryption logic
into component.
URL: https://github.com/apache/camel/pull/2495
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/components/camel-as2/camel-as2-api/src/main/java/org/apache/camel/component/as2/api/AS2Algorithm.java
b/components/camel-as2/camel-as2-api/src/main/java/org/apache/camel/component/as2/api/AS2Algorithm.java
new file mode 100644
index 000..8e71f478ff2
--- /dev/null
+++
b/components/camel-as2/camel-as2-api/src/main/java/org/apache/camel/component/as2/api/AS2Algorithm.java
@@ -0,0 +1,346 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.camel.component.as2.api;
+
+import org.bouncycastle.asn1.ASN1ObjectIdentifier;
+import org.bouncycastle.cms.CMSAlgorithm;
+
+interface AS2AlgorithmConstants {
+static final String DES_CBC = "DES_CBC";
+static final String DES_EDE3_CBC = "DES_EDE3_CBC";
+static final String RC2_CBC = "RC2_CBC";
+static final String IDEA_CBC = "IDEA_CBC";
+static final String CAST5_CBC = "CAST5_CBC";
+static final String AES128_CBC = "AES128_CBC";
+static final String AES192_CBC = "AES192_CBC";
+static final String AES256_CBC = "AES256_CBC";
+static final String AES128_CCM = "AES128_CCM";
+static final String AES192_CCM = "AES192_CCM";
+static final String AES256_CCM = "AES256_CCM";
+static final String AES128_GCM = "AES128_GCM";
+static final String AES192_GCM = "AES192_GCM";
+static final String AES256_GCM = "AES256_GCM";
+static final String CAMELLIA128_CBC = "CAMELLIA128_CBC";
+static final String CAMELLIA192_CBC = "CAMELLIA192_CBC";
+static final String CAMELLIA256_CBC = "CAMELLIA256_CBC";
+static final String GOST28147_GCFB = "GOST28147_GCFB";
+static final String SEED_CBC = "SEED_CBC";
+static final String DES_EDE3_WRAP = "DES_EDE3_WRAP";
+static final String AES128_WRAP = "AES128_WRAP";
+static final String AES192_WRAP = "AES192_WRAP";
+static final String AES256_WRAP = "AES256_WRAP";
+static final String CAMELLIA128_WRAP = "CAMELLIA128_WRAP";
+static final String CAMELLIA192_WRAP = "CAMELLIA192_WRAP";
+static final String CAMELLIA256_WRAP = "CAMELLIA256_WRAP";
+static final String SEED_WRAP = "SEED_WRAP";
+static final String GOST28147_WRAP = "GOST28147_WRAP";
+static final String GOST28147_CRYPTOPRO_WRAP = "GOST28147_CRYPTOPRO_WRAP";
+static final String ECDH_SHA1KDF = "ECDH_SHA1KDF";
+static final String ECCDH_SHA1KDF = "ECCDH_SHA1KDF";
+static final String ECMQV_SHA1KDF = "ECMQV_SHA1KDF";
+static final String ECDH_SHA224KDF = "ECDH_SHA224KDF";
+static final String ECCDH_SHA224KDF = "ECCDH_SHA224KDF";
+static final String ECMQV_SHA224KDF = "ECMQV_SHA224KDF";
+static final String ECDH_SHA256KDF = "ECDH_SHA256KDF";
+static final String ECCDH_SHA256KDF = "ECCDH_SHA256KDF";
+static final String ECMQV_SHA256KDF = "ECMQV_SHA256KDF";
+static final String ECDH_SHA384KDF = "ECDH_SHA384KDF";
+static final String ECCDH_SHA384KDF = "ECCDH_SHA384KDF";
+static final String ECMQV_SHA384KDF = "ECMQV_SHA384KDF";
+static final String ECDH_SHA512KDF = "ECDH_SHA512KDF";
+static final String ECCDH_SHA512KDF = "ECCDH_SHA512KDF";
+static final String ECMQV_SHA512KDF = "ECMQV_SHA512KDF";
+static final String ECDHGOST3410_2001 = "ECDHGOST3410_2001";
+static final String ECDHGOST3410_2012_256 = "ECDHGOST3410_2012_256";
+static final String ECDHGOST3410_2012_512 = "ECDHGOST3410_2012_512";
+static final String SHA1 = "SHA1";
+static final String SHA224 = "SHA224";
+static final String SHA256 = "SHA256";
+static final String SHA384 = "SHA384";
+static final
[jira] [Commented] (CAMEL-12605) Enhance the AS2 Component to send and receive encrypted AS2 messages
[ https://issues.apache.org/jira/browse/CAMEL-12605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16595981#comment-16595981 ] ASF GitHub Bot commented on CAMEL-12605: Github user oscerd closed the pull request at: https://github.com/apache/camel/pull/2495 > Enhance the AS2 Component to send and receive encrypted AS2 messages > > > Key: CAMEL-12605 > URL: https://issues.apache.org/jira/browse/CAMEL-12605 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.23.0 >Reporter: William Collins >Assignee: William Collins >Priority: Major > > Enhance the AS2 Component to support encrypted AS2 messages per RFC4130 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
