[jira] [Created] (CAMEL-4280) Out of date OSGi version

Out of date OSGi version Key: CAMEL-4280 URL: https://issues.apache.org/jira/browse/CAMEL-4280 Project: Camel Issue Type: Bug Components: osgi Affects Versions: 2.8.0, 2.7.3 Reporter: Jean-B

[jira] [Created] (CAMEL-4279) Add support for the new TLS for spring-ws if possible

Add support for the new TLS for spring-ws if possible - Key: CAMEL-4279 URL: https://issues.apache.org/jira/browse/CAMEL-4279 Project: Camel Issue Type: Improvement Components: ca

Re: Validation vs. validator

Hello Robert! The user@ mailing list is the best for this kind of questions... You are not so specific with your question what you want to do. In Camel, we have 4 different validation components/functionalities: - With [1] you can validate an XML document against an XML Schema. - With [2] you can

[jira] [Updated] (CAMEL-4278) Additional methods added to example QuickfixConverters

[ https://issues.apache.org/jira/browse/CAMEL-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pablo Venini updated CAMEL-4278: Attachment: patchfile.txt > Additional methods added to example QuickfixConverters > --

[jira] [Created] (CAMEL-4278) Additional methods added to example QuickfixConverters

Additional methods added to example QuickfixConverters -- Key: CAMEL-4278 URL: https://issues.apache.org/jira/browse/CAMEL-4278 Project: Camel Issue Type: Improvement Reporter:

[jira] [Updated] (CAMEL-4276) camel-cxf OSGi bundle uses an incorrect CXF version range

[ https://issues.apache.org/jira/browse/CAMEL-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated CAMEL-4276: Fix Version/s: 2.8.1 2.7.4 > camel-cxf OSGi bundle uses an incor

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

[ https://issues.apache.org/jira/browse/CAMEL-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072439#comment-13072439 ] Hadrian Zbarcea commented on CAMEL-4256: The tricky part will be the changes to th

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

[ https://issues.apache.org/jira/browse/CAMEL-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-4256 started by Hadrian Zbarcea. > Adding a EndpointConfiguration interface > > > Key: CAMEL-4256 >

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

[ https://issues.apache.org/jira/browse/CAMEL-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072430#comment-13072430 ] Keith Babo commented on CAMEL-4256: --- I think this would be a great change on a number of

[jira] [Commented] (CAMEL-4276) camel-cxf OSGi bundle uses an incorrect CXF version range

[ https://issues.apache.org/jira/browse/CAMEL-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072407#comment-13072407 ] Jean-Baptiste Onofré commented on CAMEL-4276: - Fixed on Camel trunk: revision

[jira] [Commented] (CAMEL-4277) camel-kestrel: Cannot cache data larger than 1048576 bytes

[ https://issues.apache.org/jira/browse/CAMEL-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072397#comment-13072397 ] Vadim TSes'ko commented on CAMEL-4277: -- The problem is in {{memcached-2.5.jar}}, whic

[jira] [Commented] (CAMEL-4277) camel-kestrel: Cannot cache data larger than 1048576 bytes

[ https://issues.apache.org/jira/browse/CAMEL-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072390#comment-13072390 ] Vadim TSes'ko commented on CAMEL-4277: -- OK, I'll look into it. There are two possibil

[jira] [Issue Comment Edited] (CAMEL-4277) camel-kestrel: Cannot cache data larger than 1048576 bytes

[ https://issues.apache.org/jira/browse/CAMEL-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072390#comment-13072390 ] Vadim TSes'ko edited comment on CAMEL-4277 at 7/28/11 3:01 PM: -

Re: How to correctly handle Component parameters

For component options just add getter/setters so they are configured using java bean style. So if ppl use spring xml then they can setup the component On Thu, Jul 28, 2011 at 4:36 PM, E.Gherardini wrote: > Hi, > in my component (for oracle coherence distributed cache) I have differe

How to correctly handle Component parameters

Hi, in my component (for oracle coherence distributed cache) I have different type of parameters: 1) parameters related to the endpoint (e.g. like the SedaComponent "concurrentConsumers"): these parameters are the ones that I would like an user configure inside the endpoint URI (as happens in the

[jira] [Resolved] (CAMEL-4049) Document AHC Component Support

[ https://issues.apache.org/jira/browse/CAMEL-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Valeri resolved CAMEL-4049. - Resolution: Fixed > Document AHC Component Support > -- > >

Re: [DISCUSS] - Dynamic to endpoint

> Ah seems like I finally got it. By specifying all the possible > expressions we should support. But doesn't that then require the camel-core to know about all the possible sub-expressions? Not exactly extensible. I personally think it would be better to use an of some sort there and then a

[jira] [Updated] (CAMEL-4277) camel-kestrel: Cannot cache data larger than 1048576 bytes

[ https://issues.apache.org/jira/browse/CAMEL-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-4277: --- Component/s: (was: camel-core) > camel-kestrel: Cannot cache data larger than 1048576 bytes > ---

[jira] [Updated] (CAMEL-4277) camel-kestrel: Cannot cache data larger than 1048576 bytes

[ https://issues.apache.org/jira/browse/CAMEL-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-4277: --- Priority: Minor (was: Critical) Issue Type: Improvement (was: Bug) This cannot be a critical

Re: [DISCUSS] - Dynamic to endpoint

Hi Ah seems like I finally got it. By specifying all the possible expressions we should support. We can make JAXB generate an optional choice @XmlElements({ @XmlElement(required = false, name = "simple", type = SimpleExpression.class), @XmlElement(required = false, name = "groovy", ty

[jira] [Created] (CAMEL-4277) camel-kestrel: Cannot cache data larger than 1048576 bytes

camel-kestrel: Cannot cache data larger than 1048576 bytes -- Key: CAMEL-4277 URL: https://issues.apache.org/jira/browse/CAMEL-4277 Project: Camel Issue Type: Bug Components:

Re: [DISCUSS] - Dynamic to endpoint

Hi I just had a peek once again. JAXB is still limited in how much you can customize it. The only way so far I have found for optional expressions is to add to SendDefinition: @XmlElementRef private List expression; I have to use a List as JAXB will generate a XSD (see below) So there i

[jira] [Created] (CAMEL-4276) camel-cxf OSGi bundle uses an incorrect CXF version range

camel-cxf OSGi bundle uses an incorrect CXF version range - Key: CAMEL-4276 URL: https://issues.apache.org/jira/browse/CAMEL-4276 Project: Camel Issue Type: Bug Components: ca

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13072320#comment-13072320 ] Babak Vahdat commented on CAMEL-4255: - Here you are: https://issues.apache.org/jira/br

[jira] [Updated] (CAMEL-4275) don't ignore/neglect java.io.File.delete() returned boolean value

[ https://issues.apache.org/jira/browse/CAMEL-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-4275: Attachment: file.delete.txt > don't ignore/neglect java.io.File.delete() returned boolean value > -

[jira] [Created] (CAMEL-4275) don't ignore/neglect java.io.File.delete() returned boolean value

don't ignore/neglect java.io.File.delete() returned boolean value - Key: CAMEL-4275 URL: https://issues.apache.org/jira/browse/CAMEL-4275 Project: Camel Issue Type: Improvement

[DISCUSS] - Dynamic to endpoint

Hi Its fairly common for end users of Camel to send a message to an endpoint by which the uri is dynamic. We have a FAQ for that. http://camel.apache.org/how-do-i-use-dynamic-uri-in-to.html However you would need to use the recipient list EIP to support that. Ben O'Day recently created a ticket

Re: [DISCUSS] Components relying on commercial software

HI, I am the developer of [3] http://camel.465427.n5.nabble.com/Developing-Oracle-Coherence-3-7-Camel-Component-td4618649.html My code relies on a commercial product (i.e. Oracle Coherence), but I would like to donate my own developed code. If I donate my own code under the Apache License, came

[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 Dont reopen this ticket as the title is about line separators. Open a new ticket

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13072300#comment-13072300 ] Babak Vahdat commented on CAMEL-4255: - Just as note, maybe in contrast to the provided

Re: Developing Oracle Coherence 3.7 Camel Component - License problems

Not an answer but we discussed this topic (and your component) here: http://camel.465427.n5.nabble.com/DISCUSS-Components-relying-on-commercial-software-td4621208.html On Thu, Jul 28, 2011 at 12:36 PM, E.Gherardini wrote: > Hi all, > I almost finished writing the component. > > I need to write so

SOAPFaultException: BindingOperationInfo must be specified

我將一camel專案deploy於ServiceMix 4.3.0上, 然後於client side 呼叫該Web service, 1. 於 ServiceMix console 成功出現client side 傳入參數 2. 但於client side console(Eclipse) 出現已下錯誤訊息: SOAPFaultException: BindingOperationInfo must be specified camel-context.xml 內容如下: ...input: Labor number, output: Labo

[jira] [Reopened] (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 reopened CAMEL-4255: - As part of the changes provided in the patch regarding TestSupport.deleteDirectory() method was not

Re: Developing Oracle Coherence 3.7 Camel Component - License problems

Hi all, I almost finished writing the component. I need to write some more complete test (for which suggestions are welcome ;) ) and exposing some coherence-related parameters. My main concerns now regards licences. Oracle Coherence is not a free product, but we knew it. My code is based on the

Build failed in Jenkins: Camel #1286

See Changes: [cschneider] CAMEL-4244 refactored ExecutorServiceStrategy [davsclaus] CAMEL-4198: Fixed issue with KVP when key has no value. Thanks to Surya for patch. Polished the source a bit fixing spelling etc. [dkulp] Bunch more junit4 upd

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

See -- [INFO] [INFO] Building Camel :: Web [INFO]task-segment: [clean, install] [INFO] ---

Build failed in Jenkins: Camel » Camel :: JMS #1286

See Changes: [cschneider] CAMEL-4244 refactored ExecutorServiceStrategy [dkulp] Fix checkstyle error [dkulp] Move some tests to the JUnit 4 version for CamelTestSupport [davsclaus] CAMEL-4273: Use static inner class

Re: SOAPFaultException: BindingOperationInfo must be specified

Can you make sure your myTransform copy the in message headers to the out message? It looks like the Operation header is lost when you pass the exchange to the cxf:bean:externalWSEndpoint1. BTW, Please ask the user question in the user mailing list. Willem -- View this message in context: http:

[jira] [Commented] (CAMEL-4244) Refactor ExecutorService classes into a InstanceManagerPattern

[ https://issues.apache.org/jira/browse/CAMEL-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072257#comment-13072257 ] Claus Ibsen commented on CAMEL-4244: All the model definition classes should not have

Re: [DISCUSS] Global interceptors

It's already the case and it does not fulfill my need for multiple reasons: * when the service is registered, it's way too late to change anything, I need real low level interception * only contexts created by blueprint or spring are registered, not those create with a java / scala / groovy DSL

Re: [DISCUSS] Global interceptors

Hi Christian, It's already the case. CamelContext are exposed as OSGi services. It's used in Camel commands to list it, etc. The whiteboard could work but it depends what we want to achieve. Regards JB On 07/28/2011 10:36 AM, Christian Schneider wrote: How about offering the camelContext as

Re: [DISCUSS] Global interceptors

How about offering the camelContext as an OSGi service? This way servicemix can use the whiteboard pattern to watch for camel contexts and register with them. Christian Am 28.07.2011 10:14, schrieb Guillaume Nodet: I found another way which I think is cleaner. I've added a single Container

Re: [DISCUSS] Global interceptors

Hi Guillaume, indeed, it looks cleaner. Let me take a deeper look on the code but it sounds good. Regards JB On 07/28/2011 10:14 AM, Guillaume Nodet wrote: I found another way which I think is cleaner. I've added a single Container interface with a singleton which is called back whenever a

Re: [DISCUSS] Global interceptors

I found another way which I think is cleaner. I've added a single Container interface with a singleton which is called back whenever a CamelContext is created. The implementation can then add a LifecycleListener or register any other SPI object. See https://github.com/gnodet/camel/commit/a13b4fc

[jira] [Assigned] (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 reassigned CAMEL-4254: -- Assignee: Willem Jiang Willem can you look at this as part of that other ticket for camel-soap

[jira] [Resolved] (CAMEL-4198) Bindy Parser not handling Null values in KVP

[ https://issues.apache.org/jira/browse/CAMEL-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4198. Resolution: Fixed Assignee: Claus Ibsen Thanks for the patch. > Bindy Parser not handling Nu