[jira] [Assigned] (CAMEL-4538) Make CamelTestSupport return Registry instead of JndiRegistry in createRegistry method

[ https://issues.apache.org/jira/browse/CAMEL-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-4538: -- Assignee: Claus Ibsen > Make CamelTestSupport return Registry instead of JndiRegistry in >

Re: [Discuss] How to do JMX in Apache Camel?

Hi There is a JIRA ticket from the community about adding interfaces for the various MBean we have in camel-core https://issues.apache.org/jira/browse/CAMEL-4468 I assume those interface would transpose to the MXBeans beans you refer to? That would be a good idea to have both the interfaces and

[jira] [Created] (CAMEL-4557) camel-archerype-blueprint creates the blueprint file with a wrong name space location

camel-archerype-blueprint creates the blueprint file with a wrong name space location - Key: CAMEL-4557 URL: https://issues.apache.org/jira/browse/CAMEL-4557 Project:

Re: 2.8.x builds tomorrow maybe?

Just to not shoot us in the foot. So Camel 2.8.2 uses Karaf 2.2.4, which uses Spring 3.0.6. And in the past we had this trouble with Spring 3.0.5 / Spring 3.0.6. I assume the CXF version (Is it 2.4.3) uses Spring 3.0.6 as well. So all the Spring 3.0.5 vs Spring 3.0.6 issue is not a problem on the

Re: [Discuss] How to do JMX in Apache Camel?

Hi On Mon, Oct 17, 2011 at 3:03 PM, Christian Schneider wrote: > Hi all, > > I recently had to dive quite deep into the Camel JMX annotations and their > implementation. In fact much deeper then I had wanted :-) > The problem was that I needed to find a way to send notifications from an > MBean.

[jira] [Commented] (CAMEL-4549) Add support for PGP to camel-crypto

[ https://issues.apache.org/jira/browse/CAMEL-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129489#comment-13129489 ] Adam commented on CAMEL-4549: - Thanks Claus, really appreciate the feedback with my first cont

[jira] [Updated] (CAMEL-4549) Add support for PGP to camel-crypto

[ https://issues.apache.org/jira/browse/CAMEL-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam updated CAMEL-4549: Attachment: pgpcrypto.patch new patch > Add support for PGP to camel-crypto >

Re: 2.8.1 build error

Hi, upgrade to latest JDK should fix, more discussion about this issue from [1] [1]http://camel.465427.n5.nabble.com/Compile-Exception-2-8-1-td4884516.html Freeman On 2011-10-18, at 上午9:30, karafman wrote: When building Camel 2.8.1, Camel-Core I get the following error: [INFO] Compilation fa

2.8.1 build error

When building Camel 2.8.1, Camel-Core I get the following error: [INFO] Compilation failure /home/blue/workspace/camel-2.8.1/camel-core/src/main/java/org/apache/camel/model/LoadBalanceDefinition.java:[134,16] inconvertible types found : org.apache.camel.model.ProcessorDefinition

[jira] [Updated] (CAMEL-4556) NettyProducer creating new connection on every message

[ https://issues.apache.org/jira/browse/CAMEL-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew McMahon updated CAMEL-4556: --- Description: Using a NettyProducer without the disconnect=true configuration is causing the

[jira] [Updated] (CAMEL-4556) NettyProducer creating new connection on every message

[ https://issues.apache.org/jira/browse/CAMEL-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew McMahon updated CAMEL-4556: --- Description: Using a NettyProducer without the disconnect=true configuration is causing the

[jira] [Created] (CAMEL-4556) NettyProducer creating new connection on every message

NettyProducer creating new connection on every message -- Key: CAMEL-4556 URL: https://issues.apache.org/jira/browse/CAMEL-4556 Project: Camel Issue Type: Bug Components: camel-ne

[VOTE] Release Camel 2.7.4

This is a vote to release Camel 2.7.4. 2.7.4 contains fixes for over 11 JIRA issues that would be good to get into the hands of Camel users. Please find the staging repo here: https://repository.apache.org/content/repositories/orgapachecamel-066/ The tarballs are here https://repository.apach

[jira] [Resolved] (CAMEL-4548) camel-cxf should support streaming

[ https://issues.apache.org/jira/browse/CAMEL-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CAMEL-4548. Resolution: Fixed > camel-cxf should support streaming > -- > >

[jira] [Resolved] (CAMEL-4554) Camel doesn't provide converters for StAXSource

[ https://issues.apache.org/jira/browse/CAMEL-4554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CAMEL-4554. Resolution: Fixed > Camel doesn't provide converters for StAXSource > -

Re: 2.8.x builds tomorrow maybe?

The fix version is 2.8.2. What about trunk, 2.9.0? Hadrian On 10/17/2011 02:38 PM, Daniel Kulp wrote: On Monday, October 17, 2011 12:13:59 PM Daniel Kulp wrote: Other than some minor tweaks and javadoc updates (want to add javadoc to new allowStreaming methods and such), I think I'm done wit

[jira] [Updated] (CAMEL-4555) Support nested directories with multiple segment files in the HDFS endpoint consumer

[ https://issues.apache.org/jira/browse/CAMEL-4555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Hoyt updated CAMEL-4555: Attachment: hdfs.patch > Support nested directories with multiple segment files in the HDFS endpoint >

[jira] [Created] (CAMEL-4555) Support nested directories with multiple segment files in the HDFS endpoint consumer

Support nested directories with multiple segment files in the HDFS endpoint consumer Key: CAMEL-4555 URL: https://issues.apache.org/jira/browse/CAMEL-4555 Project: C

Re: 2.8.x builds tomorrow maybe?

On Monday, October 17, 2011 12:13:59 PM Daniel Kulp wrote: > Other than some minor tweaks and javadoc updates (want to add javadoc to > new allowStreaming methods and such), I think I'm done with my performance > work for now. I may also look at the LoggerFactory.getLogger issue a bit > more, bu

[jira] [Created] (CAMEL-4554) Camel doesn't provide converters for StAXSource

Camel doesn't provide converters for StAXSource --- Key: CAMEL-4554 URL: https://issues.apache.org/jira/browse/CAMEL-4554 Project: Camel Issue Type: Improvement Components: camel-core

2.8.x builds tomorrow maybe?

Other than some minor tweaks and javadoc updates (want to add javadoc to new allowStreaming methods and such), I think I'm done with my performance work for now. I may also look at the LoggerFactory.getLogger issue a bit more, but I'm not seeing it on my stack traces anymore so it's less cri

Re: 2.7.4 staged....

On Monday, October 17, 2011 2:20:28 PM Claus Ibsen wrote: > Hi > > Any news on the 2.7.4 release? Sorry. I restaged at: https://repository.apache.org/content/repositories/orgapachecamel-066/ using the proper version of CXF now. Just got sidetracked on trying to meet some performance target

[jira] [Commented] (CAMEL-4548) camel-cxf should support streaming

[ https://issues.apache.org/jira/browse/CAMEL-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128928#comment-13128928 ] Daniel Kulp commented on CAMEL-4548: Just a quick note about perfomance results. On

[jira] [Commented] (CAMEL-4548) camel-cxf should support streaming

[ https://issues.apache.org/jira/browse/CAMEL-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128879#comment-13128879 ] Daniel Kulp commented on CAMEL-4548: Added docs to: https://cwiki.apache.org/conflue

[jira] [Commented] (CAMEL-4548) camel-cxf should support streaming

[ https://issues.apache.org/jira/browse/CAMEL-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128866#comment-13128866 ] Willem Jiang commented on CAMEL-4548: - Hi Dan, As Camel 2.8 is not using the Stream

[Discuss] How to do JMX in Apache Camel?

Hi all, I recently had to dive quite deep into the Camel JMX annotations and their implementation. In fact much deeper then I had wanted :-) The problem was that I needed to find a way to send notifications from an MBean. There are two very different implementation right now: 1) The old way:

[jira] [Updated] (CAMEL-4553) camel-cxf endpoint should be able to determine soap version from incoming message

[ https://issues.apache.org/jira/browse/CAMEL-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CAMEL-4553: Component/s: camel-cxf > camel-cxf endpoint should be able to determine soap version from incom

[jira] [Work started] (CAMEL-4553) camel-cxf endpoint should be able to determine soap version from incoming message

[ https://issues.apache.org/jira/browse/CAMEL-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-4553 started by Freeman Fang. > camel-cxf endpoint should be able to determine soap version from incoming > message > -

[jira] [Created] (CAMEL-4553) camel-cxf endpoint should be able to determine soap version from incoming message

camel-cxf endpoint should be able to determine soap version from incoming message - Key: CAMEL-4553 URL: https://issues.apache.org/jira/browse/CAMEL-4553 Project: Camel

Re: 2.7.4 staged....

Hi Any news on the 2.7.4 release? On Thu, Oct 13, 2011 at 3:24 PM, Daniel Kulp wrote: > > Actually, I'm going to drop this and rebuild it.    I forgot to update CXF to > the latest 2.3.7 release.   I'm running the tests with that now and will > rebuild if things go OK. > > Dan > > > > On Wednesd

[jira] [Created] (CAMEL-4552) Blueprint does not like @EndpointInject

Blueprint does not like @EndpointInject --- Key: CAMEL-4552 URL: https://issues.apache.org/jira/browse/CAMEL-4552 Project: Camel Issue Type: Bug Components: camel-blueprint Reporter:

Re: Issue with Camel Blueprint and EndpointInject

Done --> https://issues.apache.org/jira/browse/CAMEL-4552 On Mon, Oct 17, 2011 at 12:48 PM, Claus Ibsen wrote: > Hi Charles > > Can you create a JIRA ticket? There may be issues with @Produce and > @Consume as well. > > You would need to add support for that in the camel-blueprint component. >

Re: Issue with Camel Blueprint and EndpointInject

Hi Charles Can you create a JIRA ticket? There may be issues with @Produce and @Consume as well. You would need to add support for that in the camel-blueprint component. Like we do in camel-spring to support them by looking up in the Spring ApplicationContext. On Mon, Oct 17, 2011 at 12:05 PM,

Re: The new command aliases in Karaf 2.2.4

+1 to use singular Freeman On 2011-10-17, at 下午5:03, Jean-Baptiste Onofré wrote: Hi Claus, You are right: it depends if the command accepts several bundles or not. For instance: - bundles:start 23 34 56 - system:shutdown (no argument) On trunk, you will see bundle:* or bundles:* commands

Re: The new command aliases in Karaf 2.2.4

+1 on the singular. Moreover, it will save you a when you are using auto completion :-D -- *Ioannis Canellos* * FuseSource ** Blog: http://iocanel.blogspot.com ** Apache Karaf Committer & PMC Apache ServiceMix

[jira] [Created] (CAMEL-4551) NotifyBuilder wereSentTo condition fires too eagerly

NotifyBuilder wereSentTo condition fires too eagerly Key: CAMEL-4551 URL: https://issues.apache.org/jira/browse/CAMEL-4551 Project: Camel Issue Type: Improvement Components: came

Re: The new command aliases in Karaf 2.2.4

Good point James regarding the Unix commands. Regards JB On 10/17/2011 11:10 AM, James Strachan wrote: On 17 October 2011 10:03, Jean-Baptiste Onofré wrote: Hi Claus, You are right: it depends if the command accepts several bundles or not. For instance: - bundles:start 23 34 56 - system:sh

Re: The new command aliases in Karaf 2.2.4

On 17 October 2011 10:03, Jean-Baptiste Onofré wrote: > Hi Claus, > > You are right: it depends if the command accepts several bundles or not. > > For instance: > > - bundles:start 23 34 56 > - system:shutdown (no argument) > > On trunk, you will see bundle:* or bundles:* commands. It's the same:

Re: The new command aliases in Karaf 2.2.4

Hi Claus, You are right: it depends if the command accepts several bundles or not. For instance: - bundles:start 23 34 56 - system:shutdown (no argument) On trunk, you will see bundle:* or bundles:* commands. It's the same: it depends if the commands accept several bundles, or only one. No

The new command aliases in Karaf 2.2.4

Hi I was reading Jean's blog about the Karaf 2.2.4 release http://blog.nanthrax.net/2011/10/whats-new-in-karaf-2-2-4/ And read about the command aliases, which IMHO seems like a good thing. However just wondering why you use the plural naming? - bundles - services And then you have a non plural

[jira] [Resolved] (CAMEL-4550) Upgrade to Karaf 2.2.4

[ https://issues.apache.org/jira/browse/CAMEL-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved CAMEL-4550. - Resolution: Fixed Revision 1185026. > Upgrade to Karaf 2.2.4 > -

[jira] [Created] (CAMEL-4550) Upgrade to Karaf 2.2.4

Upgrade to Karaf 2.2.4 -- Key: CAMEL-4550 URL: https://issues.apache.org/jira/browse/CAMEL-4550 Project: Camel Issue Type: Task Components: karaf Reporter: Jean-Baptiste Onofré Assignee: