[jira] [Created] (CAMEL-10884) Add a {{cleanrepo}} profile to Maven build
Zoran Regvart created CAMEL-10884:
-
Summary: Add a {{cleanrepo}} profile to Maven build
Key: CAMEL-10884
URL: https://issues.apache.org/jira/browse/CAMEL-10884
Project: Camel
Issue Type: Improvement
Components: build system
Affects Versions: 2.19.0
Reporter: Zoran Regvart
Assignee: Zoran Regvart
Priority: Trivial
To help you manage disk space usage of your local Maven repository add a
{{cleanrepo}} profile that would remove all Camel artifacts from the local
Maven repository. To be run with
{code}
$ mvn -Pcleanrepo
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (CAMEL-10884) Add a `cleanrepo` profile to Maven build
[
https://issues.apache.org/jira/browse/CAMEL-10884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart updated CAMEL-10884:
--
Summary: Add a `cleanrepo` profile to Maven build (was: Add a
{{cleanrepo}} profile to Maven build)
> Add a `cleanrepo` profile to Maven build
>
>
> Key: CAMEL-10884
> URL: https://issues.apache.org/jira/browse/CAMEL-10884
> Project: Camel
> Issue Type: Improvement
> Components: build system
>Affects Versions: 2.19.0
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Trivial
>
> To help you manage disk space usage of your local Maven repository add a
> {{cleanrepo}} profile that would remove all Camel artifacts from the local
> Maven repository. To be run with
> {code}
> $ mvn -Pcleanrepo
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (CAMEL-10883) Support HTTP 1.1 continue in Undertow
[ https://issues.apache.org/jira/browse/CAMEL-10883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-10883. -- Resolution: Fixed > Support HTTP 1.1 continue in Undertow > - > > Key: CAMEL-10883 > URL: https://issues.apache.org/jira/browse/CAMEL-10883 > Project: Camel > Issue Type: Improvement > Components: camel-undertow >Affects Versions: 2.19.0 >Reporter: Rohan Hart >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 2.19.0 > > > Adding support for "continue" processing in Undertow is trivially done in > UndertowConsumer. > However, the processing of delayed payloads could truncate the data - for me > this happened reliably if the payload was more than 16KB. This has been > replaced by a standard blocking channel which supports the processing > expectations of Undertow's HttpServerExchange. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CAMEL-10883) Support HTTP 1.1 continue in Undertow
[ https://issues.apache.org/jira/browse/CAMEL-10883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-10883: Assignee: Andrea Cosentino > Support HTTP 1.1 continue in Undertow > - > > Key: CAMEL-10883 > URL: https://issues.apache.org/jira/browse/CAMEL-10883 > Project: Camel > Issue Type: Improvement > Components: camel-undertow >Affects Versions: 2.19.0 >Reporter: Rohan Hart >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 2.19.0 > > > Adding support for "continue" processing in Undertow is trivially done in > UndertowConsumer. > However, the processing of delayed payloads could truncate the data - for me > this happened reliably if the payload was more than 16KB. This has been > replaced by a standard blocking channel which supports the processing > expectations of Undertow's HttpServerExchange. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (CAMEL-10883) Support HTTP 1.1 continue in Undertow
[ https://issues.apache.org/jira/browse/CAMEL-10883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-10883 started by Andrea Cosentino. > Support HTTP 1.1 continue in Undertow > - > > Key: CAMEL-10883 > URL: https://issues.apache.org/jira/browse/CAMEL-10883 > Project: Camel > Issue Type: Improvement > Components: camel-undertow >Affects Versions: 2.19.0 >Reporter: Rohan Hart >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 2.19.0 > > > Adding support for "continue" processing in Undertow is trivially done in > UndertowConsumer. > However, the processing of delayed payloads could truncate the data - for me > this happened reliably if the payload was more than 16KB. This has been > replaced by a standard blocking channel which supports the processing > expectations of Undertow's HttpServerExchange. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (CAMEL-10885) Add mask option to log EIP
Claus Ibsen created CAMEL-10885: --- Summary: Add mask option to log EIP Key: CAMEL-10885 URL: https://issues.apache.org/jira/browse/CAMEL-10885 Project: Camel Issue Type: New Feature Components: camel-core Reporter: Claus Ibsen Priority: Minor See nabble http://camel.465427.n5.nabble.com/Mask-password-using-log-component-tp5794301.html We can add a mask option to the Log EIP. It would then take the toString to be logged, and then run a series of reg exp to search/replace sensitive information such as password and passphrase. We need to do this for key=value, xml and json format. So it kinda works on most common formats. We can then add this in the docs that this is what it can do, so users can use it as-is or not. Only if they have very special cases they would then need to write their own mask method and call as a bean from the log message. We can also add such functionality to the log component itself, eg . So they reuse the same masking algorithm. See UriSupport which have masking for uris with key=value -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CAMEL-10885) Add mask option to log EIP
[ https://issues.apache.org/jira/browse/CAMEL-10885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-10885: Estimated Complexity: Moderate (was: Novice) > Add mask option to log EIP > -- > > Key: CAMEL-10885 > URL: https://issues.apache.org/jira/browse/CAMEL-10885 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Priority: Minor > > See nabble > http://camel.465427.n5.nabble.com/Mask-password-using-log-component-tp5794301.html > We can add a mask option to the Log EIP. It would then take the toString to > be logged, and then run a series of reg exp to search/replace sensitive > information such as password and passphrase. > We need to do this for key=value, xml and json format. So it kinda works on > most common formats. > We can then add this in the docs that this is what it can do, so users can > use it as-is or not. Only if they have very special cases they would then > need to write their own mask method and call as a bean from the log message. > We can also add such functionality to the log component itself, eg uri="log:xxx">. > So they reuse the same masking algorithm. > See UriSupport which have masking for uris with key=value -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-10849) Salesforce: subscription channel created per component
[
https://issues.apache.org/jira/browse/CAMEL-10849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880160#comment-15880160
]
Luca Burgazzoli commented on CAMEL-10849:
-
A few notes:
- it would be nice to keep logging the replay id used for a channel
- on endpoint level, it could make more sense to have also replayId instead of
defaultReplayId/defaultReplayIdMap as most of the time you'll end up writing
{{from("salesforce:comments-1?defaultReplayId=-1&...")}} and defaultReplayId is
a little misleading, {{from("salesforce:comments-1?replayId=-1&...")}} is much
clean IMHO.
> Salesforce: subscription channel created per component
> --
>
> Key: CAMEL-10849
> URL: https://issues.apache.org/jira/browse/CAMEL-10849
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Reporter: Luca Burgazzoli
>Assignee: Zoran Regvart
> Fix For: 2.19.0
>
>
> If I creates two salesforce consumers, I can't set different options per
> channel as the client is configured on component level so i.e. you can't set
> a per channel replay id as only the first one is taken into account:
> {code:java}
> from('salesforce:comments-1?updateTopic=true&sObjectQuery=SELECT Id,
> CommentId__c FROM Comment_Event__c')
>
> .to("log:salesforce-comments?level=INFO&showHeaders=false&multiline=false")
> from('salesforce:comments-2?updateTopic=true&sObjectQuery=SELECT Id FROM
> Case')
>
> .to("log:salesforce-cases?level=INFO&showHeaders=false&multiline=false")
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Reopened] (CAMEL-10880) Clear list components "direct-vm" from another OSGI camelContext
[ https://issues.apache.org/jira/browse/CAMEL-10880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Sushko reopened CAMEL-10880: > Clear list components "direct-vm" from another OSGI camelContext > - > > Key: CAMEL-10880 > URL: https://issues.apache.org/jira/browse/CAMEL-10880 > Project: Camel > Issue Type: Bug > Components: camel-core, osgi >Reporter: Aleksey Sushko >Priority: Minor > > First CamelContext create endpoint "direct-vm". > Second CamelContext create ProducerTemplate to this endpoint. > Several attempts to start and stop the second CamelContext lead to clearing > the list of all registered components "direct-vm". > See More Forum [Stop component "direct-vm" from another OSGI > camelContext|http://camel.465427.n5.nabble.com/ > Stop-component-direct-vm-from-another-OSGI-camelContext-tp5794194.html]. > It shows the call stack. Trigger list cleaning. At the same time all the > routes are still in the running. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (CAMEL-10880) Clear list components "direct-vm" from another OSGI camelContext
[ https://issues.apache.org/jira/browse/CAMEL-10880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880020#comment-15880020 ] Aleksey Sushko edited comment on CAMEL-10880 at 2/23/17 9:30 AM: - And where is your decision about the removal of absolutely all components of "direct-vm"? Other components live in their OSGi bundle. Now they do not have access. I did not see the problem. It is clear the list "direct-vm". How to use camel-scr affects the "direct-vm"? was (Author: alexey-s): And where is your decision about the removal of absolutely all components of "direct-vm"? Other components live in their OSGi bundle. Now they do not have access. > Clear list components "direct-vm" from another OSGI camelContext > - > > Key: CAMEL-10880 > URL: https://issues.apache.org/jira/browse/CAMEL-10880 > Project: Camel > Issue Type: Bug > Components: camel-core, osgi >Reporter: Aleksey Sushko >Priority: Minor > > First CamelContext create endpoint "direct-vm". > Second CamelContext create ProducerTemplate to this endpoint. > Several attempts to start and stop the second CamelContext lead to clearing > the list of all registered components "direct-vm". > See More Forum [Stop component "direct-vm" from another OSGI > camelContext|http://camel.465427.n5.nabble.com/ > Stop-component-direct-vm-from-another-OSGI-camelContext-tp5794194.html]. > It shows the call stack. Trigger list cleaning. At the same time all the > routes are still in the running. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (CAMEL-10880) Clear list components "direct-vm" from another OSGI camelContext
[ https://issues.apache.org/jira/browse/CAMEL-10880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-10880. - Resolution: Invalid Use the mailing list for getting help > Clear list components "direct-vm" from another OSGI camelContext > - > > Key: CAMEL-10880 > URL: https://issues.apache.org/jira/browse/CAMEL-10880 > Project: Camel > Issue Type: Bug > Components: camel-core, osgi >Reporter: Aleksey Sushko >Priority: Minor > > First CamelContext create endpoint "direct-vm". > Second CamelContext create ProducerTemplate to this endpoint. > Several attempts to start and stop the second CamelContext lead to clearing > the list of all registered components "direct-vm". > See More Forum [Stop component "direct-vm" from another OSGI > camelContext|http://camel.465427.n5.nabble.com/ > Stop-component-direct-vm-from-another-OSGI-camelContext-tp5794194.html]. > It shows the call stack. Trigger list cleaning. At the same time all the > routes are still in the running. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (CAMEL-10884) Add a `cleanrepo` profile to Maven build
[
https://issues.apache.org/jira/browse/CAMEL-10884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart resolved CAMEL-10884.
---
Resolution: Fixed
You can now invoke {{mvn -Prepoclean}} from the source tree root, which will
remove all versions and all Camel artefacts, or from a single module
subdirectory to remove only artefacts of that module.
> Add a `cleanrepo` profile to Maven build
>
>
> Key: CAMEL-10884
> URL: https://issues.apache.org/jira/browse/CAMEL-10884
> Project: Camel
> Issue Type: Improvement
> Components: build system
>Affects Versions: 2.19.0
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Trivial
>
> To help you manage disk space usage of your local Maven repository add a
> {{cleanrepo}} profile that would remove all Camel artifacts from the local
> Maven repository. To be run with
> {code}
> $ mvn -Pcleanrepo
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (CAMEL-10884) Add a `cleanrepo` profile to Maven build
[
https://issues.apache.org/jira/browse/CAMEL-10884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart updated CAMEL-10884:
--
Fix Version/s: 2.19.0
> Add a `cleanrepo` profile to Maven build
>
>
> Key: CAMEL-10884
> URL: https://issues.apache.org/jira/browse/CAMEL-10884
> Project: Camel
> Issue Type: Improvement
> Components: build system
>Affects Versions: 2.19.0
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Trivial
> Fix For: 2.19.0
>
>
> To help you manage disk space usage of your local Maven repository add a
> {{cleanrepo}} profile that would remove all Camel artifacts from the local
> Maven repository. To be run with
> {code}
> $ mvn -Pcleanrepo
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (CAMEL-10886) Support Limits API response from Salesforce v39.0
Zoran Regvart created CAMEL-10886: - Summary: Support Limits API response from Salesforce v39.0 Key: CAMEL-10886 URL: https://issues.apache.org/jira/browse/CAMEL-10886 Project: Camel Issue Type: Improvement Components: camel-salesforce Affects Versions: 2.19.0 Reporter: Zoran Regvart Assignee: Zoran Regvart Priority: Minor The Limits API since version v39.0, but apparently the affects are seen regardless of specifying the version, have been extended to include additional JSON data -- per connected application API usage. This breaks the JSON response deserialization as these are unknown fields. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (CAMEL-10886) Support Limits API response from Salesforce v39.0
[ https://issues.apache.org/jira/browse/CAMEL-10886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-10886. --- Resolution: Fixed Fix Version/s: 2.19.0 The responses from Limits API that include per-application limits are now supported. > Support Limits API response from Salesforce v39.0 > - > > Key: CAMEL-10886 > URL: https://issues.apache.org/jira/browse/CAMEL-10886 > Project: Camel > Issue Type: Improvement > Components: camel-salesforce >Affects Versions: 2.19.0 >Reporter: Zoran Regvart >Assignee: Zoran Regvart >Priority: Minor > Fix For: 2.19.0 > > > The Limits API since version v39.0, but apparently the affects are seen > regardless of specifying the version, have been extended to include > additional JSON data -- per connected application API usage. > This breaks the JSON response deserialization as these are unknown fields. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-10869) TRACE on ftp component reveals password
[
https://issues.apache.org/jira/browse/CAMEL-10869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880352#comment-15880352
]
Claus Ibsen commented on CAMEL-10869:
-
If you want the password masked you are welcome to provide a github PR with a
fix
https://github.com/apache/camel/
> TRACE on ftp component reveals password
> ---
>
> Key: CAMEL-10869
> URL: https://issues.apache.org/jira/browse/CAMEL-10869
> Project: Camel
> Issue Type: Improvement
> Components: camel-ftp
>Affects Versions: 2.18.2
>Reporter: Mikael Grevsten
> Labels: ftp, trace
>
> When TRACE level is on using a ftp component the password is displayed in
> plain text.
> {{2017-02-21 11:26:28:361 o.a.c.c.f.remote.RemoteFileProducer DEBUG - Not
> already connected/logged in. Connecting to:
> ftp://192.168.170.33/mgr/out?allowNullBody=false&consumer.bridgeErrorHandler=true&disconnect=true&password=xx&pollStrategy=%23defaultPollStrategy&throwExceptionOnConnectFailed=true&username=mgr
> 2017-02-21 11:26:28:361 o.a.c.c.file.remote.FtpOperations TRACE - Connecting
> using FTPClient: org.apache.commons.net.ftp.FTPClient@456abb66
> 2017-02-21 11:26:28:361 o.a.c.c.file.remote.FtpOperations TRACE - Connecting
> to ftp://mgr@192.168.170.33:21 using connection timeout: 1
> 2017-02-21 11:26:28:377 o.a.c.c.file.remote.FtpOperations TRACE - Using
> SoTimeout=30
> 2017-02-21 11:26:28:377 o.a.c.c.file.remote.FtpOperations TRACE - Attempting
> to login user: mgr using password: gsxr1100
> 2017-02-21 11:26:28:845 o.a.c.c.file.remote.FtpOperations TRACE - User mgr
> logged in: true}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (CAMEL-10828) camel-catalog - Allow to index a maven repo and add new components to the catalog
[ https://issues.apache.org/jira/browse/CAMEL-10828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-10828. - Resolution: Fixed > camel-catalog - Allow to index a maven repo and add new components to the > catalog > - > > Key: CAMEL-10828 > URL: https://issues.apache.org/jira/browse/CAMEL-10828 > Project: Camel > Issue Type: New Feature > Components: camel-catalog >Reporter: Claus Ibsen >Assignee: Claus Ibsen > Fix For: 2.19.0 > > > So end users can publish their custom Camel components to a maven repo > (nexus) and then we can index that repo and discover 3rd party Camel > components and add them to the catalog on the fly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (CAMEL-10852) Setting content-type in Header of camel and cxfrs
[
https://issues.apache.org/jira/browse/CAMEL-10852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-10852.
-
Resolution: Invalid
Please use the user forum or user mailing list first to get help
> Setting content-type in Header of camel and cxfrs
> -
>
> Key: CAMEL-10852
> URL: https://issues.apache.org/jira/browse/CAMEL-10852
> Project: Camel
> Issue Type: Bug
>Reporter: Sarath Kumar Navarajan
>
> i have a front end UI which calls a rest service in camel, i have a request
> in which am trying to explicitly set the content type as image/jpeg in the
> Camel exchange.getOut().setHeader("Content-Type","image/jpeg");
> and setting the byte array in exchange.getOut().setBody(byte[]), this should
> actually get the file to be previewed in the browser but JAXRSOutInterceptor
> changes the content type to text/html thereby displaying the byte[] as string
> on the browser. kindly guide me through if am wrong somewhere or if i have
> missed out anything to be added.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (CAMEL-10805) JettyHttpComponent does not stops created ans started QueuedThreadPool
[ https://issues.apache.org/jira/browse/CAMEL-10805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-10805. - Resolution: Invalid > JettyHttpComponent does not stops created ans started QueuedThreadPool > -- > > Key: CAMEL-10805 > URL: https://issues.apache.org/jira/browse/CAMEL-10805 > Project: Camel > Issue Type: Bug > Components: camel-jetty >Affects Versions: 2.16.1 >Reporter: Anton >Priority: Minor > > *JettyHttpComponent* creates *QueuedThreadPool* instance in it's > *connect(HttpConsumer)*, but does not stop/shuts down it neither in > *disconnect(HttpConsumer)* nor in doStop(). > By default *QueuedThreadPool* operates with non-daemon threads > (_daemon=false) and in case of gracefully shutdown, JVM will not be able to > be stopped(process will still operates) due existence of these threads. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-10849) Salesforce: subscription channel created per component
[
https://issues.apache.org/jira/browse/CAMEL-10849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880369#comment-15880369
]
Sune Keller commented on CAMEL-10849:
-
I agree about logging; though it is possible to see already it if you enable
debug logging level for the CometD client, as it is part of the subscribe
message payload, and you could log it in your consuming route by reading the
corresponding exchange header.
As per the current naming, it is to signify that unless you specify initial
{{replayId}} values per channel using the {{initialReplayIdMap}}, the default
specified by {{defaultReplayId}} should be used.
Use case:
Keep 3 instances of a service running that subscribe to the same topic. They
use Idempotent Consumer (http://camel.apache.org/idempotent-consumer.html) to
only process each message once, but at the end of each route, the replayId from
the message is stored, e.g. in Redis with a 24h TTL (since replayIds older than
that are invalid anyway). When the application starts up, the initial replayIds
are read from Redis and populated into the {{initialReplayIdMap}}. Topics for
which no replayId is stored (or it expired per TTL) will then have
{{defaultReplayId}} instead.
Does that make sense?
> Salesforce: subscription channel created per component
> --
>
> Key: CAMEL-10849
> URL: https://issues.apache.org/jira/browse/CAMEL-10849
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Reporter: Luca Burgazzoli
>Assignee: Zoran Regvart
> Fix For: 2.19.0
>
>
> If I creates two salesforce consumers, I can't set different options per
> channel as the client is configured on component level so i.e. you can't set
> a per channel replay id as only the first one is taken into account:
> {code:java}
> from('salesforce:comments-1?updateTopic=true&sObjectQuery=SELECT Id,
> CommentId__c FROM Comment_Event__c')
>
> .to("log:salesforce-comments?level=INFO&showHeaders=false&multiline=false")
> from('salesforce:comments-2?updateTopic=true&sObjectQuery=SELECT Id FROM
> Case')
>
> .to("log:salesforce-cases?level=INFO&showHeaders=false&multiline=false")
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (CAMEL-10887) pack200.exe is not work with camel 2.18.2
Mattias Andersson created CAMEL-10887: - Summary: pack200.exe is not work with camel 2.18.2 Key: CAMEL-10887 URL: https://issues.apache.org/jira/browse/CAMEL-10887 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.18.2 Reporter: Mattias Andersson Priority: Minor we are packing camel-core-2.18.2 together using pack200.exe and get the following error: pack200.exe" -r camel-core-2.18.2.jar Exception in thread "main" java.io.IOException: null ref at com.sun.java.util.jar.pack.NativeUnpack.start(Native Method) at com.sun.java.util.jar.pack.NativeUnpack.run(NativeUnpack.java:198) at com.sun.java.util.jar.pack.NativeUnpack.run(NativeUnpack.java:247) at com.sun.java.util.jar.pack.UnpackerImpl.unpack(UnpackerImpl.java:138) at com.sun.java.util.jar.pack.Driver.main(Driver.java:354) The offending class in the jar-file seems to be: org/apache/camel/com/github/benmanes/caffeine/cache/stats/StatsCounter Should this class really be part of the jar-file (and other classes from caffeine). We excluded the class when we pack and then it works!! There is no problem using camel-core-2.17.x and pack200.exe -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (CAMEL-10849) Salesforce: subscription channel created per component
[
https://issues.apache.org/jira/browse/CAMEL-10849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880369#comment-15880369
]
Sune Keller edited comment on CAMEL-10849 at 2/23/17 12:51 PM:
---
[~lb] I agree about logging; though it is possible to see already it if you
enable debug logging level for the CometD client, as it is part of the
subscribe message payload, and you could log it in your consuming route by
reading the corresponding exchange header.
As per the current naming, it is to signify that unless you specify initial
{{replayId}} values per channel using the {{initialReplayIdMap}}, the default
specified by {{defaultReplayId}} should be used.
Use case:
Keep 3 instances of a service running that subscribe to the same topic. They
use Idempotent Consumer (http://camel.apache.org/idempotent-consumer.html) to
only process each message once, but at the end of each route, the replayId from
the message is stored, e.g. in Redis with a 24h TTL (since replayIds older than
that are invalid anyway). When the application starts up, the initial replayIds
are read from Redis and populated into the {{initialReplayIdMap}}. Topics for
which no replayId is stored (or it expired per TTL) will then have
{{defaultReplayId}} instead.
Does that make sense?
was (Author: sirlatrom):
I agree about logging; though it is possible to see already it if you enable
debug logging level for the CometD client, as it is part of the subscribe
message payload, and you could log it in your consuming route by reading the
corresponding exchange header.
As per the current naming, it is to signify that unless you specify initial
{{replayId}} values per channel using the {{initialReplayIdMap}}, the default
specified by {{defaultReplayId}} should be used.
Use case:
Keep 3 instances of a service running that subscribe to the same topic. They
use Idempotent Consumer (http://camel.apache.org/idempotent-consumer.html) to
only process each message once, but at the end of each route, the replayId from
the message is stored, e.g. in Redis with a 24h TTL (since replayIds older than
that are invalid anyway). When the application starts up, the initial replayIds
are read from Redis and populated into the {{initialReplayIdMap}}. Topics for
which no replayId is stored (or it expired per TTL) will then have
{{defaultReplayId}} instead.
Does that make sense?
> Salesforce: subscription channel created per component
> --
>
> Key: CAMEL-10849
> URL: https://issues.apache.org/jira/browse/CAMEL-10849
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Reporter: Luca Burgazzoli
>Assignee: Zoran Regvart
> Fix For: 2.19.0
>
>
> If I creates two salesforce consumers, I can't set different options per
> channel as the client is configured on component level so i.e. you can't set
> a per channel replay id as only the first one is taken into account:
> {code:java}
> from('salesforce:comments-1?updateTopic=true&sObjectQuery=SELECT Id,
> CommentId__c FROM Comment_Event__c')
>
> .to("log:salesforce-comments?level=INFO&showHeaders=false&multiline=false")
> from('salesforce:comments-2?updateTopic=true&sObjectQuery=SELECT Id FROM
> Case')
>
> .to("log:salesforce-cases?level=INFO&showHeaders=false&multiline=false")
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (CAMEL-10878) camel-http / camel-http4 - Allow to specify HTTP operation as uri parameter
[
https://issues.apache.org/jira/browse/CAMEL-10878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-10878.
--
Resolution: Fixed
> camel-http / camel-http4 - Allow to specify HTTP operation as uri parameter
> ---
>
> Key: CAMEL-10878
> URL: https://issues.apache.org/jira/browse/CAMEL-10878
> Project: Camel
> Issue Type: Improvement
> Components: camel-http-common
>Reporter: Claus Ibsen
>Assignee: Andrea Cosentino
> Fix For: 2.19.0
>
>
> Today HTTP clients do tend to guess if they should use GET or POST etc. And
> you can override this with a message header. But it would also be good to
> specify that explicit as an uri parameter,
> Today you have to do
> {code}
> from("direct:start")
> .setHeader(Exchange.HTTP_METHOD,
> constant(org.apache.camel.component.http4.HttpMethods.POST))
> .to("http4://www.google.com")
> .to("mock:results");
> {code}
> But it would be good if you can do
> {code}
> from("direct:start")
> .to("http4://www.google.com?httpMethod=POST")
> .to("mock:results");
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Work started] (CAMEL-10859) camel-jasypt - Update docs about JAR dependency to run
[ https://issues.apache.org/jira/browse/CAMEL-10859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-10859 started by onder sezgin. > camel-jasypt - Update docs about JAR dependency to run > -- > > Key: CAMEL-10859 > URL: https://issues.apache.org/jira/browse/CAMEL-10859 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Claus Ibsen >Assignee: onder sezgin >Priority: Minor > Fix For: 2.19.0 > > > See nabble > http://camel.465427.n5.nabble.com/Error-encrypting-value-using-camel-jasypt-2-18-1-jar-td5794000.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-10887) pack200.exe is not work with camel 2.18.2
[ https://issues.apache.org/jira/browse/CAMEL-10887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880499#comment-15880499 ] Claus Ibsen commented on CAMEL-10887: - The class is in the JAR 1760 Sun Jan 22 16:42:44 CET 2017 org/apache/camel/com/github/benmanes/caffeine/cache/stats/StatsCounter.class > pack200.exe is not work with camel 2.18.2 > - > > Key: CAMEL-10887 > URL: https://issues.apache.org/jira/browse/CAMEL-10887 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.18.2 >Reporter: Mattias Andersson >Priority: Minor > > we are packing camel-core-2.18.2 together using pack200.exe and get the > following error: > pack200.exe" -r camel-core-2.18.2.jar > Exception in thread "main" java.io.IOException: null ref > at com.sun.java.util.jar.pack.NativeUnpack.start(Native Method) > at com.sun.java.util.jar.pack.NativeUnpack.run(NativeUnpack.java:198) > at com.sun.java.util.jar.pack.NativeUnpack.run(NativeUnpack.java:247) > at > com.sun.java.util.jar.pack.UnpackerImpl.unpack(UnpackerImpl.java:138) > at com.sun.java.util.jar.pack.Driver.main(Driver.java:354) > The offending class in the jar-file seems to be: > org/apache/camel/com/github/benmanes/caffeine/cache/stats/StatsCounter > Should this class really be part of the jar-file (and other classes from > caffeine). We excluded the class when we pack and then it works!! > There is no problem using camel-core-2.17.x and pack200.exe -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (CAMEL-10887) pack200.exe is not work with camel 2.18.2
[ https://issues.apache.org/jira/browse/CAMEL-10887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-10887. - Resolution: Cannot Reproduce > pack200.exe is not work with camel 2.18.2 > - > > Key: CAMEL-10887 > URL: https://issues.apache.org/jira/browse/CAMEL-10887 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.18.2 >Reporter: Mattias Andersson >Priority: Minor > > we are packing camel-core-2.18.2 together using pack200.exe and get the > following error: > pack200.exe" -r camel-core-2.18.2.jar > Exception in thread "main" java.io.IOException: null ref > at com.sun.java.util.jar.pack.NativeUnpack.start(Native Method) > at com.sun.java.util.jar.pack.NativeUnpack.run(NativeUnpack.java:198) > at com.sun.java.util.jar.pack.NativeUnpack.run(NativeUnpack.java:247) > at > com.sun.java.util.jar.pack.UnpackerImpl.unpack(UnpackerImpl.java:138) > at com.sun.java.util.jar.pack.Driver.main(Driver.java:354) > The offending class in the jar-file seems to be: > org/apache/camel/com/github/benmanes/caffeine/cache/stats/StatsCounter > Should this class really be part of the jar-file (and other classes from > caffeine). We excluded the class when we pack and then it works!! > There is no problem using camel-core-2.17.x and pack200.exe -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-10543) New Apache Camel Logo
[ https://issues.apache.org/jira/browse/CAMEL-10543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880523#comment-15880523 ] ASF GitHub Bot commented on CAMEL-10543: GitHub user zregvart opened a pull request: https://github.com/apache/camel/pull/1486 CAMEL-10543: New Apache Camel Logo Here is my proposal, heavily based on @lanwen work. You can merge this pull request into a Git repository by running: $ git pull https://github.com/zregvart/camel master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1486.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 #1486 commit 5c9214acd11063de6105a566729ce0df0a9bd06c Author: Zoran Regvart Date: 2017-02-23T14:27:36Z CAMEL-10543: New Apache Camel Logo Here is my proposal, heavily based on @lanwen work. > New Apache Camel Logo > - > > Key: CAMEL-10543 > URL: https://issues.apache.org/jira/browse/CAMEL-10543 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Luca Burgazzoli > Fix For: Future > > > The Apache Camel logo is a bit out dated so we have discussed in the Camel > PMC and community to come up with a new one. > We encourage anyone to participate by submitting a logo proposal and/or share > thoughts > The logo can be submitted by either: > - a PR on GitHub (preferred) > - file attachment to this JIRA ticket > And each logo should be: > - images should be added to docs/img > - each PR should contains a single logo > We are looking for a new logo that has two parts > - graphical logo > - The name: Apache Camel > So we can use the logo without the word Apache Camel, but also as a > combination of the two of them, eg as logo on the Camel front page. > Also if the logo can be vector based it would be a benefit, so it can scale > up and down nicely. > You can find details here how to contribute to the project and how to work on > the source code. Such as how to do a github PR: > http://camel.apache.org/contributing -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-10887) pack200.exe is not work with camel 2.18.2
[ https://issues.apache.org/jira/browse/CAMEL-10887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880519#comment-15880519 ] Mattias Andersson commented on CAMEL-10887: --- So you are not considering it an error that you cannot use pack200.exe on camel-core-2.18.2.jar? Br, /Mattias > pack200.exe is not work with camel 2.18.2 > - > > Key: CAMEL-10887 > URL: https://issues.apache.org/jira/browse/CAMEL-10887 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.18.2 >Reporter: Mattias Andersson >Priority: Minor > > we are packing camel-core-2.18.2 together using pack200.exe and get the > following error: > pack200.exe" -r camel-core-2.18.2.jar > Exception in thread "main" java.io.IOException: null ref > at com.sun.java.util.jar.pack.NativeUnpack.start(Native Method) > at com.sun.java.util.jar.pack.NativeUnpack.run(NativeUnpack.java:198) > at com.sun.java.util.jar.pack.NativeUnpack.run(NativeUnpack.java:247) > at > com.sun.java.util.jar.pack.UnpackerImpl.unpack(UnpackerImpl.java:138) > at com.sun.java.util.jar.pack.Driver.main(Driver.java:354) > The offending class in the jar-file seems to be: > org/apache/camel/com/github/benmanes/caffeine/cache/stats/StatsCounter > Should this class really be part of the jar-file (and other classes from > caffeine). We excluded the class when we pack and then it works!! > There is no problem using camel-core-2.17.x and pack200.exe -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-10887) pack200.exe is not work with camel 2.18.2
[ https://issues.apache.org/jira/browse/CAMEL-10887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880582#comment-15880582 ] Mattias Andersson commented on CAMEL-10887: --- Just to explain further what I mean. camel-core-2.18.2.jar has several dependencies (sl4j, jaxb-core,jax-impl) but it's only classes from caffeine that is part of the camel-core-2.18.2 jar-file? Is it by design that these classes are included and not a dependency? > pack200.exe is not work with camel 2.18.2 > - > > Key: CAMEL-10887 > URL: https://issues.apache.org/jira/browse/CAMEL-10887 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.18.2 >Reporter: Mattias Andersson >Priority: Minor > > we are packing camel-core-2.18.2 together using pack200.exe and get the > following error: > pack200.exe" -r camel-core-2.18.2.jar > Exception in thread "main" java.io.IOException: null ref > at com.sun.java.util.jar.pack.NativeUnpack.start(Native Method) > at com.sun.java.util.jar.pack.NativeUnpack.run(NativeUnpack.java:198) > at com.sun.java.util.jar.pack.NativeUnpack.run(NativeUnpack.java:247) > at > com.sun.java.util.jar.pack.UnpackerImpl.unpack(UnpackerImpl.java:138) > at com.sun.java.util.jar.pack.Driver.main(Driver.java:354) > The offending class in the jar-file seems to be: > org/apache/camel/com/github/benmanes/caffeine/cache/stats/StatsCounter > Should this class really be part of the jar-file (and other classes from > caffeine). We excluded the class when we pack and then it works!! > There is no problem using camel-core-2.17.x and pack200.exe -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-10849) Salesforce: subscription channel created per component
[
https://issues.apache.org/jira/browse/CAMEL-10849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880697#comment-15880697
]
Luca Burgazzoli commented on CAMEL-10849:
-
Yes it make sense but what I meant was that when you want to set a replyId on
the uri string, thus bound to a specific channel, having something named
initialReplayIdMap or defaultReplayId does not make much sense whereas they are
perfectly meaningful on component level.
> Salesforce: subscription channel created per component
> --
>
> Key: CAMEL-10849
> URL: https://issues.apache.org/jira/browse/CAMEL-10849
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Reporter: Luca Burgazzoli
>Assignee: Zoran Regvart
> Fix For: 2.19.0
>
>
> If I creates two salesforce consumers, I can't set different options per
> channel as the client is configured on component level so i.e. you can't set
> a per channel replay id as only the first one is taken into account:
> {code:java}
> from('salesforce:comments-1?updateTopic=true&sObjectQuery=SELECT Id,
> CommentId__c FROM Comment_Event__c')
>
> .to("log:salesforce-comments?level=INFO&showHeaders=false&multiline=false")
> from('salesforce:comments-2?updateTopic=true&sObjectQuery=SELECT Id FROM
> Case')
>
> .to("log:salesforce-cases?level=INFO&showHeaders=false&multiline=false")
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Work started] (CAMEL-10795) PingCheck API
[
https://issues.apache.org/jira/browse/CAMEL-10795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-10795 started by Luca Burgazzoli.
---
> PingCheck API
> -
>
> Key: CAMEL-10795
> URL: https://issues.apache.org/jira/browse/CAMEL-10795
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
> Fix For: 2.19.0
>
>
> Related to CAMEL-10026 about Health Check API
> We need some way for Camel components to be able to more easily validate if
> they can connect to their remote system.
> And for that the user must configure the Camel component/endpoint accordingly
> with details such as username/password/tokens/ other beans etc.
> How this is done varies from Camel component to component, but most of them
> uses endpoint options.
> So we may want to introduce some interface (whether the name Pingable is a
> good name is up for discussion)
> {code}
> interface Pingable {
> PingResult ping(Map config);
> boolean canPing(Map config);
> }
> class PingResult {
> private boolean isSuccess();
> private String errorMessage();
> }
> {code}
> This API is just a little suggestion.
> The parameters should ideally be type less, eg Map as the
> user configures this in endpoint uris, XML DSL etc. and therefore we should
> be able to do this without having to use Java code per see.
> Also we may want to have canPing as a method to check if the component can
> accept the ping or not. In some cases it may not be able to do the ping.
> For example camel-http component would just require the following information
> in the Map
> httpUri=http://myserver/foo/bar
> Where httpUri is the name of the option accordingly to the table at
> https://github.com/apache/camel/blob/master/components/camel-http/src/main/docs/http-component.adoc
> And then it depends on each Camel component how they do the ping check, the
> http component may do a HTTP HEAD or a HTTP GET etc and check the HTTP
> response code etc.
> Notice this is not intended entirely for runtime health check, but for
> validating/testing Camel components can work with the user given
> configuration to connect to the remote system.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (CAMEL-10887) pack200.exe is not work with camel 2.18.2
[ https://issues.apache.org/jira/browse/CAMEL-10887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880795#comment-15880795 ] Claus Ibsen commented on CAMEL-10887: - Yes caffine is shaded into the jar as its an internal cache implementation that Camel uses. The logging apis has always been external dependencies, and ditto about jaxb > pack200.exe is not work with camel 2.18.2 > - > > Key: CAMEL-10887 > URL: https://issues.apache.org/jira/browse/CAMEL-10887 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.18.2 >Reporter: Mattias Andersson >Priority: Minor > > we are packing camel-core-2.18.2 together using pack200.exe and get the > following error: > pack200.exe" -r camel-core-2.18.2.jar > Exception in thread "main" java.io.IOException: null ref > at com.sun.java.util.jar.pack.NativeUnpack.start(Native Method) > at com.sun.java.util.jar.pack.NativeUnpack.run(NativeUnpack.java:198) > at com.sun.java.util.jar.pack.NativeUnpack.run(NativeUnpack.java:247) > at > com.sun.java.util.jar.pack.UnpackerImpl.unpack(UnpackerImpl.java:138) > at com.sun.java.util.jar.pack.Driver.main(Driver.java:354) > The offending class in the jar-file seems to be: > org/apache/camel/com/github/benmanes/caffeine/cache/stats/StatsCounter > Should this class really be part of the jar-file (and other classes from > caffeine). We excluded the class when we pack and then it works!! > There is no problem using camel-core-2.17.x and pack200.exe -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-6132) camel-test-karaf - To allow end users more easily do Camel and Karaf integration test
[
https://issues.apache.org/jira/browse/CAMEL-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880802#comment-15880802
]
A. Soroka commented on CAMEL-6132:
--
There is currently a {{camel-test-karaf}} bundle and feature available in
2.18.2. Is this the same effort?
> camel-test-karaf - To allow end users more easily do Camel and Karaf
> integration test
> -
>
> Key: CAMEL-6132
> URL: https://issues.apache.org/jira/browse/CAMEL-6132
> Project: Camel
> Issue Type: New Feature
> Components: karaf
>Reporter: Claus Ibsen
>Assignee: Quinn Stevenson
> Fix For: 2.19.0
>
>
> We should introduce a proper camel-test-karaf component that *end users* can
> use to do Camel and Karaf integration tests.
> The code we have in tests/camel-itest-karaf is for internal usage and testing
> of Camel. The code is not polished and intended for end users.
> We should create a new module for that, and take the good parts of
> camel-itest-karaf and make it user friendly etc. And of course have docs to
> go with as well.
> And when its good, we can use that in camel-itest-karaf also (eat our own dog
> food)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (CAMEL-10887) pack200.exe is not work with camel 2.18.2
[ https://issues.apache.org/jira/browse/CAMEL-10887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880840#comment-15880840 ] Mattias Andersson commented on CAMEL-10887: --- I was just curios to why you but those classes in there, but now I know. So I guess its a big no no to use caffeine in your own camel component then I guess. Well anyway this is not a problem for us. Thanks for your fast response. > pack200.exe is not work with camel 2.18.2 > - > > Key: CAMEL-10887 > URL: https://issues.apache.org/jira/browse/CAMEL-10887 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.18.2 >Reporter: Mattias Andersson >Priority: Minor > > we are packing camel-core-2.18.2 together using pack200.exe and get the > following error: > pack200.exe" -r camel-core-2.18.2.jar > Exception in thread "main" java.io.IOException: null ref > at com.sun.java.util.jar.pack.NativeUnpack.start(Native Method) > at com.sun.java.util.jar.pack.NativeUnpack.run(NativeUnpack.java:198) > at com.sun.java.util.jar.pack.NativeUnpack.run(NativeUnpack.java:247) > at > com.sun.java.util.jar.pack.UnpackerImpl.unpack(UnpackerImpl.java:138) > at com.sun.java.util.jar.pack.Driver.main(Driver.java:354) > The offending class in the jar-file seems to be: > org/apache/camel/com/github/benmanes/caffeine/cache/stats/StatsCounter > Should this class really be part of the jar-file (and other classes from > caffeine). We excluded the class when we pack and then it works!! > There is no problem using camel-core-2.17.x and pack200.exe -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (CAMEL-10887) pack200.exe is not work with camel 2.18.2
[ https://issues.apache.org/jira/browse/CAMEL-10887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880840#comment-15880840 ] Mattias Andersson edited comment on CAMEL-10887 at 2/23/17 4:59 PM: I was just curios to why you but those classes in there, but now I know. So I guess its a big no no to use caffeine in your own camel component. Well anyway this is not a problem for us. Thanks for your fast response. was (Author: mattias1972): I was just curios to why you but those classes in there, but now I know. So I guess its a big no no to use caffeine in your own camel component then I guess. Well anyway this is not a problem for us. Thanks for your fast response. > pack200.exe is not work with camel 2.18.2 > - > > Key: CAMEL-10887 > URL: https://issues.apache.org/jira/browse/CAMEL-10887 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.18.2 >Reporter: Mattias Andersson >Priority: Minor > > we are packing camel-core-2.18.2 together using pack200.exe and get the > following error: > pack200.exe" -r camel-core-2.18.2.jar > Exception in thread "main" java.io.IOException: null ref > at com.sun.java.util.jar.pack.NativeUnpack.start(Native Method) > at com.sun.java.util.jar.pack.NativeUnpack.run(NativeUnpack.java:198) > at com.sun.java.util.jar.pack.NativeUnpack.run(NativeUnpack.java:247) > at > com.sun.java.util.jar.pack.UnpackerImpl.unpack(UnpackerImpl.java:138) > at com.sun.java.util.jar.pack.Driver.main(Driver.java:354) > The offending class in the jar-file seems to be: > org/apache/camel/com/github/benmanes/caffeine/cache/stats/StatsCounter > Should this class really be part of the jar-file (and other classes from > caffeine). We excluded the class when we pack and then it works!! > There is no problem using camel-core-2.17.x and pack200.exe -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-6132) camel-test-karaf - To allow end users more easily do Camel and Karaf integration test
[ https://issues.apache.org/jira/browse/CAMEL-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880871#comment-15880871 ] Claus Ibsen commented on CAMEL-6132: Yes it may still need a bit more polishing and love. Contributions is welcome > camel-test-karaf - To allow end users more easily do Camel and Karaf > integration test > - > > Key: CAMEL-6132 > URL: https://issues.apache.org/jira/browse/CAMEL-6132 > Project: Camel > Issue Type: New Feature > Components: karaf >Reporter: Claus Ibsen >Assignee: Quinn Stevenson > Fix For: 2.19.0 > > > We should introduce a proper camel-test-karaf component that *end users* can > use to do Camel and Karaf integration tests. > The code we have in tests/camel-itest-karaf is for internal usage and testing > of Camel. The code is not polished and intended for end users. > We should create a new module for that, and take the good parts of > camel-itest-karaf and make it user friendly etc. And of course have docs to > go with as well. > And when its good, we can use that in camel-itest-karaf also (eat our own dog > food) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-6132) camel-test-karaf - To allow end users more easily do Camel and Karaf integration test
[
https://issues.apache.org/jira/browse/CAMEL-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880903#comment-15880903
]
A. Soroka commented on CAMEL-6132:
--
I would love to help, and I am currently wresting with getting an example up. I
keep running into errors with JNDI (?!), e.g. as shown below. I have experience
with Camel and Karaf, but it dates from five or more years ago, and times have
changed. I am subclassing {{CamelKarafTestSupport}} and I show below the
stacktrace my current {{@Configuration}} method. Any advice much appreciated,
and if I can get a working example I will make a point of at least writing a
tutorial and hopefully sending a PR with whatever improvements I can find. I'm
just stumped by this JNDI business. I think I must be missing something
obvious...
{noformat}
javax.naming.NoInitialContextException: Unable to find the
InitialContextFactory org.apache.camel.util.jndi.CamelInitialContextFactory.
at
org.apache.aries.jndi.ContextHelper.getInitialContext(ContextHelper.java:150)
at
org.apache.aries.jndi.OSGiInitialContextFactoryBuilder.getInitialContext(OSGiInitialContextFactoryBuilder.java:51)
at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
at javax.naming.InitialContext.init(InitialContext.java:244)
at javax.naming.InitialContext.(InitialContext.java:216)
at
org.apache.camel.test.junit4.CamelTestSupport.createJndiContext(CamelTestSupport.java:592)
at
org.apache.camel.test.junit4.CamelTestSupport.createRegistry(CamelTestSupport.java:578)
at
org.apache.camel.test.junit4.CamelTestSupport.createCamelContext(CamelTestSupport.java:572)
at
org.apache.camel.test.junit4.CamelTestSupport.doSetUp(CamelTestSupport.java:278)
at
org.apache.camel.test.junit4.CamelTestSupport.setUp(CamelTestSupport.java:246)
{noformat}
{noformat}
@Configuration
public Option[] config() {
MavenUrlReference camelRepo =
maven().groupId("org.apache.camel.karaf").artifactId("apache-camel")
.classifier("features").type("xml").version(CAMEL_VERSION);
MavenUrlReference jenaRepo =
maven().groupId("org.apache.jena").artifactId("jena-osgi-features")
.classifier("features").type("xml").version("3.2.0");
MavenUrlReference enterpriseRepo =
maven().groupId("org.apache.karaf.features").artifactId("enterprise")
.classifier("features").type("xml").version("4.0.7");
MavenArtifactProvisionOption shim =
mavenBundle().groupId("edu.si").artifactId("fcrepo3-shim-core")
.version("0.0.1-SNAPSHOT").start();
Option[] options = new Option[] { features(enterpriseRepo, "jndi"),
features(jenaRepo, "jena"),
features(camelRepo, "camel-test"), shim };
return ArrayUtils.addAll(configure(), options);
}
{noformat}
> camel-test-karaf - To allow end users more easily do Camel and Karaf
> integration test
> -
>
> Key: CAMEL-6132
> URL: https://issues.apache.org/jira/browse/CAMEL-6132
> Project: Camel
> Issue Type: New Feature
> Components: karaf
>Reporter: Claus Ibsen
>Assignee: Quinn Stevenson
> Fix For: 2.19.0
>
>
> We should introduce a proper camel-test-karaf component that *end users* can
> use to do Camel and Karaf integration tests.
> The code we have in tests/camel-itest-karaf is for internal usage and testing
> of Camel. The code is not polished and intended for end users.
> We should create a new module for that, and take the good parts of
> camel-itest-karaf and make it user friendly etc. And of course have docs to
> go with as well.
> And when its good, we can use that in camel-itest-karaf also (eat our own dog
> food)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (CAMEL-10802) java.lang.ClassCastException when using FlexibleAggregationStrategy with Spring Boot
[
https://issues.apache.org/jira/browse/CAMEL-10802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-10802:
---
Assignee: Claus Ibsen
> java.lang.ClassCastException when using FlexibleAggregationStrategy with
> Spring Boot
>
>
> Key: CAMEL-10802
> URL: https://issues.apache.org/jira/browse/CAMEL-10802
> Project: Camel
> Issue Type: Bug
> Components: camel-core, camel-spring-boot
>Affects Versions: 2.18.2
> Environment: Windows 10
> Camel 2.18.2
> Spring 4.3.6
> Spring Boot 1.5.1
>Reporter: Giovanni Condello
>Assignee: Claus Ibsen
>Priority: Minor
>
> We are having a strange issue while using the FlexibleAggregationStrategy
> with spring boot. Below is a sample and trivial route I just made up
> to demonstrate the issue:
> {code:java}
> from("direct:should-work")
> .id("should-work")
> .log(LoggingLevel.INFO, "Before the first split the
> body is ${body} and has class ${body.getClass()}")
> .split(body(),
> AggregationStrategies.flexible().pick(body()).accumulateInCollection(LinkedList.class))
> .log(LoggingLevel.INFO, "During the first split the
> body is ${body} and has class ${body.getClass()}")
> .end()
> .log(LoggingLevel.INFO, "Before the second split the
> body is ${body} and has class ${body.getClass()}")
> .split(body(),
> AggregationStrategies.flexible().pick(body()).accumulateInCollection(LinkedList.class))
> .log(LoggingLevel.INFO, "During the second split the
> body is ${body} and has class ${body.getClass()}")
> .end()
> .log(LoggingLevel.INFO, "After the second split the
> body is ${body} and has class ${body.getClass()}")
> {code}
> Along with the relevant unit test:
> {code:java}
>@Test
> public void shouldProduceMessages() throws InterruptedException {
> // we expect that a number of messages is automatic done by the Camel
> // route as it uses a timer to trigger
> NotifyBuilder notify = new
> NotifyBuilder(camelContext).whenDone(1).and().whenExactlyFailed(0).create();
> producerTemplateShouldWork.sendBody(Arrays.asList("FIRST", "SECOND"));
> assertTrue(notify.matches(10, TimeUnit.SECONDS));
> }
> {code}
> The test fails with the following unexpected exception:
> {code}
> java.lang.ClassCastException: Cannot cast java.util.LinkedHashSet to
> java.util.LinkedList
> at java.lang.Class.cast(Class.java:3369) ~[na:1.8.0_111]
> at
> org.apache.camel.util.toolbox.FlexibleAggregationStrategy.safeInsertIntoCollection(FlexibleAggregationStrategy.java:281)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.util.toolbox.FlexibleAggregationStrategy.injectAsCollection(FlexibleAggregationStrategy.java:264)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.util.toolbox.FlexibleAggregationStrategy.aggregate(FlexibleAggregationStrategy.java:235)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.MulticastProcessor.doAggregateInternal(MulticastProcessor.java:942)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.MulticastProcessor.doAggregate(MulticastProcessor.java:924)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.MulticastProcessor.doProcessSequential(MulticastProcessor.java:644)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.MulticastProcessor.process(MulticastProcessor.java:238)
> ~[camel-core-2.18.2.jar:2.18.2]
> at org.apache.camel.processor.Splitter.process(Splitter.java:108)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:542)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
> [camel-core-2.18.2.jar:2.18.2]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:120)
> [camel-core-2.18.2.jar:2.18.2]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:83)
> [camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
> [camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:62)
> [camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
> [camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:97)
> [camel-core-2.18.2.jar:2.18.2]
>
[jira] [Commented] (CAMEL-10849) Salesforce: subscription channel created per component
[
https://issues.apache.org/jira/browse/CAMEL-10849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880926#comment-15880926
]
Sune Keller commented on CAMEL-10849:
-
[~lb] I agree completely. So at the endpoint level, there would only be a
single replayId URI parameter, {{replayId}}, which would override any default
or initial replay IDs. This would only be useful if you're not actually using
the replay functionality, or if you always want to play back the past 24 hours
by setting the value to {{-2}}. Am I missing any other obvious use cases?
> Salesforce: subscription channel created per component
> --
>
> Key: CAMEL-10849
> URL: https://issues.apache.org/jira/browse/CAMEL-10849
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Reporter: Luca Burgazzoli
>Assignee: Zoran Regvart
> Fix For: 2.19.0
>
>
> If I creates two salesforce consumers, I can't set different options per
> channel as the client is configured on component level so i.e. you can't set
> a per channel replay id as only the first one is taken into account:
> {code:java}
> from('salesforce:comments-1?updateTopic=true&sObjectQuery=SELECT Id,
> CommentId__c FROM Comment_Event__c')
>
> .to("log:salesforce-comments?level=INFO&showHeaders=false&multiline=false")
> from('salesforce:comments-2?updateTopic=true&sObjectQuery=SELECT Id FROM
> Case')
>
> .to("log:salesforce-cases?level=INFO&showHeaders=false&multiline=false")
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (CAMEL-6132) camel-test-karaf - To allow end users more easily do Camel and Karaf integration test
[
https://issues.apache.org/jira/browse/CAMEL-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880903#comment-15880903
]
A. Soroka edited comment on CAMEL-6132 at 2/23/17 6:03 PM:
---
I would love to help, and I am currently wresting with getting an example up. I
keep running into errors with JNDI (?!), e.g. as shown below. I have experience
with Camel and Karaf, but it dates from five or more years ago, and times have
changed. I am subclassing {{CamelKarafTestSupport}} and I show below the
stacktrace my current {{@Configuration}} method. (The full code is
[here|https://github.com/ajs6f/fcrepo3-shim].) Any advice much appreciated, and
if I can get a working example I will make a point of at least writing a
tutorial and hopefully sending a PR with whatever improvements I can find. I'm
just stumped by this JNDI business. I think I must be missing something
obvious...
{noformat}
javax.naming.NoInitialContextException: Unable to find the
InitialContextFactory org.apache.camel.util.jndi.CamelInitialContextFactory.
at
org.apache.aries.jndi.ContextHelper.getInitialContext(ContextHelper.java:150)
at
org.apache.aries.jndi.OSGiInitialContextFactoryBuilder.getInitialContext(OSGiInitialContextFactoryBuilder.java:51)
at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
at javax.naming.InitialContext.init(InitialContext.java:244)
at javax.naming.InitialContext.(InitialContext.java:216)
at
org.apache.camel.test.junit4.CamelTestSupport.createJndiContext(CamelTestSupport.java:592)
at
org.apache.camel.test.junit4.CamelTestSupport.createRegistry(CamelTestSupport.java:578)
at
org.apache.camel.test.junit4.CamelTestSupport.createCamelContext(CamelTestSupport.java:572)
at
org.apache.camel.test.junit4.CamelTestSupport.doSetUp(CamelTestSupport.java:278)
at
org.apache.camel.test.junit4.CamelTestSupport.setUp(CamelTestSupport.java:246)
{noformat}
{noformat}
@Configuration
public Option[] config() {
MavenUrlReference camelRepo =
maven().groupId("org.apache.camel.karaf").artifactId("apache-camel")
.classifier("features").type("xml").version(CAMEL_VERSION);
MavenUrlReference jenaRepo =
maven().groupId("org.apache.jena").artifactId("jena-osgi-features")
.classifier("features").type("xml").version("3.2.0");
MavenUrlReference enterpriseRepo =
maven().groupId("org.apache.karaf.features").artifactId("enterprise")
.classifier("features").type("xml").version("4.0.7");
MavenArtifactProvisionOption shim =
mavenBundle().groupId("edu.si").artifactId("fcrepo3-shim-core")
.version("0.0.1-SNAPSHOT").start();
Option[] options = new Option[] { features(enterpriseRepo, "jndi"),
features(jenaRepo, "jena"),
features(camelRepo, "camel-test"), shim };
return ArrayUtils.addAll(configure(), options);
}
{noformat}
was (Author: ajs6f):
I would love to help, and I am currently wresting with getting an example up. I
keep running into errors with JNDI (?!), e.g. as shown below. I have experience
with Camel and Karaf, but it dates from five or more years ago, and times have
changed. I am subclassing {{CamelKarafTestSupport}} and I show below the
stacktrace my current {{@Configuration}} method. (The full code is
[here|https://github.com/ajs6f/fcrepo3-shim]. Any advice much appreciated, and
if I can get a working example I will make a point of at least writing a
tutorial and hopefully sending a PR with whatever improvements I can find. I'm
just stumped by this JNDI business. I think I must be missing something
obvious...
{noformat}
javax.naming.NoInitialContextException: Unable to find the
InitialContextFactory org.apache.camel.util.jndi.CamelInitialContextFactory.
at
org.apache.aries.jndi.ContextHelper.getInitialContext(ContextHelper.java:150)
at
org.apache.aries.jndi.OSGiInitialContextFactoryBuilder.getInitialContext(OSGiInitialContextFactoryBuilder.java:51)
at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
at javax.naming.InitialContext.init(InitialContext.java:244)
at javax.naming.InitialContext.(InitialContext.java:216)
at
org.apache.camel.test.junit4.CamelTestSupport.createJndiContext(CamelTestSupport.java:592)
at
org.apache.camel.test.junit4.CamelTestSupport.createRegistry(CamelTestSupport.java:578)
at
org.apache.camel.test.junit4.CamelTestSupport.createCamelContext(CamelTestSupport.java:572)
at
org.apache.camel.test.junit4.CamelTestSupport.doSetUp(CamelTestSuppor
[jira] [Comment Edited] (CAMEL-6132) camel-test-karaf - To allow end users more easily do Camel and Karaf integration test
[
https://issues.apache.org/jira/browse/CAMEL-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880903#comment-15880903
]
A. Soroka edited comment on CAMEL-6132 at 2/23/17 6:03 PM:
---
I would love to help, and I am currently wresting with getting an example up. I
keep running into errors with JNDI (?!), e.g. as shown below. I have experience
with Camel and Karaf, but it dates from five or more years ago, and times have
changed. I am subclassing {{CamelKarafTestSupport}} and I show below the
stacktrace my current {{@Configuration}} method. (The full code is
[here|https://github.com/ajs6f/fcrepo3-shim]. Any advice much appreciated, and
if I can get a working example I will make a point of at least writing a
tutorial and hopefully sending a PR with whatever improvements I can find. I'm
just stumped by this JNDI business. I think I must be missing something
obvious...
{noformat}
javax.naming.NoInitialContextException: Unable to find the
InitialContextFactory org.apache.camel.util.jndi.CamelInitialContextFactory.
at
org.apache.aries.jndi.ContextHelper.getInitialContext(ContextHelper.java:150)
at
org.apache.aries.jndi.OSGiInitialContextFactoryBuilder.getInitialContext(OSGiInitialContextFactoryBuilder.java:51)
at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
at javax.naming.InitialContext.init(InitialContext.java:244)
at javax.naming.InitialContext.(InitialContext.java:216)
at
org.apache.camel.test.junit4.CamelTestSupport.createJndiContext(CamelTestSupport.java:592)
at
org.apache.camel.test.junit4.CamelTestSupport.createRegistry(CamelTestSupport.java:578)
at
org.apache.camel.test.junit4.CamelTestSupport.createCamelContext(CamelTestSupport.java:572)
at
org.apache.camel.test.junit4.CamelTestSupport.doSetUp(CamelTestSupport.java:278)
at
org.apache.camel.test.junit4.CamelTestSupport.setUp(CamelTestSupport.java:246)
{noformat}
{noformat}
@Configuration
public Option[] config() {
MavenUrlReference camelRepo =
maven().groupId("org.apache.camel.karaf").artifactId("apache-camel")
.classifier("features").type("xml").version(CAMEL_VERSION);
MavenUrlReference jenaRepo =
maven().groupId("org.apache.jena").artifactId("jena-osgi-features")
.classifier("features").type("xml").version("3.2.0");
MavenUrlReference enterpriseRepo =
maven().groupId("org.apache.karaf.features").artifactId("enterprise")
.classifier("features").type("xml").version("4.0.7");
MavenArtifactProvisionOption shim =
mavenBundle().groupId("edu.si").artifactId("fcrepo3-shim-core")
.version("0.0.1-SNAPSHOT").start();
Option[] options = new Option[] { features(enterpriseRepo, "jndi"),
features(jenaRepo, "jena"),
features(camelRepo, "camel-test"), shim };
return ArrayUtils.addAll(configure(), options);
}
{noformat}
was (Author: ajs6f):
I would love to help, and I am currently wresting with getting an example up. I
keep running into errors with JNDI (?!), e.g. as shown below. I have experience
with Camel and Karaf, but it dates from five or more years ago, and times have
changed. I am subclassing {{CamelKarafTestSupport}} and I show below the
stacktrace my current {{@Configuration}} method. Any advice much appreciated,
and if I can get a working example I will make a point of at least writing a
tutorial and hopefully sending a PR with whatever improvements I can find. I'm
just stumped by this JNDI business. I think I must be missing something
obvious...
{noformat}
javax.naming.NoInitialContextException: Unable to find the
InitialContextFactory org.apache.camel.util.jndi.CamelInitialContextFactory.
at
org.apache.aries.jndi.ContextHelper.getInitialContext(ContextHelper.java:150)
at
org.apache.aries.jndi.OSGiInitialContextFactoryBuilder.getInitialContext(OSGiInitialContextFactoryBuilder.java:51)
at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
at javax.naming.InitialContext.init(InitialContext.java:244)
at javax.naming.InitialContext.(InitialContext.java:216)
at
org.apache.camel.test.junit4.CamelTestSupport.createJndiContext(CamelTestSupport.java:592)
at
org.apache.camel.test.junit4.CamelTestSupport.createRegistry(CamelTestSupport.java:578)
at
org.apache.camel.test.junit4.CamelTestSupport.createCamelContext(CamelTestSupport.java:572)
at
org.apache.camel.test.junit4.CamelTestSupport.doSetUp(CamelTestSupport.java:278)
at
org.apache.camel.test.junit4.CamelTestSupp
[jira] [Updated] (CAMEL-10802) java.lang.ClassCastException when using FlexibleAggregationStrategy with Spring Boot
[
https://issues.apache.org/jira/browse/CAMEL-10802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-10802:
Fix Version/s: 2.19.0
2.18.3
> java.lang.ClassCastException when using FlexibleAggregationStrategy with
> Spring Boot
>
>
> Key: CAMEL-10802
> URL: https://issues.apache.org/jira/browse/CAMEL-10802
> Project: Camel
> Issue Type: Bug
> Components: camel-core, camel-spring-boot
>Affects Versions: 2.18.2
> Environment: Windows 10
> Camel 2.18.2
> Spring 4.3.6
> Spring Boot 1.5.1
>Reporter: Giovanni Condello
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.18.3, 2.19.0
>
>
> We are having a strange issue while using the FlexibleAggregationStrategy
> with spring boot. Below is a sample and trivial route I just made up
> to demonstrate the issue:
> {code:java}
> from("direct:should-work")
> .id("should-work")
> .log(LoggingLevel.INFO, "Before the first split the
> body is ${body} and has class ${body.getClass()}")
> .split(body(),
> AggregationStrategies.flexible().pick(body()).accumulateInCollection(LinkedList.class))
> .log(LoggingLevel.INFO, "During the first split the
> body is ${body} and has class ${body.getClass()}")
> .end()
> .log(LoggingLevel.INFO, "Before the second split the
> body is ${body} and has class ${body.getClass()}")
> .split(body(),
> AggregationStrategies.flexible().pick(body()).accumulateInCollection(LinkedList.class))
> .log(LoggingLevel.INFO, "During the second split the
> body is ${body} and has class ${body.getClass()}")
> .end()
> .log(LoggingLevel.INFO, "After the second split the
> body is ${body} and has class ${body.getClass()}")
> {code}
> Along with the relevant unit test:
> {code:java}
>@Test
> public void shouldProduceMessages() throws InterruptedException {
> // we expect that a number of messages is automatic done by the Camel
> // route as it uses a timer to trigger
> NotifyBuilder notify = new
> NotifyBuilder(camelContext).whenDone(1).and().whenExactlyFailed(0).create();
> producerTemplateShouldWork.sendBody(Arrays.asList("FIRST", "SECOND"));
> assertTrue(notify.matches(10, TimeUnit.SECONDS));
> }
> {code}
> The test fails with the following unexpected exception:
> {code}
> java.lang.ClassCastException: Cannot cast java.util.LinkedHashSet to
> java.util.LinkedList
> at java.lang.Class.cast(Class.java:3369) ~[na:1.8.0_111]
> at
> org.apache.camel.util.toolbox.FlexibleAggregationStrategy.safeInsertIntoCollection(FlexibleAggregationStrategy.java:281)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.util.toolbox.FlexibleAggregationStrategy.injectAsCollection(FlexibleAggregationStrategy.java:264)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.util.toolbox.FlexibleAggregationStrategy.aggregate(FlexibleAggregationStrategy.java:235)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.MulticastProcessor.doAggregateInternal(MulticastProcessor.java:942)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.MulticastProcessor.doAggregate(MulticastProcessor.java:924)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.MulticastProcessor.doProcessSequential(MulticastProcessor.java:644)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.MulticastProcessor.process(MulticastProcessor.java:238)
> ~[camel-core-2.18.2.jar:2.18.2]
> at org.apache.camel.processor.Splitter.process(Splitter.java:108)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:542)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
> [camel-core-2.18.2.jar:2.18.2]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:120)
> [camel-core-2.18.2.jar:2.18.2]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:83)
> [camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
> [camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:62)
> [camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
> [camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(Delegat
[jira] [Commented] (CAMEL-6132) camel-test-karaf - To allow end users more easily do Camel and Karaf integration test
[ https://issues.apache.org/jira/browse/CAMEL-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880964#comment-15880964 ] Quinn Stevenson commented on CAMEL-6132: Claus is correct in the statement that this still needs quite a bit of love. I started it by combining on what was already in the Camel codeline with some stuff I'd done for a customer, and I ran out of time before I got very far. I'd love to have some help on this one - I'll see if I can pull your example (or find the one I had), but it may take me a few days (kinda busy with customers right now). > camel-test-karaf - To allow end users more easily do Camel and Karaf > integration test > - > > Key: CAMEL-6132 > URL: https://issues.apache.org/jira/browse/CAMEL-6132 > Project: Camel > Issue Type: New Feature > Components: karaf >Reporter: Claus Ibsen >Assignee: Quinn Stevenson > Fix For: 2.19.0 > > > We should introduce a proper camel-test-karaf component that *end users* can > use to do Camel and Karaf integration tests. > The code we have in tests/camel-itest-karaf is for internal usage and testing > of Camel. The code is not polished and intended for end users. > We should create a new module for that, and take the good parts of > camel-itest-karaf and make it user friendly etc. And of course have docs to > go with as well. > And when its good, we can use that in camel-itest-karaf also (eat our own dog > food) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (CAMEL-10888) camel-spring-ws - Has problem with returning proper response due invalid IN vs OUT code
Claus Ibsen created CAMEL-10888: --- Summary: camel-spring-ws - Has problem with returning proper response due invalid IN vs OUT code Key: CAMEL-10888 URL: https://issues.apache.org/jira/browse/CAMEL-10888 Project: Camel Issue Type: Bug Components: camel-spring-ws Reporter: Claus Ibsen Fix For: 2.18.3, 2.19.0 See SO http://stackoverflow.com/questions/42385355/apache-camel-spring-webservices-springwebserviceconsumer-does-not-read-answer-fr -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (CAMEL-10802) java.lang.ClassCastException when using FlexibleAggregationStrategy with Spring Boot
[
https://issues.apache.org/jira/browse/CAMEL-10802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-10802.
-
Resolution: Fixed
Thanks for the test project
> java.lang.ClassCastException when using FlexibleAggregationStrategy with
> Spring Boot
>
>
> Key: CAMEL-10802
> URL: https://issues.apache.org/jira/browse/CAMEL-10802
> Project: Camel
> Issue Type: Bug
> Components: camel-core, camel-spring-boot
>Affects Versions: 2.18.2
> Environment: Windows 10
> Camel 2.18.2
> Spring 4.3.6
> Spring Boot 1.5.1
>Reporter: Giovanni Condello
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.18.3, 2.19.0
>
>
> We are having a strange issue while using the FlexibleAggregationStrategy
> with spring boot. Below is a sample and trivial route I just made up
> to demonstrate the issue:
> {code:java}
> from("direct:should-work")
> .id("should-work")
> .log(LoggingLevel.INFO, "Before the first split the
> body is ${body} and has class ${body.getClass()}")
> .split(body(),
> AggregationStrategies.flexible().pick(body()).accumulateInCollection(LinkedList.class))
> .log(LoggingLevel.INFO, "During the first split the
> body is ${body} and has class ${body.getClass()}")
> .end()
> .log(LoggingLevel.INFO, "Before the second split the
> body is ${body} and has class ${body.getClass()}")
> .split(body(),
> AggregationStrategies.flexible().pick(body()).accumulateInCollection(LinkedList.class))
> .log(LoggingLevel.INFO, "During the second split the
> body is ${body} and has class ${body.getClass()}")
> .end()
> .log(LoggingLevel.INFO, "After the second split the
> body is ${body} and has class ${body.getClass()}")
> {code}
> Along with the relevant unit test:
> {code:java}
>@Test
> public void shouldProduceMessages() throws InterruptedException {
> // we expect that a number of messages is automatic done by the Camel
> // route as it uses a timer to trigger
> NotifyBuilder notify = new
> NotifyBuilder(camelContext).whenDone(1).and().whenExactlyFailed(0).create();
> producerTemplateShouldWork.sendBody(Arrays.asList("FIRST", "SECOND"));
> assertTrue(notify.matches(10, TimeUnit.SECONDS));
> }
> {code}
> The test fails with the following unexpected exception:
> {code}
> java.lang.ClassCastException: Cannot cast java.util.LinkedHashSet to
> java.util.LinkedList
> at java.lang.Class.cast(Class.java:3369) ~[na:1.8.0_111]
> at
> org.apache.camel.util.toolbox.FlexibleAggregationStrategy.safeInsertIntoCollection(FlexibleAggregationStrategy.java:281)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.util.toolbox.FlexibleAggregationStrategy.injectAsCollection(FlexibleAggregationStrategy.java:264)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.util.toolbox.FlexibleAggregationStrategy.aggregate(FlexibleAggregationStrategy.java:235)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.MulticastProcessor.doAggregateInternal(MulticastProcessor.java:942)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.MulticastProcessor.doAggregate(MulticastProcessor.java:924)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.MulticastProcessor.doProcessSequential(MulticastProcessor.java:644)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.MulticastProcessor.process(MulticastProcessor.java:238)
> ~[camel-core-2.18.2.jar:2.18.2]
> at org.apache.camel.processor.Splitter.process(Splitter.java:108)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:542)
> ~[camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
> [camel-core-2.18.2.jar:2.18.2]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:120)
> [camel-core-2.18.2.jar:2.18.2]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:83)
> [camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
> [camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:62)
> [camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
> [camel-core-2.18.2.jar:2.18.2]
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(Delega
[jira] [Commented] (CAMEL-6132) camel-test-karaf - To allow end users more easily do Camel and Karaf integration test
[ https://issues.apache.org/jira/browse/CAMEL-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880970#comment-15880970 ] Claus Ibsen commented on CAMEL-6132: JndiContext comes from when using DefaultCamelContext that uses JNDI as registry by default. Somewhere that camel-test-karaf module needs to setup a OSGi based CamelContext (typically using blueprint or something). > camel-test-karaf - To allow end users more easily do Camel and Karaf > integration test > - > > Key: CAMEL-6132 > URL: https://issues.apache.org/jira/browse/CAMEL-6132 > Project: Camel > Issue Type: New Feature > Components: karaf >Reporter: Claus Ibsen >Assignee: Quinn Stevenson > Fix For: 2.19.0 > > > We should introduce a proper camel-test-karaf component that *end users* can > use to do Camel and Karaf integration tests. > The code we have in tests/camel-itest-karaf is for internal usage and testing > of Camel. The code is not polished and intended for end users. > We should create a new module for that, and take the good parts of > camel-itest-karaf and make it user friendly etc. And of course have docs to > go with as well. > And when its good, we can use that in camel-itest-karaf also (eat our own dog > food) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CAMEL-10888) camel-spring-ws - Has problem with returning proper response due invalid IN vs OUT code
[ https://issues.apache.org/jira/browse/CAMEL-10888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-10888: Estimated Complexity: Novice (was: Unknown) > camel-spring-ws - Has problem with returning proper response due invalid IN > vs OUT code > --- > > Key: CAMEL-10888 > URL: https://issues.apache.org/jira/browse/CAMEL-10888 > Project: Camel > Issue Type: Bug > Components: camel-spring-ws >Reporter: Claus Ibsen > Fix For: 2.18.3, 2.19.0 > > > See SO > http://stackoverflow.com/questions/42385355/apache-camel-spring-webservices-springwebserviceconsumer-does-not-read-answer-fr -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-10883) Support HTTP 1.1 continue in Undertow
[ https://issues.apache.org/jira/browse/CAMEL-10883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880999#comment-15880999 ] ASF GitHub Bot commented on CAMEL-10883: Github user RohanHart closed the pull request at: https://github.com/apache/camel/pull/1482 > Support HTTP 1.1 continue in Undertow > - > > Key: CAMEL-10883 > URL: https://issues.apache.org/jira/browse/CAMEL-10883 > Project: Camel > Issue Type: Improvement > Components: camel-undertow >Affects Versions: 2.19.0 >Reporter: Rohan Hart >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 2.19.0 > > > Adding support for "continue" processing in Undertow is trivially done in > UndertowConsumer. > However, the processing of delayed payloads could truncate the data - for me > this happened reliably if the payload was more than 16KB. This has been > replaced by a standard blocking channel which supports the processing > expectations of Undertow's HttpServerExchange. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-6132) camel-test-karaf - To allow end users more easily do Camel and Karaf integration test
[ https://issues.apache.org/jira/browse/CAMEL-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15881051#comment-15881051 ] A. Soroka commented on CAMEL-6132: -- [~hqstevenson], thank you for any time you are willing to spend with this! [~cib...@e-ma.net], thanks for the pointer! I will try to override whatever behavior is currently setting up the Camel Context and see if I can make some progress that way. > camel-test-karaf - To allow end users more easily do Camel and Karaf > integration test > - > > Key: CAMEL-6132 > URL: https://issues.apache.org/jira/browse/CAMEL-6132 > Project: Camel > Issue Type: New Feature > Components: karaf >Reporter: Claus Ibsen >Assignee: Quinn Stevenson > Fix For: 2.19.0 > > > We should introduce a proper camel-test-karaf component that *end users* can > use to do Camel and Karaf integration tests. > The code we have in tests/camel-itest-karaf is for internal usage and testing > of Camel. The code is not polished and intended for end users. > We should create a new module for that, and take the good parts of > camel-itest-karaf and make it user friendly etc. And of course have docs to > go with as well. > And when its good, we can use that in camel-itest-karaf also (eat our own dog > food) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (CAMEL-6132) camel-test-karaf - To allow end users more easily do Camel and Karaf integration test
[
https://issues.apache.org/jira/browse/CAMEL-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15881051#comment-15881051
]
A. Soroka edited comment on CAMEL-6132 at 2/23/17 7:14 PM:
---
[~hqstevenson], thank you for any time you are willing to spend with this!
[~cib...@e-ma.net], thanks for the pointer! I will try to override whatever
behavior is currently setting up the {{CamelContext}} and see if I can make
some progress that way.
was (Author: ajs6f):
[~hqstevenson], thank you for any time you are willing to spend with this!
[~cib...@e-ma.net], thanks for the pointer! I will try to override whatever
behavior is currently setting up the Camel Context and see if I can make some
progress that way.
> camel-test-karaf - To allow end users more easily do Camel and Karaf
> integration test
> -
>
> Key: CAMEL-6132
> URL: https://issues.apache.org/jira/browse/CAMEL-6132
> Project: Camel
> Issue Type: New Feature
> Components: karaf
>Reporter: Claus Ibsen
>Assignee: Quinn Stevenson
> Fix For: 2.19.0
>
>
> We should introduce a proper camel-test-karaf component that *end users* can
> use to do Camel and Karaf integration tests.
> The code we have in tests/camel-itest-karaf is for internal usage and testing
> of Camel. The code is not polished and intended for end users.
> We should create a new module for that, and take the good parts of
> camel-itest-karaf and make it user friendly etc. And of course have docs to
> go with as well.
> And when its good, we can use that in camel-itest-karaf also (eat our own dog
> food)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (CAMEL-6132) camel-test-karaf - To allow end users more easily do Camel and Karaf integration test
[
https://issues.apache.org/jira/browse/CAMEL-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15881051#comment-15881051
]
A. Soroka edited comment on CAMEL-6132 at 2/23/17 7:28 PM:
---
[~hqstevenson], thank you for any time you are willing to spend with this!
[~davsclaus], thanks for the pointer! I will try to override whatever behavior
is currently setting up the {{CamelContext}} and see if I can make some
progress that way.
was (Author: ajs6f):
[~hqstevenson], thank you for any time you are willing to spend with this!
[~cib...@e-ma.net], thanks for the pointer! I will try to override whatever
behavior is currently setting up the {{CamelContext}} and see if I can make
some progress that way.
> camel-test-karaf - To allow end users more easily do Camel and Karaf
> integration test
> -
>
> Key: CAMEL-6132
> URL: https://issues.apache.org/jira/browse/CAMEL-6132
> Project: Camel
> Issue Type: New Feature
> Components: karaf
>Reporter: Claus Ibsen
>Assignee: Quinn Stevenson
> Fix For: 2.19.0
>
>
> We should introduce a proper camel-test-karaf component that *end users* can
> use to do Camel and Karaf integration tests.
> The code we have in tests/camel-itest-karaf is for internal usage and testing
> of Camel. The code is not polished and intended for end users.
> We should create a new module for that, and take the good parts of
> camel-itest-karaf and make it user friendly etc. And of course have docs to
> go with as well.
> And when its good, we can use that in camel-itest-karaf also (eat our own dog
> food)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (CAMEL-6132) camel-test-karaf - To allow end users more easily do Camel and Karaf integration test
[
https://issues.apache.org/jira/browse/CAMEL-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15881085#comment-15881085
]
A. Soroka commented on CAMEL-6132:
--
[~davsclaus], success! Thanks for the pointer! I overrode:
{noformat}
@Override
protected CamelContext createCamelContext() {
return new OsgiDefaultCamelContext(bundleContext);
}
{noformat}
and added {{camel-core-osgi}}
{noformat}
MavenArtifactProvisionOption camelOsgi =
mavenBundle().groupId("org.apache.camel").artifactId("camel-core-osgi")
.version("2.18.2").start();
{noformat}
to the mix. I think that bundle should be part of the "default" results of
{{org.apache.camel.test.karaf.AbstractFeatureTest.configure(String...)}}. I
will send a PR with these changes, for your consideration. Now on to writing
some tests-- I'm sure I will have more questions but I will take them to the
lists.
Thanks!
> camel-test-karaf - To allow end users more easily do Camel and Karaf
> integration test
> -
>
> Key: CAMEL-6132
> URL: https://issues.apache.org/jira/browse/CAMEL-6132
> Project: Camel
> Issue Type: New Feature
> Components: karaf
>Reporter: Claus Ibsen
>Assignee: Quinn Stevenson
> Fix For: 2.19.0
>
>
> We should introduce a proper camel-test-karaf component that *end users* can
> use to do Camel and Karaf integration tests.
> The code we have in tests/camel-itest-karaf is for internal usage and testing
> of Camel. The code is not polished and intended for end users.
> We should create a new module for that, and take the good parts of
> camel-itest-karaf and make it user friendly etc. And of course have docs to
> go with as well.
> And when its good, we can use that in camel-itest-karaf also (eat our own dog
> food)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (CAMEL-10849) Salesforce: subscription channel created per component
[
https://issues.apache.org/jira/browse/CAMEL-10849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15881096#comment-15881096
]
Dhiraj Bokde commented on CAMEL-10849:
--
IIRC, the way that field was set was at the client level, which is wrong, it
should really be just added to a map that the SF extension should then use. Or
it could be an endpoint property, which I think you are making it now. That
should be the only change required, since the SF extension does use a map from
what I recall.
> Salesforce: subscription channel created per component
> --
>
> Key: CAMEL-10849
> URL: https://issues.apache.org/jira/browse/CAMEL-10849
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Reporter: Luca Burgazzoli
>Assignee: Zoran Regvart
> Fix For: 2.19.0
>
>
> If I creates two salesforce consumers, I can't set different options per
> channel as the client is configured on component level so i.e. you can't set
> a per channel replay id as only the first one is taken into account:
> {code:java}
> from('salesforce:comments-1?updateTopic=true&sObjectQuery=SELECT Id,
> CommentId__c FROM Comment_Event__c')
>
> .to("log:salesforce-comments?level=INFO&showHeaders=false&multiline=false")
> from('salesforce:comments-2?updateTopic=true&sObjectQuery=SELECT Id FROM
> Case')
>
> .to("log:salesforce-cases?level=INFO&showHeaders=false&multiline=false")
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (CAMEL-10888) camel-spring-ws - Has problem with returning proper response due invalid IN vs OUT code
[ https://issues.apache.org/jira/browse/CAMEL-10888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin reassigned CAMEL-10888: Assignee: onder sezgin > camel-spring-ws - Has problem with returning proper response due invalid IN > vs OUT code > --- > > Key: CAMEL-10888 > URL: https://issues.apache.org/jira/browse/CAMEL-10888 > Project: Camel > Issue Type: Bug > Components: camel-spring-ws >Reporter: Claus Ibsen >Assignee: onder sezgin > Fix For: 2.18.3, 2.19.0 > > > See SO > http://stackoverflow.com/questions/42385355/apache-camel-spring-webservices-springwebserviceconsumer-does-not-read-answer-fr -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (CAMEL-10889) camel-telegram and html styled messages
Jörg Larbig created CAMEL-10889: --- Summary: camel-telegram and html styled messages Key: CAMEL-10889 URL: https://issues.apache.org/jira/browse/CAMEL-10889 Project: Camel Issue Type: New Feature Affects Versions: 2.18.2 Reporter: Jörg Larbig camel-telegram component should support the Formatting options from the bot api https://core.telegram.org/bots/api to be able to send formatted messages (in my case HTML style) Please also add camel-telegram to the components list in Jira -- This message was sent by Atlassian JIRA (v6.3.15#6346)
