[jira] [Assigned] (CAMEL-4370) It's hardly possible to use all expression of the Simple language to create file names in the file component

[ https://issues.apache.org/jira/browse/CAMEL-4370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-4370: -- Assignee: Claus Ibsen It's hardly possible to use all expression of the Simple language to

[jira] [Created] (CAMEL-4372) Add FiltersRef option for the Jetty component

Add FiltersRef option for the Jetty component - Key: CAMEL-4372 URL: https://issues.apache.org/jira/browse/CAMEL-4372 Project: Camel Issue Type: New Feature Components: camel-jetty

[jira] [Created] (CAMEL-4373) Upgrade to xstream 1.4.1

Upgrade to xstream 1.4.1 Key: CAMEL-4373 URL: https://issues.apache.org/jira/browse/CAMEL-4373 Project: Camel Issue Type: Task Components: camel-xstream Affects Versions: 2.9.0 Reporter:

[jira] [Assigned] (CAMEL-4373) Upgrade to xstream 1.4.1

[ https://issues.apache.org/jira/browse/CAMEL-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned CAMEL-4373: --- Assignee: Jean-Baptiste Onofré Upgrade to xstream 1.4.1

[jira] [Resolved] (CAMEL-4370) It's hardly possible to use all expression of the Simple language to create file names in the file component

[ https://issues.apache.org/jira/browse/CAMEL-4370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4370. Resolution: Fixed Fix Version/s: 2.9.0 2.8.1 Thanks for reporting.

[jira] [Resolved] (CAMEL-4368) The debug doesn't work in the CamelSpringTestSupport

[ https://issues.apache.org/jira/browse/CAMEL-4368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-4368. - Resolution: Fixed Applied patch into trunk and camel-2.8.x branch. The debug doesn't work in

[jira] [Resolved] (CAMEL-4355) CxfRsProducer - Should use LRUSoftCache and start/stop the cache according to the producers lifecycle

[ https://issues.apache.org/jira/browse/CAMEL-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-4355. - Resolution: Fixed Applied patch into trunk CxfRsProducer - Should use LRUSoftCache and

[jira] [Resolved] (CAMEL-4372) Add FiltersRef option for the Jetty component

[ https://issues.apache.org/jira/browse/CAMEL-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-4372. - Resolution: Fixed Applied patch into the trunk. Add FiltersRef option for the Jetty component

[jira] [Updated] (CAMEL-4374) The debugger doesn't work in the CamelSpringTestSupport with route defined in XML

[ https://issues.apache.org/jira/browse/CAMEL-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Kuhtz updated CAMEL-4374: - Description: The debugger doesn't work in the CamelSpringTestSupport with route defined in XML.

[jira] [Created] (CAMEL-4374) The debugger doesn't work in the CamelSpringTestSupport with route defined in XML

The debugger doesn't work in the CamelSpringTestSupport with route defined in XML - Key: CAMEL-4374 URL: https://issues.apache.org/jira/browse/CAMEL-4374 Project: Camel

[jira] [Updated] (CAMEL-4374) The debugger doesn't work in the CamelSpringTestSupport with route defined in XML

[ https://issues.apache.org/jira/browse/CAMEL-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Kuhtz updated CAMEL-4374: - Attachment: camel-4374.patch The debugger doesn't work in the CamelSpringTestSupport with route

[jira] [Updated] (CAMEL-4375) FilterCreateCamelContextPerClassTest is wrong configured

[ https://issues.apache.org/jira/browse/CAMEL-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Kuhtz updated CAMEL-4375: - Attachment: camel-4375.patch FilterCreateCamelContextPerClassTest is wrong configured

[jira] [Created] (CAMEL-4375) FilterCreateCamelContextPerClassTest is wrong configured

FilterCreateCamelContextPerClassTest is wrong configured Key: CAMEL-4375 URL: https://issues.apache.org/jira/browse/CAMEL-4375 Project: Camel Issue Type: Bug Components:

Re: Scope of org.apache.camel.spi

On Tue, Aug 23, 2011 at 12:38 PM, Christian Schneider ch...@die-schneider.net wrote: I wonder what our scope for the org.apache.camel.spi package is vs the org.apache.camel (API) package. I know two valid definitions for API vs SPI: 1) API interfaces are called by the user to invoke

[jira] [Commented] (CAMEL-4374) The debugger doesn't work in the CamelSpringTestSupport with route defined in XML

[ https://issues.apache.org/jira/browse/CAMEL-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13090160#comment-13090160 ] Willem Jiang commented on CAMEL-4374: - @Andreas If there are more than one camel

[jira] [Commented] (CAMEL-4374) The debugger doesn't work in the CamelSpringTestSupport with route defined in XML

[ https://issues.apache.org/jira/browse/CAMEL-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13090171#comment-13090171 ] Andreas Kuhtz commented on CAMEL-4374: -- @Willem You're right, but currently it

Re: Scope of org.apache.camel.spi

So where do you propose to put them? 1. org.apache.camel 2. org.apache.camel.api.management I propose to go with 2 and create an api package with subpackages so we can structure org.apache.camel better. In the long run I would like to also move the whole camel api into an api package to make

[jira] [Assigned] (CAMEL-4375) FilterCreateCamelContextPerClassTest is wrong configured

[ https://issues.apache.org/jira/browse/CAMEL-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned CAMEL-4375: --- Assignee: Willem Jiang FilterCreateCamelContextPerClassTest is wrong configured

[jira] [Commented] (CAMEL-4373) Upgrade to xstream 1.4.1

[ https://issues.apache.org/jira/browse/CAMEL-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13090248#comment-13090248 ] Jean-Baptiste Onofré commented on CAMEL-4373: - Revision 1161112. I let this

[jira] [Commented] (CAMEL-4374) The debugger doesn't work in the CamelSpringTestSupport with route defined in XML

[ https://issues.apache.org/jira/browse/CAMEL-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13090277#comment-13090277 ] Willem Jiang commented on CAMEL-4374: - @Andreas I just ran a test within camel-test in

[jira] [Assigned] (CAMEL-4374) The debugger doesn't work in the CamelSpringTestSupport with route defined in XML

[ https://issues.apache.org/jira/browse/CAMEL-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned CAMEL-4374: --- Assignee: Willem Jiang The debugger doesn't work in the CamelSpringTestSupport with route

Re: camel FTP not polling the files

I added the recursive=true option but same thing. Process is not polling the files. -- View this message in context: http://camel.465427.n5.nabble.com/camel-FTP-not-polling-the-files-tp4727841p4730805.html Sent from the Camel Development mailing list archive at Nabble.com.

Re: Scope of org.apache.camel.spi

On Wed, Aug 24, 2011 at 3:04 PM, Christian Schneider ch...@die-schneider.net wrote: So where do you propose to put them? 1. org.apache.camel 2. org.apache.camel.api.management I propose to put them here, where they where already 3. org.apache.camel.management These annotations are part of

Re: Scope of org.apache.camel.spi

Hi Claus, we can do that but then we have to move the impl classes somewhere else. We may not mix impl and api in the same package. This is what leads to cycles. Christian Am 24.08.2011 17:53, schrieb Claus Ibsen: On Wed, Aug 24, 2011 at 3:04 PM, Christian Schneider

Re: Scope of org.apache.camel.spi

On Wed, Aug 24, 2011 at 6:17 PM, Christian Schneider ch...@die-schneider.net wrote: Hi Claus, we can do that but then we have to move the impl classes somewhere else. We may not mix impl and api in the same package. This is what leads to cycles. That is actually common. For example look at

Re: Scope of org.apache.camel.spi

Actually JDk and spring are two very good examples how to not do it :-) I guess in the JDK no one cared as you will always have it. Btw. I guess everyone agrees that the JDK is a mess architecturally. Btw. he JDK extensions ship separate API jars like JAXB api. So they seem to have learned.

[HEADS-UP] Removing error prone DefaultEndpoint constructors

Hi, There are 2 DefaultEndpoint constructors that are not necessary, are not really used (and as the doc says they should not be used anyway) that I intend to remove. One issue is that during endpoint construction because the component and context are set later services from the context such

[jira] [Created] (CAMEL-4376) Deprecate DefaultEndpoint constructors that create partially constructed endpoints

Deprecate DefaultEndpoint constructors that create partially constructed endpoints --- Key: CAMEL-4376 URL: https://issues.apache.org/jira/browse/CAMEL-4376 Project:

Re: Scope of org.apache.camel.spi

Actually I think it would be better to put annotations in their own package: org.apache.camel.annotation org.apache.camel.annotation.management org.apache.camel.annotation.etc... Then it won't feel weird that org.apache.camel.management is not there My $0.02, Hadrian On 08/24/2011 01:55 PM,

[jira] [Updated] (CAMEL-4227) Seda component doesn't block on its blocking queue

-blockWhenNotFull-20110824.patch (svn diff . in .../camel/seda (main)) * seda-blockWhenFull-test-20110824.patch (svn diff . in .../camel/seda (test) * SedaBlockWhenFullTest.java (to be added to .../camel/seda (test)) Let me know if I need to make further changes. I've added the ASF license

[jira] [Commented] (CAMEL-2472) A Zookeeper Component for Camel

[ https://issues.apache.org/jira/browse/CAMEL-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13090666#comment-13090666 ] Hadrian Zbarcea commented on CAMEL-2472: Patch applied in r1161306 with a minor

[jira] [Resolved] (CAMEL-2472) A Zookeeper Component for Camel

[ https://issues.apache.org/jira/browse/CAMEL-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea resolved CAMEL-2472. Resolution: Fixed A Zookeeper Component for Camel ---

[jira] [Commented] (CAMEL-4374) The debugger doesn't work in the CamelSpringTestSupport with route defined in XML

[ https://issues.apache.org/jira/browse/CAMEL-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13090744#comment-13090744 ] Willem Jiang commented on CAMEL-4374: - The SpringTestSupport of camel-testng is not

[jira] [Updated] (CAMEL-4374) The debugger doesn't work in the CamelSpringTestSupport with route defined in XML

[ https://issues.apache.org/jira/browse/CAMEL-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CAMEL-4374: Fix Version/s: (was: 2.8.1) The debugger doesn't work in the CamelSpringTestSupport with

[jira] [Commented] (CAMEL-4374) The debugger doesn't work in the CamelSpringTestSupport with route defined in XML

[ https://issues.apache.org/jira/browse/CAMEL-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13090746#comment-13090746 ] Willem Jiang commented on CAMEL-4374: - As there a lots of change on the camel-test

[jira] [Resolved] (CAMEL-4374) The debugger doesn't work in the CamelSpringTestSupport with route defined in XML

[ https://issues.apache.org/jira/browse/CAMEL-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-4374. - Resolution: Fixed Applied the patch into trunk. The debugger doesn't work in the

[jira] [Created] (CAMEL-4377) camel-zookeper - Add features.xml

camel-zookeper - Add features.xml - Key: CAMEL-4377 URL: https://issues.apache.org/jira/browse/CAMEL-4377 Project: Camel Issue Type: Sub-task Reporter: Claus Ibsen Priority: Minor

[jira] [Created] (CAMEL-4378) camel-zookeper - Add osgi unit tests

camel-zookeper - Add osgi unit tests Key: CAMEL-4378 URL: https://issues.apache.org/jira/browse/CAMEL-4378 Project: Camel Issue Type: Sub-task Reporter: Claus Ibsen Priority:

[jira] [Commented] (CAMEL-4376) Deprecate DefaultEndpoint constructors that create partially constructed endpoints

[ https://issues.apache.org/jira/browse/CAMEL-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13090762#comment-13090762 ] Claus Ibsen commented on CAMEL-4376: The default ctr should definitely be there as

[jira] [Commented] (CAMEL-4376) Deprecate DefaultEndpoint constructors that create partially constructed endpoints

[ https://issues.apache.org/jira/browse/CAMEL-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13090763#comment-13090763 ] Claus Ibsen commented on CAMEL-4376: And I would not change anything in a patch

[jira] [Assigned] (CAMEL-4227) Seda component doesn't block on its blocking queue

[ https://issues.apache.org/jira/browse/CAMEL-4227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-4227: -- Assignee: Claus Ibsen Seda component doesn't block on its blocking queue

[jira] [Resolved] (CAMEL-4227) Seda component doesn't block on its blocking queue

[ https://issues.apache.org/jira/browse/CAMEL-4227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4227. Resolution: Fixed Thanks for the patch. I have marked CollectionProducer as @deprecated. I