I also wondered why this happened as I used a eclipse refactor command
like before. I guess it happened as my eclipse workspace was not
connected to svn at the time.
Normally I try to move classes in svn.
Christian
Am 08.09.2011 08:16, schrieb Claus Ibsen:
Hi
When you refactor the code such
Hi,
Build servicemix-camel JBI component and smx4 kit against Camel 2.8.1,
and all camel related example there works well.
Here is my +1
Freeman
On 2011-9-7, at 上午3:27, Zbarcea Hadrian wrote:
A new patch release apache-camel-2.8.1 is out with approximately 45
issues resolved: improvements
Hi
When you refactor the code such as moving classes to new packages,
etc. Then try to make sure to use svn mv so so we keep the svn
revisions of this class. If you do a delete and add instead, we loose
all that details.
This is important to keep as it helps resolving issues as you can
compare wi
+1
Christian
Am 06.09.2011 21:27, schrieb Zbarcea Hadrian:
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 tarba
Matt/Hadrian, to your question about the distributed lock being "safe" when
things crash...it depends on the implementation, but
http://www.hazelcast.com/documentation.jsp#Lock Hazelcast claims that it is
designed to handle this scenario...
"Locks are fail-safe. If a member holds a lock and some
Maybe contribute a LockingProcessor that accepts a Lock in the constructor?
Don
Hadrian-
I agree. This is the same conceptual problem NFS/GFS and other similar systems
have. Anytime you implement a centralized locking, you always have to account
for the clients that requested locks disappearing, or the thing that is
centralizing the locks goes away. This is usually solv
Cleanup usage of improper URIs in Camel
---
Key: CAMEL-4425
URL: https://issues.apache.org/jira/browse/CAMEL-4425
Project: Camel
Issue Type: Improvement
Affects Versions: 2.8.0
Reporter: Ha
Christian,
> I moved the following classes without compat stubs as they were not needed
> outside camel-core:
> DefaultPollingConsumerPollStrategy, DefaultRouteNode,
> DefaultScheduledPollConsumer, DefaultSubUnitOfWork, DefaultTracedRouteNodes,
> EventDrivenPollingConsumer, ExpressionAdapter,
Well at least in my case queueing would not work as the lock would
protect the original source of events.
In the solution we used then the other instances would detect that the
active instance is not working anymore and then find a new active
instance among the remaining instances.
If the lock
Well my case is a little different as the locking or synchronization is
not per object.
In my case it was the connection to a backend system (a Stock Exchange)
where only one instance should be connected to the
exchange but several were needed as fallbacks.
So the main difference is that in my
Ben, no issue with the term lock(), I get the semantics. What I don't
get is this: what happens in your scenario if one of the boxes crashes
(say physically, burnt memory chip, power supply explodes) with the lock
acquired. What do the other camel processes do?
Why not just queue the requests?
Yeah, we have a DelegateProcessor for before/after processing.
Hadrian
On 09/07/2011 12:25 AM, Matt Pavlovich wrote:
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
Christian, my use case is that I have multiple apps that update the same data
(PurchaseOrders) and we periodically see some stale writes. We have a
combination of Camel/CXF web services (load balanced across 2 machines) and
batch processing in Camel routes (in a separate app) and are evaluating
us
[
https://issues.apache.org/jira/browse/CAMEL-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099033#comment-13099033
]
Hadrian Zbarcea commented on CAMEL-4417:
@Christian, all the changes you make in 2
[
https://issues.apache.org/jira/browse/CAMEL-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099017#comment-13099017
]
Jonathan Anstey commented on CAMEL-4424:
Yeah, having everything 100% at central w
[
https://issues.apache.org/jira/browse/CAMEL-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099001#comment-13099001
]
Nils Breunese commented on CAMEL-4424:
--
Adding that repository fixes the dependency p
[
https://issues.apache.org/jira/browse/CAMEL-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098996#comment-13098996
]
Jonathan Anstey commented on CAMEL-4424:
It is here
http://svn.apache.org/repos/a
Missing saxon-sql 9.1.0.8 dependency for camel-saxon in Maven Central
-
Key: CAMEL-4424
URL: https://issues.apache.org/jira/browse/CAMEL-4424
Project: Camel
Issue Type: Bug
[
https://issues.apache.org/jira/browse/CAMEL-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated CAMEL-4417:
---
Attachment: CAMEL-4417-1.patch
Patch moving all support classes from impl to support.
Hi
Thanks for all your help.
i have exposed the soap web service through camel.
Below is my code structure, it is consuming the message sent from soap ui.
- soap endpoint configured in context file
from wsdl all the files are generted.
from("cxf:bean:) - exposed web service
.ch
[
https://issues.apache.org/jira/browse/CAMEL-4423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098858#comment-13098858
]
Freeman Fang commented on CAMEL-4423:
-
commit fix
http://svn.apache.org/viewvc?rev=116
[
https://issues.apache.org/jira/browse/CAMEL-4363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098814#comment-13098814
]
Joshua Watkins commented on CAMEL-4363:
---
I think I understand what you are saying. I
[
https://issues.apache.org/jira/browse/CAMEL-4423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-4423 started by Freeman Fang.
> use geronimo-jaxws_2.2_spec 1.1 bundle
> --
>
> Key: CAMEL-4423
>
use geronimo-jaxws_2.2_spec 1.1 bundle
--
Key: CAMEL-4423
URL: https://issues.apache.org/jira/browse/CAMEL-4423
Project: Camel
Issue Type: Improvement
Reporter: Freeman Fang
Assigne
I am not sure if this is the same use case that I had some years ago.
We wanted to have several instances of an integration running but only
one of them should be active at any time.
At the time there was no easy solution for this problem.
So in that use case you would have several instances o
Maybe a lock block DSL with a key could help use to implement such a
function.
lock().to(xxx).unlock()
Willem
On Wed Sep 7 15:07:33 2011, boday wrote:
thanks for the feedback. I agree that this needs more consideration and may
not even be a good fit for Camel (hence this post). I do fee
+1 (non binding).
Tested with Karaf 2.2.2, using Spring DSL and Blueprint DSL.
Regards
JB
On 09/06/2011 09:27 PM, Zbarcea Hadrian wrote:
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:
htt
[
https://issues.apache.org/jira/browse/CAMEL-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098673#comment-13098673
]
Jean-Baptiste Onofré commented on CAMEL-4419:
-
The upgrade breaks the camel-cx
thanks for the feedback. I agree that this needs more consideration and may
not even be a good fit for Camel (hence this post). I do feel like this is
becoming a more common use case given the trend towards more
concurrent/distributed solutions (clustering, cloud deployments, big data,
etc). AMQ
30 matches
Mail list logo
