[jira] Resolved: (CAMEL-3606) Regression in stateful job support caused by duplicate job name check added in camel-quartz 2.6

[ https://issues.apache.org/jira/browse/CAMEL-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-3606. Resolution: Duplicate Fixed by that other ticket > Regression in stateful job support caused by du

[jira] Resolved: (CAMEL-3239) camel-quartz should require unique timername

[ https://issues.apache.org/jira/browse/CAMEL-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-3239. Resolution: Fixed Fix Version/s: 2.7.0 Thanks for the patch. trunk: 1067615. > camel-quart

[jira] Commented: (CAMEL-3606) Regression in stateful job support caused by duplicate job name check added in camel-quartz 2.6

[ https://issues.apache.org/jira/browse/CAMEL-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991126#comment-12991126 ] Claus Ibsen commented on CAMEL-3606: Bryan the patch is applied to trunk. You are welc

[jira] Commented: (CAMEL-2853) camel-stream - tailing logfile does not seem to work when logfile is rolled over

[ https://issues.apache.org/jira/browse/CAMEL-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991131#comment-12991131 ] Rob Howes commented on CAMEL-2853: -- Although the benefit in being able to retry overwritt

Re: svn commit: r1067621 - in /camel/trunk/components/camel-servlet: pom.xml src/main/java/org/apache/camel/component/servlet/OsgiServletRegisterer.java

Christian I think you must put the osgi code in a sub package, eg org.apache.camel.component.servlet.osgi This ensures the classloader in non osgi environments will not barf about not able to find OSGI JARs. We do the same in camel-core, see the Activator class in the core, as its in a .osgi sub

[jira] Created: (CAMEL-3633) Force disable Quartz UpdateChecker

Force disable Quartz UpdateChecker -- Key: CAMEL-3633 URL: https://issues.apache.org/jira/browse/CAMEL-3633 Project: Camel Issue Type: Improvement Components: camel-quartz Affects Versions: 2.6.0

[jira] Resolved: (CAMEL-3579) Impossible to use multiple quartz schedulers.

[ https://issues.apache.org/jira/browse/CAMEL-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-3579. Resolution: Fixed Thanks for the patch Sergey. trunk: 1067624. I did some tests on OSGi and manag

[jira] Resolved: (CAMEL-3633) Force disable Quartz UpdateChecker

[ https://issues.apache.org/jira/browse/CAMEL-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-3633. Resolution: Fixed trunk: 1067624. No more 'phone home' by Quartz. Wonder if Terracotta slipped it

[jira] Commented: (CAMEL-3593) Add AvailablePortFinder to camel-test

[ https://issues.apache.org/jira/browse/CAMEL-3593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991138#comment-12991138 ] Claus Ibsen commented on CAMEL-3593: trunk: 1067626. Thanks for the patch its in trun

[jira] Assigned: (CAMEL-3627) Upgrade to groovy 1.7.7

[ https://issues.apache.org/jira/browse/CAMEL-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-3627: -- Assignee: Claus Ibsen > Upgrade to groovy 1.7.7 > --- > > K

[jira] Resolved: (CAMEL-3627) Upgrade to groovy 1.7.7

[ https://issues.apache.org/jira/browse/CAMEL-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-3627. Resolution: Fixed trunk: 1067628. > Upgrade to groovy 1.7.7 > --- > >

[jira] Created: (CAMEL-3634) Add option to set resultClass when using native query with camel-jpa

Add option to set resultClass when using native query with camel-jpa Key: CAMEL-3634 URL: https://issues.apache.org/jira/browse/CAMEL-3634 Project: Camel Issue Type: New Fe

Re: [DISCUSS] The future of camel-extra

I would also prefer option #2. Christian

Re: [DISCUSS] The future of camel-extra

I also prefer option #2 On Sun, Feb 6, 2011 at 11:58 AM, Christian Müller wrote: > I would also prefer option #2. > > Christian > -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Autho

Re: [DISCUSS] The future of camel-extra

I give +1 for option #2 as we are then more independent of google Christian Am 05.02.2011 23:29, schrieb Hadrian Zbarcea: Now that 2.6.0 is out, I planned to give camel-extra a bit more attention. There are some changes we need to make to camel-extra and I raised an issue about it a while ag

[jira] Commented: (CAMEL-3490) camel-servlet should register on the OSGi HTTP service if deployed in OSGi

[ https://issues.apache.org/jira/browse/CAMEL-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991143#comment-12991143 ] Christian Schneider commented on CAMEL-3490: I have committed the OsgiServletR

Re: [DISCUSS] The future of camel-extra

#2 looks for logic for me. Regards JB -Original Message- From: Hadrian Zbarcea Date: Sat, 5 Feb 2011 17:29:11 To: Reply-To: dev@camel.apache.org Subject: [DISCUSS] The future of camel-extra Now that 2.6.0 is out, I planned to give camel-extra a bit more attention. There are some chang

[jira] Commented: (CAMEL-3490) camel-servlet should register on the OSGi HTTP service if deployed in OSGi

[ https://issues.apache.org/jira/browse/CAMEL-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991146#comment-12991146 ] Claus Ibsen commented on CAMEL-3490: Christian I think you must put the osgi code in a

[jira] Resolved: (CAMEL-3576) camel-jms - Provided a task executor by default

[ https://issues.apache.org/jira/browse/CAMEL-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-3576. Resolution: Fixed trunk: 1067658. > camel-jms - Provided a task executor by default >

[jira] Updated: (CAMEL-3628) Remove Java Util Logging from camel-cxf

[ https://issues.apache.org/jira/browse/CAMEL-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tracy Snell updated CAMEL-3628: --- Attachment: cxf-jul.txt CXF not only uses JUL they require it in some cases when you implement some

[jira] Commented: (CAMEL-3628) Remove Java Util Logging from camel-cxf

[ https://issues.apache.org/jira/browse/CAMEL-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991162#comment-12991162 ] Claus Ibsen commented on CAMEL-3628: Are you camel-cxf code fully up to date. I get a

[jira] Assigned: (CAMEL-3628) Remove Java Util Logging from camel-cxf

[ https://issues.apache.org/jira/browse/CAMEL-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tracy Snell reassigned CAMEL-3628: -- Assignee: (was: Tracy Snell) > Remove Java Util Logging from camel-cxf > --

[jira] Assigned: (CAMEL-3628) Remove Java Util Logging from camel-cxf

[ https://issues.apache.org/jira/browse/CAMEL-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tracy Snell reassigned CAMEL-3628: -- Assignee: Tracy Snell > Remove Java Util Logging from camel-cxf > -

[jira] Commented: (CAMEL-3576) camel-jms - Provided a task executor by default

[ https://issues.apache.org/jira/browse/CAMEL-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991164#comment-12991164 ] Claus Ibsen commented on CAMEL-3576: trunk: 1067682. Don't use thread pool for single

Re: [DISCUSS] The future of camel-extra

[2] - best to stay consistent with other apache projects On 5 Feb 2011, at 22:29, Hadrian Zbarcea wrote: > Now that 2.6.0 is out, I planned to give camel-extra a bit more attention. > > There are some changes we need to make to camel-extra and I raised an issue > about it a while ago and added o

[jira] Commented: (CAMEL-3490) camel-servlet should register on the OSGi HTTP service if deployed in OSGi

[ https://issues.apache.org/jira/browse/CAMEL-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991185#comment-12991185 ] Christian Schneider commented on CAMEL-3490: Done. I am curious though why it

[jira] Updated: (CAMEL-3628) Remove Java Util Logging from camel-cxf

[ https://issues.apache.org/jira/browse/CAMEL-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tracy Snell updated CAMEL-3628: --- Attachment: cxf-jul-diff.txt svn diff was failing to create a usable patch file. Switch to diff and a

[jira] Commented: (CAMEL-3604) Upgrade to Spring 3.0.x as minimum (eg drop support for Spring 2.x)

[ https://issues.apache.org/jira/browse/CAMEL-3604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991209#comment-12991209 ] Christian Müller commented on CAMEL-3604: - Claus, ${camel-root}/parent/pom.xml set

[jira] Assigned: (CAMEL-3634) Add option to set resultClass when using native query with camel-jpa

[ https://issues.apache.org/jira/browse/CAMEL-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller reassigned CAMEL-3634: --- Assignee: Christian Müller > Add option to set resultClass when using native query wi

[jira] Commented: (CAMEL-3628) Remove Java Util Logging from camel-cxf

[ https://issues.apache.org/jira/browse/CAMEL-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991212#comment-12991212 ] Edstrom Johan commented on CAMEL-3628: -- Applies cleanly on trunk, osgi manifests and

[jira] Work started: (CAMEL-3634) Add option to set resultClass when using native query with camel-jpa

[ https://issues.apache.org/jira/browse/CAMEL-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-3634 started by Christian Müller. > Add option to set resultClass when using native query with camel-jpa > -

[jira] Updated: (CAMEL-3634) Add option to set resultClass when using native query with camel-jpa

[ https://issues.apache.org/jira/browse/CAMEL-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller updated CAMEL-3634: Fix Version/s: 2.7.0 > Add option to set resultClass when using native query with camel-jpa

[jira] Resolved: (CAMEL-3628) Remove Java Util Logging from camel-cxf

[ https://issues.apache.org/jira/browse/CAMEL-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edstrom Johan resolved CAMEL-3628. -- Resolution: Fixed Closed, thanks for the patch Tracy. > Remove Java Util Logging from camel-cx

[jira] Assigned: (CAMEL-3628) Remove Java Util Logging from camel-cxf

[ https://issues.apache.org/jira/browse/CAMEL-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edstrom Johan reassigned CAMEL-3628: Assignee: Edstrom Johan (was: Tracy Snell) > Remove Java Util Logging from camel-cxf > ---

[jira] Created: (CAMEL-3635) JPA Native Query Returns Entity Instead of Array

JPA Native Query Returns Entity Instead of Array Key: CAMEL-3635 URL: https://issues.apache.org/jira/browse/CAMEL-3635 Project: Camel Issue Type: Improvement Components: camel-jpa

[jira] Commented: (CAMEL-3634) Add option to set resultClass when using native query with camel-jpa

[ https://issues.apache.org/jira/browse/CAMEL-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991234#comment-12991234 ] Christian Müller commented on CAMEL-3634: - Committed r1067791 > Add option to set

[jira] Resolved: (CAMEL-3634) Add option to set resultClass when using native query with camel-jpa

[ https://issues.apache.org/jira/browse/CAMEL-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller resolved CAMEL-3634. - Resolution: Fixed > Add option to set resultClass when using native query with camel-jpa

[jira] Work stopped: (CAMEL-3634) Add option to set resultClass when using native query with camel-jpa

[ https://issues.apache.org/jira/browse/CAMEL-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-3634 stopped by Christian Müller. > Add option to set resultClass when using native query with camel-jpa > -

[jira] Commented: (CAMEL-3634) Add option to set resultClass when using native query with camel-jpa

[ https://issues.apache.org/jira/browse/CAMEL-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991235#comment-12991235 ] Christian Müller commented on CAMEL-3634: - Mark, you are welcome to test the patch

[jira] Resolved: (CAMEL-3635) JPA Native Query Returns Entity Instead of Array

[ https://issues.apache.org/jira/browse/CAMEL-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller resolved CAMEL-3635. - Resolution: Duplicate See CAMEL-3634 > JPA Native Query Returns Entity Instead of Array

[jira] Created: (CAMEL-3636) Update jira configuration to send notifications to the right address

Update jira configuration to send notifications to the right address Key: CAMEL-3636 URL: https://issues.apache.org/jira/browse/CAMEL-3636 Project: Camel Issue Type: Task

[jira] Work started: (CAMEL-3636) Update jira configuration to send notifications to the right address

[ https://issues.apache.org/jira/browse/CAMEL-3636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-3636 started by Hadrian Zbarcea. > Update jira configuration to send notifications to the right address > --

[jira] Commented: (CAMEL-3606) Regression in stateful job support caused by duplicate job name check added in camel-quartz 2.6

[ https://issues.apache.org/jira/browse/CAMEL-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991256#comment-12991256 ] Bryan Keller commented on CAMEL-3606: - Is the fix in 2.7-SNAPSHOT at https://reposito

[jira] Commented: (CAMEL-3606) Regression in stateful job support caused by duplicate job name check added in camel-quartz 2.6

[ https://issues.apache.org/jira/browse/CAMEL-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991258#comment-12991258 ] Tracy Snell commented on CAMEL-3606: Tomorrow it should be there. > Regression in sta

Camel added to the Sonar pilot

Hi, The ASF is running a pilot instance of Sonar [1] and, thanks to Brett Porter, Camel was included. After four failed builds, Olivier Lamy pitched in and made Chuck Norris happy on the fifth try. Therefore [drum roll] I am happy to introduce the first sonar report of Camel [2]. Feel free to

[jira] Resolved: (CAMEL-3636) Update jira configuration to send notifications to the right address

[ https://issues.apache.org/jira/browse/CAMEL-3636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea resolved CAMEL-3636. Resolution: Fixed Seems to be working. > Update jira configuration to send notifications t

[jira] Commented: (CAMEL-3579) Impossible to use multiple quartz schedulers.

[ https://issues.apache.org/jira/browse/CAMEL-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991285#comment-12991285 ] Sergey Zhemzhitsky commented on CAMEL-3579: --- You're welcome ) > Impossible to u

[jira] Created: (CAMEL-3637) Mistake in camel-eventAdmin feature

Mistake in camel-eventAdmin feature --- Key: CAMEL-3637 URL: https://issues.apache.org/jira/browse/CAMEL-3637 Project: Camel Issue Type: Bug Affects Versions: 2.6.0 Reporter: Jean-Baptiste Onof

[jira] Commented: (CAMEL-3604) Upgrade to Spring 3.0.x as minimum (eg drop support for Spring 2.x)

[ https://issues.apache.org/jira/browse/CAMEL-3604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991296#comment-12991296 ] Claus Ibsen commented on CAMEL-3604: Thanks Christian I have fixed it: 1067870. > Upg