[jira] [Resolved] (CAMEL-4255) avoid using "\n" as line seperator while doing I/O and preferably stick to System.getProperty("line.separator")

[ https://issues.apache.org/jira/browse/CAMEL-4255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4255. Resolution: Fixed Fix Version/s: 2.9.0 Thanks for the patch. > avoid using "\n" as line sep

Re: [DISCUSS] Global interceptors

+1 It's a must have for "new" SMX :) Regards JB On 07/21/2011 11:22 AM, Guillaume Nodet wrote: For ServiceMix, we are in need for having *global* interceptors, i.e. some kind of static list of interceptors and other strategies. The main use case is that users would deploy plain camel routes

[jira] [Created] (CAMEL-4259) Add blueprint integration test for CXF endpoint

Add blueprint integration test for CXF endpoint --- Key: CAMEL-4259 URL: https://issues.apache.org/jira/browse/CAMEL-4259 Project: Camel Issue Type: Sub-task Reporter: Willem Jiang

[jira] [Created] (CAMEL-4258) Add blueprint integrate test for CXFRS

Add blueprint integrate test for CXFRS -- Key: CAMEL-4258 URL: https://issues.apache.org/jira/browse/CAMEL-4258 Project: Camel Issue Type: Sub-task Reporter: Willem Jiang Assignee:

[jira] [Commented] (CAMEL-4110) camel-cxf - Add blueprint namespace parser for CXFRS (and possible another missing)

[ https://issues.apache.org/jira/browse/CAMEL-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069371#comment-13069371 ] Willem Jiang commented on CAMEL-4110: - We need to upgrade CXF version to 2.4.2 which h

[jira] [Commented] (CAMEL-4110) camel-cxf - Add blueprint namespace parser for CXFRS (and possible another missing)

[ https://issues.apache.org/jira/browse/CAMEL-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069370#comment-13069370 ] Willem Jiang commented on CAMEL-4110: - Committed the patch into trunk in revision 1149

Re: [DISCUSS] Components relying on commercial software

On 7/22/11 6:20 AM, Richard Kettelerij wrote: Hi As we all know Camel has many components [1] and as such depends on a large number of (third party) libraries. Occasionally community members are requesting new components or are willing to donate components they have developed themselves. Usually

Re: [DISCUSS] - Removing the camel-example-axis

+1, Willem On 7/22/11 12:04 AM, Claus Ibsen wrote: Hi In the current Camel kit we have about 34 examples (give or take). One of these is the camel-example-axis. Its a very old example I created 3 years ago, when Camel was still in 1.x and rather new. The example uses Apache Axis 1.4 and uses S

Re: [DISCUSS] - Removing the camel-example-axis

+1 And cxf is a better candidate to show soap related feature IMHO. Freeman On 2011-7-22, at 上午12:04, Claus Ibsen wrote: Hi In the current Camel kit we have about 34 examples (give or take). One of these is the camel-example-axis. Its a very old example I created 3 years ago, when Camel was s

Re: [DISCUSS] Components relying on commercial software

Whomever creates such a component is responsible for releasing it under a license compatible with the licenses of the dependencies. I'd think that in such case the best option is either something like camel-extra (if GPL is ok) or an independent project at github, or hosted by some organization.

Re: [DISCUSS] Global interceptors

+1 Totally agree. This is a functionality that I've implemented a number of times and is great for creating audit trails, and replay. On Jul 21, 2011, at 4:22 AM, Guillaume Nodet wrote: > For ServiceMix, we are in need for having *global* interceptors, i.e. > some kind of static list of inte

[DISCUSS] Components relying on commercial software

Hi As we all know Camel has many components [1] and as such depends on a large number of (third party) libraries. Occasionally community members are requesting new components or are willing to donate components they have developed themselves. Usually the question emerges where to host these new co

Re: [DISCUSS] - Removing the camel-example-axis

+1 for removing this example Christian On Thu, Jul 21, 2011 at 6:53 PM, Daniel Kulp wrote: > > +1 > > Axis themselves haven't supported Axis 1.4 for several years. > > Besides, CXF is just SOOO much better ;-) > > > Dan > > > On Thursday, July 21, 2011 6:04:58 PM Claus Ibsen wrote: > > Hi

Re: [VOTE] Release Apache Camel 2.8.0

+1 On Thu, Jul 21, 2011 at 5:10 PM, bvahdat wrote: > Hi Claus, > Sorry for my late response Am currently pretty busy > > Created the ticket and provided a patch for it. Actually I went one step > forward regarding this issue to resolve it on other test cases as well. So > please verify/check the

[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-tabpanel&focusedCommentId=13069103#comment-13069103 ] Hadrian Zbarcea commented on CAMEL-2472: Stephen, are you still interested in dona

[jira] [Updated] (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 updated CAMEL-2472: --- Fix Version/s: (was: 3.0.0) 2.9.0 > A Zookeeper Component for Camel >

[jira] [Assigned] (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 reassigned CAMEL-2472: -- Assignee: Hadrian Zbarcea > A Zookeeper Component for Camel > -

Re: [DISCUSS] - Removing the camel-example-axis

+1 Axis themselves haven't supported Axis 1.4 for several years. Besides, CXF is just SOOO much better ;-) Dan On Thursday, July 21, 2011 6:04:58 PM Claus Ibsen wrote: > Hi > > In the current Camel kit we have about 34 examples (give or take). One > of these is the camel-example-axis

[jira] [Updated] (CAMEL-4246) TraceInterceptor does not work correctly for AsyncProcessing

[ https://issues.apache.org/jira/browse/CAMEL-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-4246: --- Fix Version/s: 2.9.0 > TraceInterceptor does not work correctly for AsyncProcessing > ---

[jira] [Updated] (CAMEL-4240) Unable to use XA JMS trabsaction on WebLogic

[ https://issues.apache.org/jira/browse/CAMEL-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-4240: --- Fix Version/s: 2.9.0 > Unable to use XA JMS trabsaction on WebLogic > ---

Re: [DISCUSS] - Removing the camel-example-axis

+1 Christian Am 21.07.2011 18:04, schrieb Claus Ibsen: Hi In the current Camel kit we have about 34 examples (give or take). One of these is the camel-example-axis. Its a very old example I created 3 years ago, when Camel was still in 1.x and rather new. The example uses Apache Axis 1.4 and us

[jira] [Assigned] (CAMEL-4255) avoid using "\n" as line seperator while doing I/O and preferably stick to System.getProperty("line.separator")

[ https://issues.apache.org/jira/browse/CAMEL-4255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-4255: -- Assignee: Claus Ibsen > avoid using "\n" as line seperator while doing I/O and preferably stick

[jira] [Updated] (CAMEL-4254) Missing setter or constructor-argument for elementNameStrategyRef in SoapJaxbDataFormat

[ https://issues.apache.org/jira/browse/CAMEL-4254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-4254: --- Fix Version/s: 2.9.0 > Missing setter or constructor-argument for elementNameStrategyRef in > SoapJa

[jira] [Commented] (CAMEL-4254) Missing setter or constructor-argument for elementNameStrategyRef in SoapJaxbDataFormat

[ https://issues.apache.org/jira/browse/CAMEL-4254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069058#comment-13069058 ] Claus Ibsen commented on CAMEL-4254: Oliver do you want to work on a patch? > Missing

[jira] [Created] (CAMEL-4257) Expose setDeliveryMode property in org.apache.camel.component.jms.JmsComponent

Expose setDeliveryMode property in org.apache.camel.component.jms.JmsComponent -- Key: CAMEL-4257 URL: https://issues.apache.org/jira/browse/CAMEL-4257 Project: Camel

Re: [DISCUSS] - Removing the camel-example-axis

+1 No problem for me. Regards JB On 07/21/2011 06:04 PM, Claus Ibsen wrote: Hi In the current Camel kit we have about 34 examples (give or take). One of these is the camel-example-axis. Its a very old example I created 3 years ago, when Camel was still in 1.x and rather new. The example uses

[DISCUSS] - Removing the camel-example-axis

Hi In the current Camel kit we have about 34 examples (give or take). One of these is the camel-example-axis. Its a very old example I created 3 years ago, when Camel was still in 1.x and rather new. The example uses Apache Axis 1.4 and uses Spring Servlet to show how to use the "spring way" back

[jira] [Created] (CAMEL-4256) Adding a EndpointConfiguration interface

Adding a EndpointConfiguration interface Key: CAMEL-4256 URL: https://issues.apache.org/jira/browse/CAMEL-4256 Project: Camel Issue Type: New Feature Components: camel-core Affects Versi

[jira] [Updated] (CAMEL-4255) avoid using "\n" as line seperator while doing I/O and preferably stick to System.getProperty("line.separator")

[ https://issues.apache.org/jira/browse/CAMEL-4255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-4255: Description: See http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-8-0-tp4610671p46161

Re: [VOTE] Release Apache Camel 2.8.0

Hi Claus, Sorry for my late response Am currently pretty busy Created the ticket and provided a patch for it. Actually I went one step forward regarding this issue to resolve it on other test cases as well. So please verify/check the delivered patch if it makes sense to you in all cases: https

[jira] [Updated] (CAMEL-4255) avoid using "\n" as line seperator while doing I/O and preferably stick to System.getProperty("line.separator")

[ https://issues.apache.org/jira/browse/CAMEL-4255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-4255: Summary: avoid using "\n" as line seperator while doing I/O and preferably stick to System.getPrope

[jira] [Updated] (CAMEL-4255) avoid using "\n" as line seperator while doing I/O, but stick to System.getProperty("line.separator")

[ https://issues.apache.org/jira/browse/CAMEL-4255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-4255: Attachment: cleanup.txt > avoid using "\n" as line seperator while doing I/O, but stick to > Syste

[jira] [Created] (CAMEL-4255) avoid using "\n" as line seperator while doing I/O, but stick to System.getProperty("line.separator")

avoid using "\n" as line seperator while doing I/O, but stick to System.getProperty("line.separator") - Key: CAMEL-4255 URL: https://issues.apache.org/jira/browse/

[jira] [Updated] (CAMEL-4255) avoid using "\n" as line seperator while doing I/O, but stick to System.getProperty("line.separator")

[ https://issues.apache.org/jira/browse/CAMEL-4255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-4255: Description: See http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-8-0-td4610671.html

Re: [CONF] Apache Camel > Scalate

Dan's unilateral decision to scrub the Scalate component from the Camel site, while simply adding the others to a new table, does not send the "we are happy about good external components" message. It sends the message that Dan is the new Camel cop and we need to do things his way or else. I'm su

[jira] [Updated] (CAMEL-4254) Missing setter or constructor-argument for elementNameStrategyRef in SoapJaxbDataFormat

[ https://issues.apache.org/jira/browse/CAMEL-4254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Jelinski updated CAMEL-4254: --- Description: Because the variable "elementNameStrategyRef" in org.apache.camel.dataformat.so

Re: [DISCUSS] Global interceptors

The interceptors story in camel needs revisiting anyway. Hadrian On Jul 21, 2011, at 5:22 AM, Guillaume Nodet wrote: > For ServiceMix, we are in need for having *global* interceptors, i.e. > some kind of static list of interceptors and other strategies. The > main use case is that users would

[jira] [Created] (CAMEL-4254) Missing setter or constructor-argument for elementNameStrategyRef in SoapJaxbDataFormat

Missing setter or constructor-argument for elementNameStrategyRef in SoapJaxbDataFormat --- Key: CAMEL-4254 URL: https://issues.apache.org/jira/browse/CAMEL-4254 Proj

Re: Developing Oracle Coherence 3.7 Camel Component

Correction: I meant camel-cache (not camel-ehcache). On Thu, Jul 21, 2011 at 2:54 PM, Richard Kettelerij < richardkettele...@gmail.com> wrote: > Hi, > > You may want to take a look at camel-ehcache, since Coherence shares many > similarities with EHCache. Otherwise just take a look at a few compo

Re: Developing Oracle Coherence 3.7 Camel Component

Hi, You may want to take a look at camel-ehcache, since Coherence shares many similarities with EHCache. Otherwise just take a look at a few components to get a feeling how these are organized (classes like endpoint, producer, consumer, configuration, etc). Regards, Richard On Thu, Jul 21, 2011

Re: Developing Oracle Coherence 3.7 Camel Component

Thanks a lot for answering Claus. I meant, and if you have time to suggest, is there any component I should particularry take as example, to avoid doing common mistakes ? Thanks again, Emanuele -- View this message in context: http://camel.465427.n5.nabble.com/Developing-Oracle-Coherence-3-7-C

Build failed in Jenkins: Camel #1280

See Changes: [davsclaus] CAMEL-4253: Polished examples. [davsclaus] Upgraded to spring integration 2.0.5 [davsclaus] Upgraded version in pom.xml after release. [davsclaus] Added unit test based on user forum issue [davsclaus] Fixed ftp tests

Build failed in Jenkins: Camel » Camel :: Web #1280

See -- [...truncated 25 lines...] [INFO] Executing tasks [echo] Copying to code together for the XSD generation [mkdir] Created dir:

Jenkins build is back to normal : Camel » Camel :: JMX #1280

See

Jenkins build is back to normal : Camel » Camel :: Platforms :: Apache Karaf :: Commands #1280

See

Jenkins build is back to normal : Camel » Camel :: Test Bundles: mock-javamail-1.7 #1280

See

Jenkins build is back to normal : Camel » Camel :: Core XML #1280

See

Jenkins build is back to normal : Camel » Camel :: Guice #1280

See

Jenkins build is back to normal : Camel » Camel :: Integration Tests :: Standalone #1280

See

Jenkins build is back to normal : Camel » Camel :: Core OSGi #1280

See

Re: Developing Oracle Coherence 3.7 Camel Component

Hi On Thu, Jul 21, 2011 at 11:09 AM, ghepardo wrote: > Hi, > I am starting developing an Oracle Coherence Camel Component (that I am > intentioned to donate), that will support Topics and Queues. > Ah cool. > I would like to ask you some advices, if there is some component more than > other to

Re: [VOTE] Release Apache Camel 2.8.0

I just compiled from trunk and got a complete build without any test failures on windows. That is really great. Many thanks, Christian Am 20.07.2011 15:37, schrieb Claus Ibsen: On Wed, Jul 20, 2011 at 3:21 PM, Claus Ibsen wrote: On Wed, Jul 20, 2011 at 1:15 PM, Christian Schneider wrote:

[jira] [Resolved] (CAMEL-4253) Polish examples XML files

[ https://issues.apache.org/jira/browse/CAMEL-4253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4253. Resolution: Fixed > Polish examples XML files > - > > Key:

[DISCUSS] Global interceptors

For ServiceMix, we are in need for having *global* interceptors, i.e. some kind of static list of interceptors and other strategies. The main use case is that users would deploy plain camel routes and ServiceMix would kick in and configure its interceptors but without any need for the user to cha

[jira] [Created] (CAMEL-4253) Polish examples XML files

Polish examples XML files - Key: CAMEL-4253 URL: https://issues.apache.org/jira/browse/CAMEL-4253 Project: Camel Issue Type: Task Components: examples Reporter: Claus Ibsen Assignee:

Developing Oracle Coherence 3.7 Camel Component

Hi, I am starting developing an Oracle Coherence Camel Component (that I am intentioned to donate), that will support Topics and Queues. I would like to ask you some advices, if there is some component more than other to look at. Thanks a lot to everyone answering, Emanuele. -- View this messag

Re: [CONF] Apache Camel > Scalate

On 20 July 2011 17:43, Eric Johnson wrote: > My understanding of what Dan is saying is that since the Scalate > component is not developed as part of the Apache Camel project it > cannot be documented in a way that makes it look like it is a part of > the Apache Camel project. Thing is though, it

Re: [CONF] Apache Camel > Scalate

BTW the very first paragraph of the scalate camel page clearly showed the groupId of the component - which highlights that its never been part of the camel distro nor was it pretending to be. The components page has always been about all components for camel - irrespective of which distro they come

Re: [CONF] Apache Camel > Scalate

Hi Claus, I think we should also list external components. We only need to make sure it is visible that they are not part of the package and not supported by the camel community. So I think we could have an external components header at the end of the components page where we list external c