[
https://issues.apache.org/jira/browse/CAMEL-4168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13076058#comment-13076058
]
Lucien Schmitz commented on CAMEL-4168:
---
I think getRouteId has also to be added to
Hi
The stop operation on the consumer is synchronous to ensure the
operation goes well.
I am not to keen that this is changed just with the mind of improving
your unit test times.
This could break behavior for people using it in production.
Also you grab the executor service on the reply
[
https://issues.apache.org/jira/browse/CAMEL-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider resolved CAMEL-4244.
Resolution: Fixed
Refactor ExecutorService classes into a InstanceManagerPattern
Agreed. If the issue is test time, just make the test cases call stop
asynchronously?
On 2 August 2011 07:43, Claus Ibsen claus.ib...@gmail.com wrote:
Hi
The stop operation on the consumer is synchronous to ensure the
operation goes well.
I am not to keen that this is changed just with the
[
https://issues.apache.org/jira/browse/CAMEL-4168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-4168.
Resolution: Fixed
Fix Version/s: (was: 2.8.0)
2.9.0
Thanks for
[
https://issues.apache.org/jira/browse/CAMEL-4168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reopened CAMEL-4168:
Add getRouteId() to TraceEventMessage
-
Key:
[
https://issues.apache.org/jira/browse/CAMEL-4248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-4248:
--
Assignee: Claus Ibsen
Create a set of Camel JMX annotations
[
https://issues.apache.org/jira/browse/CAMEL-4248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-4248.
Resolution: Fixed
Fix Version/s: (was: 3.0.0)
There is now 3 annotations in
[
https://issues.apache.org/jira/browse/CAMEL-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13076079#comment-13076079
]
Claus Ibsen commented on CAMEL-4291:
We should create a Camel MBeanInfoAssembler that
Create Camel based JmxMBeanAssembler
Key: CAMEL-4291
URL: https://issues.apache.org/jira/browse/CAMEL-4291
Project: Camel
Issue Type: Sub-task
Reporter: Claus Ibsen
Assignee:
Hi
Just a heads up on the progress so far.
The parent ticket is, and I have created sub-tickets for sub tasks to
be executed:
https://issues.apache.org/jira/browse/CAMEL-3408
There is a pluggable API in place, that ensures that when people uses
camel-spring with Camel, it will support the
Camel JMS documentation - Two links to nabble do no longer work
---
Key: CAMEL-4292
URL: https://issues.apache.org/jira/browse/CAMEL-4292
Project: Camel
Issue Type: Task
[
https://issues.apache.org/jira/browse/CAMEL-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13076101#comment-13076101
]
Claus Ibsen commented on CAMEL-4249:
The following components
- camel-jms
- camel-jpa
[
https://issues.apache.org/jira/browse/CAMEL-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13076102#comment-13076102
]
Claus Ibsen commented on CAMEL-4249:
And then check all the pom.xml files and remove
[
https://issues.apache.org/jira/browse/CAMEL-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13076104#comment-13076104
]
Claus Ibsen commented on CAMEL-4249:
Add unit test in camel-spring that uses the
@Bean method name is ignored
Key: CAMEL-4293
URL: https://issues.apache.org/jira/browse/CAMEL-4293
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.8.0
[
https://issues.apache.org/jira/browse/CAMEL-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent MATHON updated CAMEL-4293:
--
Attachment: camel-bug-2.8.0.zip
@Bean method name is ignored
See https://builds.apache.org/job/Camel/org.apache.camel$camel-web/1291/
--
[...truncated 1240 lines...]
2K downloaded (google-collections-1.0.pom)
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
See https://builds.apache.org/job/Camel/org.apache.camel$camel-jmx/1291/
See https://builds.apache.org/job/Camel/1291/changes
Changes:
[davsclaus] CAMEL-4168: Added getRouteId to trace event message
[davsclaus] CAMEL-4248: Introducing a set of Camel JMX annotations to be used
for JMX management.
[davsclaus] CAMEL-4168: Added getRouteId to trace event message
[
https://issues.apache.org/jira/browse/CAMEL-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-4291.
Resolution: Fixed
Fix Version/s: (was: 3.0.0)
Create Camel based JmxMBeanAssembler
Hi
I have noticed since this commit, some of the JMS unit tests start to fail.
Seen that in camel-jms and also in tests/camel-itest
On Tue, Aug 2, 2011 at 8:43 AM, Claus Ibsen claus.ib...@gmail.com wrote:
Hi
The stop operation on the consumer is synchronous to ensure the
operation goes
Hi
Another heads up. I have implemented the Camel JmxMbeanAssember, and
committed to trunk.
All the unit tests passed and the migrated is easy. Just replace the
Spring JMX annotations with their Camel counterparts.
So camel-core now use pure Camel for JMX and only depend on slf4j-api
as 3rd
[
https://issues.apache.org/jira/browse/CAMEL-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13076134#comment-13076134
]
Christian Schneider commented on CAMEL-4244:
Got them fixed now
Refactor
Camel CXF Endpoint creates incomplete WSDL
--
Key: CAMEL-4294
URL: https://issues.apache.org/jira/browse/CAMEL-4294
Project: Camel
Issue Type: Bug
Components: camel-cxf
Affects Versions:
[
https://issues.apache.org/jira/browse/CAMEL-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
herriot one updated CAMEL-4294:
---
Attachment: camel-cxf-test.zip
Camel CXF Endpoint creates incomplete WSDL
camel-spring-ws bundle specify a wrong version of spring package
Key: CAMEL-4295
URL: https://issues.apache.org/jira/browse/CAMEL-4295
Project: Camel
Issue Type: Bug
[
https://issues.apache.org/jira/browse/CAMEL-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-4295.
-
Resolution: Fixed
Applied patch into trunk.
camel-spring-ws bundle specify a wrong version of
[
https://issues.apache.org/jira/browse/CAMEL-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-4249:
--
Assignee: Claus Ibsen
Replace all Spring JMX annotations with Camel JMX annotations
[
https://issues.apache.org/jira/browse/CAMEL-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua Watkins updated CAMEL-3938:
--
Attachment: simpleMessageListenerContainerAddition
Patch re-adding
[
https://issues.apache.org/jira/browse/CAMEL-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua Watkins updated CAMEL-3938:
--
Patch Info: [Patch Available]
Affects Version/s: 2.7.3
2.8.0
Exception handlers added with CamelTestSupport.adviceWith() are not applied
consistently
Key: CAMEL-4296
URL: https://issues.apache.org/jira/browse/CAMEL-4296
[
https://issues.apache.org/jira/browse/CAMEL-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakub Korab updated CAMEL-4296:
---
Attachment: MultiAdviceWithTest.java
JUnit test demonstrating the behaviour.
Exception handlers
[
https://issues.apache.org/jira/browse/CAMEL-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakub Korab updated CAMEL-4296:
---
Priority: Minor (was: Major)
Exception handlers added with CamelTestSupport.adviceWith() are not
Add errorHandler option for DMLC to camel-jms
-
Key: CAMEL-4297
URL: https://issues.apache.org/jira/browse/CAMEL-4297
Project: Camel
Issue Type: Improvement
Affects Versions: 2.8.0
[
https://issues.apache.org/jira/browse/CAMEL-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13078324#comment-13078324
]
Keith Babo commented on CAMEL-4256:
---
The approach to start with a default, map-based
[
https://issues.apache.org/jira/browse/CAMEL-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Anstey resolved CAMEL-4297.
Resolution: Fixed
janstey@duffman:/x1/asf/camel/trunk/components/camel-jms$ svn ci -m
Hi,
I shared my code (I hope it can be linked in the components page) inside
google code:
http://code.google.com/p/oracle-coherence-camel-component/
Suggestions and feedbacks are welcome.
--
View this message in context:
Hello!
I love to see as we asking our users to be more involved with our project.
I would like to add the label Contributor or Beginner (or something
similar) to issues which are easy to be resolve (by interested
users/customers). We should not fix these issues so soon (unless it's an
urgent
Hi,
I would personally love it, since I am willing to contribute.
I started developing a new component, but having also the change to join the
project resolving small tasks/issues (without the need to harass devs on
chat asking advices to avoid doing big mistakes...which I did indeed ;) )
would
Hi Christian everyone on the list,
Great idea. We are currently using Camel in the ESB implementation of a
large-scale project and loving it. Me and my senior teammate would love
to get involved with the internals of Camel and finally contribute back
to the community after receiving so much
[
https://issues.apache.org/jira/browse/CAMEL-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang reassigned CAMEL-4294:
---
Assignee: Willem Jiang
Camel CXF Endpoint creates incomplete WSDL
On Tuesday, August 02, 2011 10:45:42 PM Christian Müller wrote:
Hello!
I love to see as we asking our users to be more involved with our project.
+1
I would like to add the label Contributor or Beginner (or something
similar) to issues which are easy to be resolve (by interested
See https://builds.apache.org/job/Camel/1292/
--
Started by an SCM change
Building remotely on ubuntu2
hudson.util.IOException2: remote file operation failed:
https://builds.apache.org/job/Camel/ws/ at
hudson.remoting.Channel@840cbd:ubuntu2
at
+1
This is great stuff, it will be really helpful to see the estimated
complexity, because we often don't have the full picture of the issue
immediately and some are on much more limited time than those
dedicated half or full time to the project.
Taariq
On Wed, Aug 3, 2011 at 3:24 AM, Daniel
FYI,
in Karaf and ServiceMix, we added the low-hanging-fruit Jira tag to
classify the Jira easy to fix.
Regards
JB
On 08/03/2011 06:34 AM, Taariq Levack wrote:
+1
This is great stuff, it will be really helpful to see the estimated
complexity, because we often don't have the full picture of
46 matches
Mail list logo
