All,
I'm trying to modify the below code to use a self signed of CA signed
certificate with a jetty endpoint. I've gotten it to work with a key that I
generated and I'm prompted to accept the certificate manually. However I
need it to work in either circumstance without any manual intervention.
I have written a simple Spring DSL route to make an HTTP Get Call, which
sends 2 parameters and returns a list of results. This works!!
I then copy the same code to a bigger Context and get an HTTP 400 error. The
original route works with a simple
http://myapp.rhcloud.com/TestDB-1/GetEvents?spo
I'm afraid you have to share the project then ;)
regards
Grzegorz
2015-10-09 16:43 GMT+02:00 Arnaud Deprez :
> No I got the same behaviour with camel 2.16-SNAPSHOT :-(
>
> On Fri, Oct 9, 2015 at 4:21 PM Grzegorz Grzybek
> wrote:
>
>> Hi
>>
>> for camel-2.15.2 you have
>> "com.googlecode.pojosr:d
No I got the same behaviour with camel 2.16-SNAPSHOT :-(
On Fri, Oct 9, 2015 at 4:21 PM Grzegorz Grzybek
wrote:
> Hi
>
> for camel-2.15.2 you have
> "com.googlecode.pojosr:de.kalpatec.pojosr.framework:jar:0.2.1:test"
> dependency - which isn't stable.
> for camel-2.16 it looks fine -
> "org.apac
Hi Antonin,
thanks for your answer.
I modified the example slightly. Please see
https://github.com/claudiusb/camel-threads-problem-reproducer/commit/9c09201e54513a36e3b1bb6c325689cfe09bdb5f
You are right, if the size of the producing thread pool is increased to be
greater than the queue size of
Hi
for camel-2.15.2 you have
"com.googlecode.pojosr:de.kalpatec.pojosr.framework:jar:0.2.1:test"
dependency - which isn't stable.
for camel-2.16 it looks fine -
"org.apache.felix:org.apache.felix.connect:jar:0.1.0:test" and
"org.apache.aries.blueprint:org.apache.aries.blueprint.core:jar:1.4.4:test
Hi again,
I've posted my dependency tree there
http://camel.465427.n5.nabble.com/VOTE-Camel-2-16-0-td5772119i20.html.
I may do something wrong but I just read the source code of the pom here
https://repo1.maven.org/maven2/org/apache/camel/camel-test-blueprint/2.15.2/camel-test-blueprint-2.15.2.po
I'm upgrading from *camel-netty* to *camel-netty4* and I see there are lots
of API changes. Currently, with *camel-netty*, I have a route that consumes
from *netty:udp* and a *ServerPipelineFactory *that has a *UdpPacketDecoder
*that is working fine. The idea is to detect and fire a message upstr
I am using the camel zookeeper, and able to get the data of the znode but not
able to create it if does not exist. In logs able to see that "node do not
exist. creating it" but same znode is not available in zookeeper.
from("direct:start")
.to("zookeeper://localhost:2181/path1/child1/test.txt?
Hi Hubertus,
the Stream Caches and their corresponding files are closed/deleted at
the end of the route, because it could be that some processor in the
route still needs the stream. Maybe it helps in your case to increase
the threshold so that only the first big file 400 MB is written into
the fil
Hi,
Non-ASCII characters with MIME headers is always a bit difficult. You could try
to use
in.addAttachment(javax.mail.internet.MimeUtility.encodeText("\u041f\u0440\u0438\u0432\u0435\u0442",
"UTF-8", null), new
DataHandler(data, "application/vnd.ms-excel"));
This may or may not work with your ma
Hi
Thanks for reporting.
You are very welcome to log a JIRA and provide a patch
http://camel.apache.org/support.html
We love contributions
http://camel.apache.org/contributing.html
On Fri, Oct 9, 2015 at 9:22 AM, Martin Scheffler
wrote:
> Hi all,
>
> I tried enabling CORS for our camel REST en
Hi all,
I tried enabling CORS for our camel REST endpoint and it does not really
work.
The Access-Control-Allow-Origin header is sent, as it should be.
Unfortunately the value of the header is "*, *" which is not accepted as
correct by newer browser versions.
Firefox 41.0.1 and Chrome 45.0 both re
13 matches
Mail list logo
