[jira] [Created] (CAMEL-4143) CxfPayload to Node conversion is not working properly

CxfPayload to Node conversion is not working properly -- Key: CAMEL-4143 URL: https://issues.apache.org/jira/browse/CAMEL-4143 Project: Camel Issue Type: Bug Components: camel-cx

[jira] [Created] (CAMEL-4142) Add a profile in camel-example-cxf-osgi to build the bundle with Blueprint

Add a profile in camel-example-cxf-osgi to build the bundle with Blueprint -- Key: CAMEL-4142 URL: https://issues.apache.org/jira/browse/CAMEL-4142 Project: Camel Issue

Re: source distributions....

+1 for at least having only one source assembly +1 to complete remove the source distribution (I'm sure that people that want to take a look on the source certainly checkout from subversion/git). Regards JB On 06/22/2011 09:28 PM, Daniel Kulp wrote: Question: Does anyone really feel strongl

Re: source distributions....

On Wednesday, June 22, 2011 5:38:19 PM Donald Whytock wrote: > I actually use the source distribution for Windows, because opening up > a .zip is one less step. But I'm good either way. Eclipse can deal > with either file type. > I attached a patch to: https://issues.apache.org/jira/browse/CAME

[jira] [Updated] (CAMEL-4141) Don't filter for line ending for source distributions

[ https://issues.apache.org/jira/browse/CAMEL-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp updated CAMEL-4141: --- Attachment: CAMEL-4141.txt This creates a much simpler src distro that assembles in MUCH MUCH less t

[jira] [Created] (CAMEL-4141) Don't filter for line ending for source distributions

Don't filter for line ending for source distributions - Key: CAMEL-4141 URL: https://issues.apache.org/jira/browse/CAMEL-4141 Project: Camel Issue Type: Improvement Components: bu

Re: source distributions....

If you are using maven, maven eclipse will download the source jar for you automatically. +1 to unify the assembly build, it can save us some CPU time :) Willem On 6/23/11 5:38 AM, Donald Whytock wrote: I actually use the source distribution for Windows, because opening up a .zip is one less

[jira] [Commented] (CAMEL-4139) Unify blueprint and spring namespace parsing in camel-cxf

[ https://issues.apache.org/jira/browse/CAMEL-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053574#comment-13053574 ] Willem Jiang commented on CAMEL-4139: - Just committed the patch of removing the CxfEnd

[jira] [Resolved] (CAMEL-4139) Unify blueprint and spring namespace parsing in camel-cxf

[ https://issues.apache.org/jira/browse/CAMEL-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edstrom Johan resolved CAMEL-4139. -- Resolution: Fixed > Unify blueprint and spring namespace parsing in camel-cxf > ---

Re: source distributions....

I actually use the source distribution for Windows, because opening up a .zip is one less step. But I'm good either way. Eclipse can deal with either file type. Don On Wed, Jun 22, 2011 at 5:13 PM, Aki Yoshida wrote: > I agree with you and I am also for a single unix-type source assembly. > >

Re: source distributions....

I agree with you and I am also for a single unix-type source assembly. saving energy and resources. regards, aki 2011/6/22 Daniel Kulp : > > Question: > > Does anyone really feel strongly that we need separate windows and unix SOURCE > distributions?  We can easily chop a minute or two off the a

Re: source distributions....

+1 For one source distribution with Unix line endings Am 22.06.2011 21:28, schrieb Daniel Kulp: Question: Does anyone really feel strongly that we need separate windows and unix SOURCE distributions? We can easily chop a minute or two off the assembly build if we only have a single source dis

[jira] [Updated] (CAMEL-4104) camel-restlet - Should use dynamic assigned port numbers for testing

[ https://issues.apache.org/jira/browse/CAMEL-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated CAMEL-4104: Attachment: CAMEL-4104.patch New patch covering all unit tests in complement of Chr

[jira] [Updated] (CAMEL-4104) camel-restlet - Should use dynamic assigned port numbers for testing

[ https://issues.apache.org/jira/browse/CAMEL-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated CAMEL-4104: Attachment: (was: CAMEL-4104.patch) > camel-restlet - Should use dynamic assign

[jira] [Resolved] (CAMEL-4140) Improve pom.xml for camel-jibx - use maven-jibx-plugin

[ https://issues.apache.org/jira/browse/CAMEL-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Kettelerij resolved CAMEL-4140. --- Resolution: Fixed > Improve pom.xml for camel-jibx - use maven-jibx-plugin >

[jira] [Updated] (CAMEL-4140) Improve pom.xml for camel-jibx - use maven-jibx-plugin

[ https://issues.apache.org/jira/browse/CAMEL-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Kettelerij updated CAMEL-4140: -- Fix Version/s: 2.8.0 Applied patch, thanks! > Improve pom.xml for camel-jibx - use mav

[jira] [Work started] (CAMEL-4140) Improve pom.xml for camel-jibx - use maven-jibx-plugin

[ https://issues.apache.org/jira/browse/CAMEL-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-4140 started by Richard Kettelerij. > Improve pom.xml for camel-jibx - use maven-jibx-plugin > -- > >

[jira] [Assigned] (CAMEL-4140) Improve pom.xml for camel-jibx - use maven-jibx-plugin

[ https://issues.apache.org/jira/browse/CAMEL-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Kettelerij reassigned CAMEL-4140: - Assignee: Richard Kettelerij > Improve pom.xml for camel-jibx - use maven-jibx-pl

source distributions....

Question: Does anyone really feel strongly that we need separate windows and unix SOURCE distributions? We can easily chop a minute or two off the assembly build if we only have a single source distribution. Most of the time is spent doing the scans and the line ending filtering for the two

[jira] [Updated] (CAMEL-4140) Improve pom.xml for camel-jibx - use maven-jibx-plugin

[ https://issues.apache.org/jira/browse/CAMEL-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Love updated CAMEL-4140: -- Attachment: pom.xml Patch for the pom.xml > Improve pom.xml for camel-jibx - use maven-jibx-plugin > -

[jira] [Created] (CAMEL-4140) Improve pom.xml for camel-jibx - use maven-jibx-plugin

Improve pom.xml for camel-jibx - use maven-jibx-plugin -- Key: CAMEL-4140 URL: https://issues.apache.org/jira/browse/CAMEL-4140 Project: Camel Issue Type: Improvement Affects Versions:

[jira] [Updated] (CAMEL-4139) Unify blueprint and spring namespace parsing in camel-cxf

[ https://issues.apache.org/jira/browse/CAMEL-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp updated CAMEL-4139: --- Attachment: CAMEL-4139b.txt New version of patch that uses the bundle to load the class. > Unify blu

Re: CAMEL-4135/4109 and Spring and Blueprint namespace things....

I've started a bit of this in CAMEL-4139 I got rid of the CxfEndpointBean (and the spring subclass) and updated the spring stuff to parse directly into the CxfEndpoint.I've added setters/getters for the various things that the parsers need to support. This now unifies the Blueprint and S

[jira] [Updated] (CAMEL-4139) Unify blueprint and spring namespace parsing in camel-cxf

[ https://issues.apache.org/jira/browse/CAMEL-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp updated CAMEL-4139: --- Attachment: CAMEL-4139.txt > Unify blueprint and spring namespace parsing in camel-cxf >

[jira] [Created] (CAMEL-4139) Unify blueprint and spring namespace parsing in camel-cxf

Unify blueprint and spring namespace parsing in camel-cxf - Key: CAMEL-4139 URL: https://issues.apache.org/jira/browse/CAMEL-4139 Project: Camel Issue Type: Improvement Compon

[jira] [Commented] (CAMEL-4131) Update versions of various things that CXF depends on

[ https://issues.apache.org/jira/browse/CAMEL-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053276#comment-13053276 ] Willem Jiang commented on CAMEL-4131: - Applied the patch with thanks to Dan, I also di

[jira] [Resolved] (CAMEL-4131) Update versions of various things that CXF depends on

[ https://issues.apache.org/jira/browse/CAMEL-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-4131. - Resolution: Fixed > Update versions of various things that CXF depends on > -

[jira] [Resolved] (CAMEL-4132) Update camel-atom to non-incubator version of abdera

[ https://issues.apache.org/jira/browse/CAMEL-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-4132. - Resolution: Fixed Applied patch with thanks to Dan. I also updated the org.apache.abdera package

[jira] [Commented] (CAMEL-4138) camel-example-cxf-osgi can't be deployed with CXF 2.4.x

[ https://issues.apache.org/jira/browse/CAMEL-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053216#comment-13053216 ] Christian Schneider commented on CAMEL-4138: Ah .. so it just could not resolv

[jira] [Resolved] (CAMEL-4138) camel-example-cxf-osgi can't be deployed with CXF 2.4.x

[ https://issues.apache.org/jira/browse/CAMEL-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-4138. - Resolution: Fixed > camel-example-cxf-osgi can't be deployed with CXF 2.4.x > ---

[jira] [Commented] (CAMEL-4138) camel-example-cxf-osgi can't be deployed with CXF 2.4.x

[ https://issues.apache.org/jira/browse/CAMEL-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053211#comment-13053211 ] Willem Jiang commented on CAMEL-4138: - It relates to the OSGi import package of "org.a

[jira] [Commented] (CAMEL-4138) camel-example-cxf-osgi can't be deployed with CXF 2.4.x

[ https://issues.apache.org/jira/browse/CAMEL-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053184#comment-13053184 ] Christian Schneider commented on CAMEL-4138: Can you go into more details what

[jira] [Issue Comment Edited] (CAMEL-4138) camel-example-cxf-osgi can't be deployed with CXF 2.4.x

[ https://issues.apache.org/jira/browse/CAMEL-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053184#comment-13053184 ] Christian Schneider edited comment on CAMEL-4138 at 6/22/11 11:12 AM: --

[jira] [Updated] (CAMEL-4138) camel-example-cxf-osgi can't be deployed with CXF 2.4.x

[ https://issues.apache.org/jira/browse/CAMEL-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CAMEL-4138: Summary: camel-example-cxf-osgi can't be deployed with CXF 2.4.x (was: camel-example-cxf-osgi can'

[jira] [Created] (CAMEL-4138) camel-example-cxf-osgi can't be deploy with CXF 2.4.x

camel-example-cxf-osgi can't be deploy with CXF 2.4.x - Key: CAMEL-4138 URL: https://issues.apache.org/jira/browse/CAMEL-4138 Project: Camel Issue Type: Bug Components: examples

[jira] [Updated] (CAMEL-4127) camel-jboss 2.6.0 is incompatible with camel-core 2.7.2

[ https://issues.apache.org/jira/browse/CAMEL-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-4127: --- Fix Version/s: 2.9.0 Issue Type: Task (was: Bug) > camel-jboss 2.6.0 is incompatible with cam

[jira] [Resolved] (CAMEL-4122) JMX API to create/delete endpoint

[ https://issues.apache.org/jira/browse/CAMEL-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4122. Resolution: Fixed > JMX API to create/delete endpoint > - > >