Github user onders86 closed the pull request at:
https://github.com/apache/camel/pull/1550
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is en
GitHub user igarashitm opened a pull request:
https://github.com/apache/camel/pull/1561
CAMEL-10885 Add mask option to log EIP
Introduced a StringFormatter interface to plugin a formatter into the Log
EIP processor. MaskingStringFormatter is the implementation which masks
sensitive
The Apache Jenkins build system has built Camel.2.17.x.notest (build #195)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.2.17.x.notest/195/
to view the results.
Hi,
I am trying to call soap web service from my rest java DSL but its giving me
server error. below is my code and error.
I will receive request as rest with json data and I need to call soap
service, process the data and return the response in json to my client.
Please help me. thanks in advanc
Github user objectiser closed the pull request at:
https://github.com/apache/camel/pull/1559
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
+1
---
Luca Burgazzoli
On Thu, Mar 16, 2017 at 8:16 PM, Claus Ibsen wrote:
> Hi
>
> I wonder if we shall deprecate more stuff on OSGi as its one of the
> most problematic platforms to support.
>
> Ideally only OSGi Blueprint is the best supported we have.
>
> We should consider deprecating on
Hi
There is also the old camel-servletlistener module which was intended
for users on WAR files whom didnt want to use spring xml to bootstrap
Camel.
https://github.com/apache/camel/blob/master/components/camel-servletlistener/src/main/docs/servletlistener.adoc
In today a modern WAR can deploy us
Camel 2.18.3 seems to have upgraded most camel modules to spring 4.
The only exemption is the camel-spring-dm feature which depends on
spring < 4.
As far as I know this causes camel 2.18.3 to not work on karaf when
using camel-spring-dm with any of the other camel modules that require
spring
GitHub user dmvolod opened a pull request:
https://github.com/apache/camel/pull/1562
CAMEL-11056: Create a new camel-olingo4 component for supporting OData 4.0
This is a new camel-olingo4 component which supports OData 4.0 protocol via
Olingo4 library.
It's was migrated from cam
Github user mluckam closed the pull request at:
https://github.com/apache/camel/pull/1558
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
GitHub user dmvolod opened a pull request:
https://github.com/apache/camel/pull/1563
CAMEL-11058: camel-olingo2 component doesn't support OData 3.0
Component camel-olingo2 doesn't support OData 3.0 as olingo-odata2 library
never did it.
It would be nice to remove this info (ODat
Github user dmvolod closed the pull request at:
https://github.com/apache/camel/pull/1563
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
GitHub user dmvolod opened a pull request:
https://github.com/apache/camel/pull/1564
CAMEL-11058: Remove OData 3.0 version info from the camel-olingo2
Component camel-olingo2 doesn't support OData 3.0 as olingo-odata2 library
never did it.
It would be nice to remove this info (O
I think you can run camel-spring-dm and maybe not install components
that require Spring 4.x etc and then do some limited Camel application
on the legacy Spring DM. Or in theory have spring 3.x and 4.x run side
by side (osgi versioning) and have it somehow work. But hey f...
spring-dm is not good i
The Apache Jenkins build system has built Camel.trunk.notest (build #3070)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3070/
to view the results.
I also think removing spring dm for camel 2.19 is a good idea.
Currently people just mix camel-spring-dm with any other camel features
and expect it to work. So they can only be disappointed.
Christian
On 23.03.2017 17:50, Claus Ibsen wrote:
I think you can run camel-spring-dm and maybe not i
The Apache Jenkins build system has built Camel.trunk.notest (build #3071)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3071/
to view the results.
Logged a ticket
https://issues.apache.org/jira/browse/CAMEL-11059
On Thu, Mar 23, 2017 at 6:01 PM, Christian Schneider
wrote:
> I also think removing spring dm for camel 2.19 is a good idea.
> Currently people just mix camel-spring-dm with any other camel features and
> expect it to work. So they
Hi
Some time ago I created a camel component for PubNub in the Rhiot project.
https://github.com/rhiot/rhiot/tree/master/datastream/components/camel-pubnub
The Rhiot project is no longer maintained, so I was thinking if it would
make any sense to polish the component, and move it to the apache ca
GitHub user blove319 opened a pull request:
https://github.com/apache/camel/pull/1565
Prj keep alive
Problem:
When using failover in queue consumption, if a connection is bumped to
another broker then the session in SjmsBatchConsumer becomes invalid and an
IllegalStateException
The Apache Jenkins build system has built Camel.trunk.notest (build #3072)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3072/
to view the results.
Hello,
I've recently worked on some examples related to the service-call eip
using undertow as underlying component to see how complex is to go
beyond the defaults and it worked nice, the only downside is that you
cannot simply swap the component as undertow expect also the protocol
(http/https) t
22 matches
Mail list logo
