Wow .. you invested some time in that story below :-)
The problem is that it is not the true story.
Let´s say we are on 2.8.x. If we neeed bug fixes only then we upgrade to
a higher bug fix version. In this version there will be no functional
changes so no problems should
occur.
If we move
[
https://issues.apache.org/jira/browse/CAMEL-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved CAMEL-4415.
-
Resolution: Fixed
Revision 1165563.
> Use Karaf new spring features
> --
[
https://issues.apache.org/jira/browse/CAMEL-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-4416 started by Jean-Baptiste Onofré.
> Upgrade to Spring 3.0.6.RELEASE
> ---
>
> Key: CAMEL-4416
>
[
https://issues.apache.org/jira/browse/CAMEL-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097850#comment-13097850
]
Jonas Bengtsson commented on CAMEL-4213:
It works with 2.9-SNAPSHOT! I also tried
Hi All,
the use-case Claus gave as an example in his last post indeed happened today
morning with my client to whom I've provided the application (running stable
since July 27th with camel 2.8.0 in the production).
I wanted to give a try to the snapshot build of today morning at [1], and
followin
Hi bvahdat,
this is important feedback. Can you give me the compile failures. I will
make sure this will be compatible.
We are currently at a snapshot. So stuff is not in release quality. Btw.
this is why I would like to do a release candidate.
It is great you already tested this but many peopl
Hello
Could I use jetty and http4 to do redirect request.
My goal : have an http server via camel jetty and send the received request
via a proxy to the net.
http://localhost:/test/"/>
Could it be running?
Valery
--
View this message in context:
htt
Btw. I just compiled the unchanged camel-extra components against my
current camel trunk and they showed no compile or test failures.
So I hope we can fix the problem you see quite fast.
Christian
Am 06.09.2011 12:50, schrieb Christian Schneider:
Hi bvahdat,
this is important feedback. Can y
You may need to enable the bridgeEndpoint on the Jetty endpoint like
this
from("jetty:http://localhost:/test/?bridgeEndpoint=true";).to("http4:xxx");
On Tue Sep 6 18:52:11 2011, v.de...@gmail.com wrote:
Hello
Could I use jetty and http4 to do redirect request.
My goal : have an http serv
[
https://issues.apache.org/jira/browse/CAMEL-4412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-4412.
-
Resolution: Fixed
Applied patch into trunk and camel 2.8.x branch.
> ServletEndpoint doesn't sup
[
https://issues.apache.org/jira/browse/CAMEL-4363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097977#comment-13097977
]
Willem Jiang commented on CAMEL-4363:
-
I just did some test on the current Jetty compo
Hi
Still with the redirection that I am trying to do with Http4
http://localhost:/test/?bridgeEndpoint=true"/>
do you know why I have "The reference to entity "proxyPort" must end with
the ';' delimiter" as error? during the parsing of Camelcontext?
thks
Valery
--
View this m
[
https://issues.apache.org/jira/browse/CAMEL-4363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-4363.
-
Resolution: Won't Fix
Current there is no solution for it.
> Allow for static file handlers to b
[
https://issues.apache.org/jira/browse/CAMEL-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved CAMEL-4416.
-
Resolution: Fixed
Revision 1165658.
> Upgrade to Spring 3.0.6.RELEASE
>
camel-hazelcast should allow the user to provide an existing instance to the
component
--
Key: CAMEL-4418
URL: https://issues.apache.org/jira/browse/CAMEL-4418
Projec
[
https://issues.apache.org/jira/browse/CAMEL-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ioannis Canellos updated CAMEL-4418:
Attachment: CAMEL-4418-patch.txt
I am attaching a patch which changes the hazelcast compone
[
https://issues.apache.org/jira/browse/CAMEL-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ioannis Canellos updated CAMEL-4418:
Description: The camel-hazelcast component currently is using Hazelcast
default instance. I
You can find the answer here[1]
BTW, please ask this kind of question in the camel-user mailing list.
[1]http://camel.apache.org/how-do-i-use-uris-with-parameters-in-xml.html
On Tue Sep 6 21:15:11 2011, v.de...@gmail.com wrote:
Hi
Still with the redirection that I am trying to do with Http4
Upgrade to CXF 2.4.3
Key: CAMEL-4419
URL: https://issues.apache.org/jira/browse/CAMEL-4419
Project: Camel
Issue Type: Task
Components: camel-cxf
Reporter: Jean-Baptiste Onofré
Assignee:
[
https://issues.apache.org/jira/browse/CAMEL-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-4419 started by Jean-Baptiste Onofré.
> Upgrade to CXF 2.4.3
>
>
> Key: CAMEL-4419
> URL: https://issue
[
https://issues.apache.org/jira/browse/CAMEL-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098020#comment-13098020
]
Willem Jiang commented on CAMEL-4213:
-
This issue may be fixed by CAMEL-4347.
> camel
On Friday, September 02, 2011 3:06:28 AM hadr...@apache.org wrote:
> Author: hadrian
> Date: Fri Sep 2 03:06:28 2011
> New Revision: 1164338
>
> URL: http://svn.apache.org/viewvc?rev=1164338&view=rev
> Log:
> More URI encoding fixes
...
> camel/trunk/components/camel-gae/src/test/java
Agree, my bad. Will get it fixed.
Thanks,
Hadrian
On 09/06/2011 10:44 AM, Daniel Kulp wrote:
On Friday, September 02, 2011 3:06:28 AM hadr...@apache.org wrote:
Author: hadrian
Date: Fri Sep 2 03:06:28 2011
New Revision: 1164338
URL: http://svn.apache.org/viewvc?rev=1164338&view=rev
Log:
More
[
https://issues.apache.org/jira/browse/CAMEL-4363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098069#comment-13098069
]
Joshua Watkins commented on CAMEL-4363:
---
Is there any way to be able to set these be
´The Tracer and TraceInterceptor do too many additional things
--
Key: CAMEL-4420
URL: https://issues.apache.org/jira/browse/CAMEL-4420
Project: Camel
Issue Type: Improvement
Make Tracer tests simpler
-
Key: CAMEL-4421
URL: https://issues.apache.org/jira/browse/CAMEL-4421
Project: Camel
Issue Type: Improvement
Affects Versions: 2.8.0
Reporter: Christian Schneider
A new patch release apache-camel-2.8.1 is out with approximately 45 issues
resolved: improvements and bug fixes [1].
Please find the staging repo here:
https://repository.apache.org/content/repositories/orgapachecamel-037/
The tarballs are here
https://repository.apache.org/content/repositories
[
https://issues.apache.org/jira/browse/CAMEL-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben O'Day updated CAMEL-4397:
-
Description:
add support for Hazelcast distributed locking/unlocking APIs in a route...see
http://www.ha
hey guys, while working on a solution for a client, I ran into the need to
"synchronize" multiple routes that modify the same data (users, orders, etc)
to prevent collisions (stale writes, etc). Is there an existing way to do
this that I've overlooked?
In the past, I've relied on http://active
Just a thought...If you're naming the lock, you should also name the
unlock. You might want to have multiple locks on a single route, and
you might not want ro release all of them at once.
Don
On Tue, Sep 6, 2011 at 4:16 PM, boday wrote:
> hey guys, while working on a solution for a client, I r
I don't know, the whole thing looks very error prone to me. Looking at
your example, I can see a million ways in which the hazelcast header
could disappear, which would totally mess up the locking (ok, making it
a property would help a bit).
For the technology being used I can see others worki
[
https://issues.apache.org/jira/browse/CAMEL-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098503#comment-13098503
]
Hadrian Zbarcea commented on CAMEL-4397:
@Ben, see my comment on the dev@. Btw, I
[
https://issues.apache.org/jira/browse/CAMEL-4363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098514#comment-13098514
]
Willem Jiang commented on CAMEL-4363:
-
@Joshua,
Because jetty endpoint share the serve
NPE when sending the SMS message less than 255.
---
Key: CAMEL-4422
URL: https://issues.apache.org/jira/browse/CAMEL-4422
Project: Camel
Issue Type: Bug
Components: camel-smpp
Affects
[
https://issues.apache.org/jira/browse/CAMEL-4402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-4402.
-
Resolution: Fixed
> OsgiCamelContextPublisher should publish the camel context with the camelName
[
https://issues.apache.org/jira/browse/CAMEL-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-4422.
-
Resolution: Fixed
Fix Version/s: 2.8.2
Applied patch into trunk and 2.8.x branch.
> NPE w
Disclaimer-- I haven't used either of these locking technologies described, but
understand how and why Ben is looking to use them.
I think it would be helpful to understand how other use cases would apply to
support this in the DSL. I can see a lot of ways where users would
misinterpret what f
37 matches
Mail list logo
