Github user yuruki closed the pull request at:
https://github.com/apache/camel/pull/760
---
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 enabl
Github user yuruki closed the pull request at:
https://github.com/apache/camel/pull/773
---
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 enabl
Apache Camel's XStream usage is vulnerable to Remote Code Execution attacks
Apache Camel's camel-xstream component is vulnerable to Java object
de-serialisation vulnerability.
Such as de-serializing untrusted data can lead to security flaws as
demonstrated in various similar reports about Java de-
In an attempt to get the Camel Context I did the following in the scala
project.
In application.conf I added
akka.camel.context-provider="com.utility.MyContextProvider"
I then created a new class in the scala file.
@Component
final class MyContextProvider extends ContextProvider {
@Autowir
Another option;
If I reverse the call in my Scala application to be
val camel = CamelExtension(actorSystem).context
SpringApplication.run(classOf[Application]) // Call the Java
Spring Boot dependent jar file to host the endpoints.
actorSystem.actorOf(Props(classOf[CamelSer
I'd love to see use of Optional at least in the Message and Exchange
interfaces.
On 29 January 2016 at 13:38, Johan Edstrom wrote:
> Dan, I like that!
>
> /je
> > On Jan 29, 2016, at 12:30 PM, James Carman
> wrote:
> >
> > Proper Java8 support could give us quite an opportunity here. Marking ou
Dan, I like that!
/je
> On Jan 29, 2016, at 12:30 PM, James Carman wrote:
>
> Proper Java8 support could give us quite an opportunity here. Marking our
> interfaces as functional (not required of course) and designing our API to
> be "lambda-friendly"
>
> On Fri, Jan 29, 2016 at 8:24 AM Daniel
Proper Java8 support could give us quite an opportunity here. Marking our
interfaces as functional (not required of course) and designing our API to
be "lambda-friendly"
On Fri, Jan 29, 2016 at 8:24 AM Daniel Kulp wrote:
> THAT said, I would be OK with going through all the code, removing all th
GitHub user astefanutti opened a pull request:
https://github.com/apache/camel/pull/821
XML JSON Data Format Asciidoc documentation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/astefanutti/camel camel-xmljson
Alternatively yo
GitHub user astefanutti opened a pull request:
https://github.com/apache/camel/pull/820
REST DSL with CDI example
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/astefanutti/camel rest-cdi
Alternatively you can review and apply
Github user sebi-hgdata closed the pull request at:
https://github.com/apache/camel/pull/817
---
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
Hi all, first time poster here and a first time user of Camel
I have a working Spring Boot service developed using the example provided
here https://spring.io/guides/gs/producing-web-service/
I built a web service from a provided WSDL file. The service needed to
support SOAP12 as shown in the c
Github user lburgazzoli closed the pull request at:
https://github.com/apache/camel/pull/818
---
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
GitHub user lburgazzoli opened a pull request:
https://github.com/apache/camel/pull/819
CAMEL-9542 - add labels to new options
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lburgazzoli/apache-camel CAMEL-9542-labels
Alternativ
GitHub user lburgazzoli opened a pull request:
https://github.com/apache/camel/pull/818
CAMEL-9542 - Allow HttpClient configuration (proxy, connection poolinâ¦
â¦g, etc) for camel-geocoder component
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user sebi-hgdata opened a pull request:
https://github.com/apache/camel/pull/817
Fix if allowable values are not set
We should not set 'enum' field in parameter if allowable values are empty
as it makes swagger ui unusable by not allowing parameter inputs. (for all
parameter
+1 for removing everything marked deprecated, upgrading to Java 8, and
calling that version 3.0 then.
On Fri, Jan 29, 2016 at 2:23 PM, Daniel Kulp wrote:
> THAT said, I would be OK with going through all the code, removing all the
> stuff marked deprecated, update to JDK8, and call it 3.0. :-
Thanks Raul, I will go further and merge my implementation to master.
Before that I will see what ideas I can take from your branch.
Going forward, we may have to consdier what new versions of Java is
bringing to the table for Camel Java DSL in general anyway.
Cheers,
On 28 January 2016 at 14:12
Hi
Good to hear that you guys will pickup this and work on a
camel-hystrix component.
I agree with Bilgin that the component should be similar to how you
use all the other components using the endpoints and how they are
configured.
PS: Another cool component would be a Apache Storm component.
O
THAT said, I would be OK with going through all the code, removing all the
stuff marked deprecated, update to JDK8, and call it 3.0. :-) It’s just a
version number. We can always do a 4.0 if needed/wanted.
Dan
> On Jan 29, 2016, at 8:21 AM, Daniel Kulp wrote:
>
>>
>> On Jan 29, 201
> On Jan 29, 2016, at 3:21 AM, Christian Müller
> wrote:
>
> Yes, it's a minor release. And regarding to [1]:
>
> MINOR version when you add functionality in a backwards-compatible manner
>
> And that's not the case, if you have to upgrade your JRE.
How is it not backwards compatible? All o
Hi Christian,
But if we follow this rule literally, we would need to bump the major
version every time when we do a minor release like we do now. In each
minor release, we are introducing a bunch of binary incompatibilities
that require updates of the underlining libraries. The servers
document[1]
Yes, it's a minor release. And regarding to [1]:
MINOR version when you add functionality in a backwards-compatible manner
And that's not the case, if you have to upgrade your JRE.
[1] http://semver.org/
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apac
23 matches
Mail list logo
