[jira] [Commented] (CAMEL-13611) Camel Web3j - Upgrade to Web3j 4.3.1
[ https://issues.apache.org/jira/browse/CAMEL-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16859247#comment-16859247 ] Bilgin Ibryam commented on CAMEL-13611: --- [~Choucri Fahed] I created the component but it is now maintained by the community. Feel free to create a PR and update and improve the component. If needed, start a discussion thread on the dev list. > Camel Web3j - Upgrade to Web3j 4.3.1 > > > Key: CAMEL-13611 > URL: https://issues.apache.org/jira/browse/CAMEL-13611 > Project: Camel > Issue Type: New Feature >Reporter: Choucri Fahed >Assignee: Bilgin Ibryam >Priority: Major > Fix For: 3.0.0, 2.25.0 > > > Support the latest version of Web3j. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-12530) camel-web3j - Finish the work
[ https://issues.apache.org/jira/browse/CAMEL-12530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam reassigned CAMEL-12530: - Assignee: Bilgin Ibryam > camel-web3j - Finish the work > - > > Key: CAMEL-12530 > URL: https://issues.apache.org/jira/browse/CAMEL-12530 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Assignee: Bilgin Ibryam >Priority: Major > Fix For: 2.22.0 > > > This is a new component - camel-web3j. > The configuration class is not finished. There is a TODO with > // TODO: Add javadoc for setter for documentation and add @UriParam to each > option > And it should be possible to configure the List options as plain > String values in URI endpoints, eg separated by comma etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12530) camel-web3j - Finish the work
[ https://issues.apache.org/jira/browse/CAMEL-12530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16501442#comment-16501442 ] Bilgin Ibryam commented on CAMEL-12530: --- hey [~davsclaus] where do I have to update so the component docs appear on camel website? Similarly, I cannot see docs for other components, (I was just looking at atomix for example). > camel-web3j - Finish the work > - > > Key: CAMEL-12530 > URL: https://issues.apache.org/jira/browse/CAMEL-12530 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Priority: Major > Fix For: 2.22.0 > > > This is a new component - camel-web3j. > The configuration class is not finished. There is a TODO with > // TODO: Add javadoc for setter for documentation and add @UriParam to each > option > And it should be possible to configure the List options as plain > String values in URI endpoints, eg separated by comma etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12530) camel-web3j - Finish the work
[ https://issues.apache.org/jira/browse/CAMEL-12530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16496654#comment-16496654 ] Bilgin Ibryam commented on CAMEL-12530: --- [~davsclaus] it is not List that is already supported. The todo is to make it work for all List and also List>.How do you represent list of lists of String in Camel URI? The component also lacks documentations which I have to do... plenty of work. > camel-web3j - Finish the work > - > > Key: CAMEL-12530 > URL: https://issues.apache.org/jira/browse/CAMEL-12530 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Priority: Major > Fix For: 2.22.0 > > > This is a new component - camel-web3j. > The configuration class is not finished. There is a TODO with > // TODO: Add javadoc for setter for documentation and add @UriParam to each > option > And it should be possible to configure the List options as plain > String values in URI endpoints, eg separated by comma etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-9098) Camel Hystrix component
[ https://issues.apache.org/jira/browse/CAMEL-9098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224176#comment-15224176 ] Bilgin Ibryam commented on CAMEL-9098: -- cool! I'll update the feature then. > Camel Hystrix component > --- > > Key: CAMEL-9098 > URL: https://issues.apache.org/jira/browse/CAMEL-9098 > Project: Camel > Issue Type: New Feature >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 2.18.0 > > > Create a camel-hystrix component with the following features: > * (/) Capable of wrapping processors. > * (/) Capable of wrapping static endpoints: > ** (/) wrapping Endpoint objects. > ** (/) wrapping URIs. > * (/) Fluent builders to wrap processors and endpoints. > * Support building Hystrix endpoints with URIs. > * (/) Support fallback endpoints and processors. > * (/) Support response caching, where cache key is calculated by Camel > Expressions. > * (/) Support suppressing exceptions to avoid fallback via > HystrixBadRequestException. > * Request collapsing. > * (/) HystrixRequestContext propagation via Camel headers, to allow multiple > threads to share the HystrixRequestContext. > * Full support in OSGi (Hystrix, Archaius). > * Integrate Archaius configuration with Camel property placeholders – if > possible – including OSGi Config Admin integration. > * Integrate with Turbine to enable the nice Hystrix dashboard. > (/) = done -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-9098) Camel Hystrix component
[ https://issues.apache.org/jira/browse/CAMEL-9098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224134#comment-15224134 ] Bilgin Ibryam commented on CAMEL-9098: -- Claus I've updated the version to point to latest SMX bundle, but when I tried to run a hystrix demo on [OSGI|https://github.com/bibryam/camel-hystrix-demo] I had to install other bundles: install -s mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.commons-configuration/1.9_2 install -s mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.commons-digester/1.8_4 install -s mvn:org.apache.commons/commons-jexl/2.1.1 install -s mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.commons-jxpath/1.3_1 install -s wrap:mvn:com.netflix.archaius/archaius-core/0.4.1 install -s mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.hystrix/1.4.23_1 I wonder, do we need another SMX bundle for archaius, or is it enough to add those to hystrix feature in Camel? > Camel Hystrix component > --- > > Key: CAMEL-9098 > URL: https://issues.apache.org/jira/browse/CAMEL-9098 > Project: Camel > Issue Type: New Feature >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 2.18.0 > > > Create a camel-hystrix component with the following features: > * (/) Capable of wrapping processors. > * (/) Capable of wrapping static endpoints: > ** (/) wrapping Endpoint objects. > ** (/) wrapping URIs. > * (/) Fluent builders to wrap processors and endpoints. > * Support building Hystrix endpoints with URIs. > * (/) Support fallback endpoints and processors. > * (/) Support response caching, where cache key is calculated by Camel > Expressions. > * (/) Support suppressing exceptions to avoid fallback via > HystrixBadRequestException. > * Request collapsing. > * (/) HystrixRequestContext propagation via Camel headers, to allow multiple > threads to share the HystrixRequestContext. > * Full support in OSGi (Hystrix, Archaius). > * Integrate Archaius configuration with Camel property placeholders – if > possible – including OSGi Config Admin integration. > * Integrate with Turbine to enable the nice Hystrix dashboard. > (/) = done -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-9098) Camel Hystrix component
[ https://issues.apache.org/jira/browse/CAMEL-9098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213583#comment-15213583 ] Bilgin Ibryam commented on CAMEL-9098: -- I've done that already - SM-2887. Waiting for the bundle to be awailable this month on maven repo. > Camel Hystrix component > --- > > Key: CAMEL-9098 > URL: https://issues.apache.org/jira/browse/CAMEL-9098 > Project: Camel > Issue Type: New Feature >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 2.18.0 > > > Create a camel-hystrix component with the following features: > * (/) Capable of wrapping processors. > * (/) Capable of wrapping static endpoints: > ** (/) wrapping Endpoint objects. > ** (/) wrapping URIs. > * (/) Fluent builders to wrap processors and endpoints. > * Support building Hystrix endpoints with URIs. > * (/) Support fallback endpoints and processors. > * (/) Support response caching, where cache key is calculated by Camel > Expressions. > * (/) Support suppressing exceptions to avoid fallback via > HystrixBadRequestException. > * Request collapsing. > * (/) HystrixRequestContext propagation via Camel headers, to allow multiple > threads to share the HystrixRequestContext. > * Full support in OSGi (Hystrix, Archaius). > * Integrate Archaius configuration with Camel property placeholders – if > possible – including OSGi Config Admin integration. > * Integrate with Turbine to enable the nice Hystrix dashboard. > (/) = done -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7853) Implement AggregationRepository based on Infinispan data grid
[ https://issues.apache.org/jira/browse/CAMEL-7853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15154006#comment-15154006 ] Bilgin Ibryam commented on CAMEL-7853: -- There is no assignee. You are free to take it. > Implement AggregationRepository based on Infinispan data grid > - > > Key: CAMEL-7853 > URL: https://issues.apache.org/jira/browse/CAMEL-7853 > Project: Camel > Issue Type: Improvement > Components: camel-infinispan >Reporter: Bilgin Ibryam >Priority: Minor > Labels: newbie > Fix For: Future > > > Implement org.apache.camel.spi.AggregationRepository interface using > Infinispan libraries. This implementation will be useful for distributed > applicaitons aggregating messages withe the same repo. > For a reference check LevelDBAggregationRepository, > MemoryAggregationRepository and HazelcastAggregationRepository > implementations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (CAMEL-8243) Enhance the Infinispan module to add support for HotRod events
[ https://issues.apache.org/jira/browse/CAMEL-8243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-8243 started by Bilgin Ibryam. > Enhance the Infinispan module to add support for HotRod events > -- > > Key: CAMEL-8243 > URL: https://issues.apache.org/jira/browse/CAMEL-8243 > Project: Camel > Issue Type: Improvement > Components: camel-infinispan >Reporter: Tristan Tarrant >Assignee: Bilgin Ibryam > > HotRod 2.0 (included in Infinispan 7.0) has support for remote events. The > Infinispan component should be enhance to support this as well as embedded > events. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8243) Enhance the Infinispan module to add support for HotRod events
[ https://issues.apache.org/jira/browse/CAMEL-8243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam updated CAMEL-8243: - Component/s: camel-infinispan > Enhance the Infinispan module to add support for HotRod events > -- > > Key: CAMEL-8243 > URL: https://issues.apache.org/jira/browse/CAMEL-8243 > Project: Camel > Issue Type: Improvement > Components: camel-infinispan >Reporter: Tristan Tarrant >Assignee: Bilgin Ibryam > > HotRod 2.0 (included in Infinispan 7.0) has support for remote events. The > Infinispan component should be enhance to support this as well as embedded > events. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-7853) Implement AggregationRepository based on Infinispan data grid
[ https://issues.apache.org/jira/browse/CAMEL-7853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam updated CAMEL-7853: - Component/s: camel-infinispan > Implement AggregationRepository based on Infinispan data grid > - > > Key: CAMEL-7853 > URL: https://issues.apache.org/jira/browse/CAMEL-7853 > Project: Camel > Issue Type: Improvement > Components: camel-infinispan >Reporter: Bilgin Ibryam >Priority: Minor > Labels: newbie > Fix For: 2.15.0 > > > Implement org.apache.camel.spi.AggregationRepository interface using > Infinispan libraries. This implementation will be useful for distributed > applicaitons aggregating messages withe the same repo. > For a reference check LevelDBAggregationRepository, > MemoryAggregationRepository and HazelcastAggregationRepository > implementations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8244) Enhance the Infinispan module to add support for HotRod querying
[ https://issues.apache.org/jira/browse/CAMEL-8244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam updated CAMEL-8244: - Component/s: camel-infinispan > Enhance the Infinispan module to add support for HotRod querying > > > Key: CAMEL-8244 > URL: https://issues.apache.org/jira/browse/CAMEL-8244 > Project: Camel > Issue Type: Improvement > Components: camel-infinispan >Reporter: Tristan Tarrant >Assignee: Bilgin Ibryam > > HotRod 2.0 (included in Infinispan 7.0) has added support for remote > querying. The Camel Infinispan module should be enhanced to support this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-8244) Enhance the Infinispan module to add support for HotRod querying
[ https://issues.apache.org/jira/browse/CAMEL-8244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam reassigned CAMEL-8244: Assignee: Bilgin Ibryam > Enhance the Infinispan module to add support for HotRod querying > > > Key: CAMEL-8244 > URL: https://issues.apache.org/jira/browse/CAMEL-8244 > Project: Camel > Issue Type: Improvement >Reporter: Tristan Tarrant >Assignee: Bilgin Ibryam > > HotRod 2.0 (included in Infinispan 7.0) has added support for remote > querying. The Camel Infinispan module should be enhanced to support this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-8243) Enhance the Infinispan module to add support for HotRod events
[ https://issues.apache.org/jira/browse/CAMEL-8243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam reassigned CAMEL-8243: Assignee: Bilgin Ibryam > Enhance the Infinispan module to add support for HotRod events > -- > > Key: CAMEL-8243 > URL: https://issues.apache.org/jira/browse/CAMEL-8243 > Project: Camel > Issue Type: Improvement >Reporter: Tristan Tarrant >Assignee: Bilgin Ibryam > > HotRod 2.0 (included in Infinispan 7.0) has support for remote events. The > Infinispan component should be enhance to support this as well as embedded > events. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-5539) Circuit Breaker EIP
[ https://issues.apache.org/jira/browse/CAMEL-5539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185065#comment-14185065 ] Bilgin Ibryam commented on CAMEL-5539: -- Sounds like a good improvements to add. Feel free to create issues and do PRs > Circuit Breaker EIP > --- > > Key: CAMEL-5539 > URL: https://issues.apache.org/jira/browse/CAMEL-5539 > Project: Camel > Issue Type: New Feature > Components: camel-core, eip >Reporter: Claus Ibsen >Assignee: Raúl Kripalani > Fix For: Future > > Attachments: CAMEL-5539-output-82ef800.txt, CAMEL-5539-output.txt > > > Look at add the circuit breaker EIP to the Camel DSL. > http://davybrion.com/blog/2008/05/the-circuit-breaker/ > Would need some thoughts for that though. Either as an explicit in the DSL. > Or as a interceptor for sending to an endpoint. As explicit its a kind to the > load balancer (in fact it may be extended upon that). Either the LB selects > the intended target, or it select the breaker, which rejects executing the > message. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-7853) Implement AggregationRepository based on Infinispan data grid
[ https://issues.apache.org/jira/browse/CAMEL-7853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam updated CAMEL-7853: - Description: Implement org.apache.camel.spi.AggregationRepository interface using Infinispan libraries. This implementation will be useful for distributed applicaitons aggregating messages withe the same repo. For a reference check LevelDBAggregationRepository, MemoryAggregationRepository and HazelcastAggregationRepository implementations. was:The infinispan implementation will be useful for distributed applicaitons Labels: newbie (was: ) > Implement AggregationRepository based on Infinispan data grid > - > > Key: CAMEL-7853 > URL: https://issues.apache.org/jira/browse/CAMEL-7853 > Project: Camel > Issue Type: Improvement >Reporter: Bilgin Ibryam >Priority: Minor > Labels: newbie > Fix For: 2.15.0 > > > Implement org.apache.camel.spi.AggregationRepository interface using > Infinispan libraries. This implementation will be useful for distributed > applicaitons aggregating messages withe the same repo. > For a reference check LevelDBAggregationRepository, > MemoryAggregationRepository and HazelcastAggregationRepository > implementations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-7853) Implement AggregationRepository based on Infinispan data grid
Bilgin Ibryam created CAMEL-7853: Summary: Implement AggregationRepository based on Infinispan data grid Key: CAMEL-7853 URL: https://issues.apache.org/jira/browse/CAMEL-7853 Project: Camel Issue Type: Improvement Reporter: Bilgin Ibryam Priority: Minor Fix For: 2.15.0 The infinispan implementation will be useful for distributed applicaitons -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7220) Camel Schematron component
[ https://issues.apache.org/jira/browse/CAMEL-7220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144671#comment-14144671 ] Bilgin Ibryam commented on CAMEL-7220: -- Congrats on your first Camel component Ayache. Hopefully many more contributions to follow :) > Camel Schematron component > -- > > Key: CAMEL-7220 > URL: https://issues.apache.org/jira/browse/CAMEL-7220 > Project: Camel > Issue Type: New Feature >Reporter: ayache khettar >Assignee: Willem Jiang >Priority: Minor > Fix For: 2.14.0 > > > Hi > I would like to contribute apache camel components by introducing the > schematron engine. Here is a link to it in Github: > https://github.com/akhettar/camel/tree/master/components/camel-schematron > Comments and suggestions are welcome. > Regards, > Ayache -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7220) Camel Schematron component
[ https://issues.apache.org/jira/browse/CAMEL-7220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14086016#comment-14086016 ] Bilgin Ibryam commented on CAMEL-7220: -- can you try the same mvn command by adding "- U" ? > Camel Schematron component > -- > > Key: CAMEL-7220 > URL: https://issues.apache.org/jira/browse/CAMEL-7220 > Project: Camel > Issue Type: New Feature >Reporter: ayache khettar >Assignee: Bilgin Ibryam >Priority: Minor > > Hi > I would like to contribute apache camel components by introducing the > schematron engine. Here is a link to it in Github: > https://github.com/akhettar/camel/tree/master/components/camel-schematron > Comments and suggestions are welcome. > Regards, > Ayache -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7220) Camel Schematron component
[ https://issues.apache.org/jira/browse/CAMEL-7220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14083961#comment-14083961 ] Bilgin Ibryam commented on CAMEL-7220: -- Good job Ayache, Yes, you can generate the feature in platform/karaf foolder and build it to validate the feature. Can you also answer question number 7 above. Cheers, > Camel Schematron component > -- > > Key: CAMEL-7220 > URL: https://issues.apache.org/jira/browse/CAMEL-7220 > Project: Camel > Issue Type: New Feature >Reporter: ayache khettar >Assignee: Bilgin Ibryam >Priority: Minor > > Hi > I would like to contribute apache camel components by introducing the > schematron engine. Here is a link to it in Github: > https://github.com/akhettar/camel/tree/master/components/camel-schematron > Comments and suggestions are welcome. > Regards, > Ayache -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7220) Camel Schematron component
[ https://issues.apache.org/jira/browse/CAMEL-7220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14076773#comment-14076773 ] Bilgin Ibryam commented on CAMEL-7220: -- Dear Ayache, this is a great contribution. Can you do the following cleanup pls: 1. run mvn clean install -Pfastinstall,sourcecheck for your component and fix the warnings. 2. Add license header to camel-schematron/src/main/resources/META-INF/services/org/apache/camel/component/schematron file. Also to all the files, including test resources. 3. Update component pom to use only one version of Camel 4. Remove author refs in the source files 5. Rename contants package to constants 6. Do you really need saxon-dom? can you remove that dependency and replace net.sf.saxon.FeatureKeys with net.sf.saxon.lib.FeatureKeys? With that change tests seem to pass fine. 7. Can you provide a link to where you get the copy of all the resources in camel-schematron/src/main/resources/iso-schematron-xslt2 folder, so we can verify their license. 8. Change the constant values so they are consistent with other components, ie start with CamelSchematron Thanks, > Camel Schematron component > -- > > Key: CAMEL-7220 > URL: https://issues.apache.org/jira/browse/CAMEL-7220 > Project: Camel > Issue Type: New Feature >Reporter: ayache khettar >Assignee: Bilgin Ibryam >Priority: Minor > > Hi > I would like to contribute apache camel components by introducing the > schematron engine. Here is a link to it in Github: > https://github.com/akhettar/camel/tree/master/components/camel-schematron > Comments and suggestions are welcome. > Regards, > Ayache -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7297) Add remote querying feature to camel-infinispan component
[ https://issues.apache.org/jira/browse/CAMEL-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040950#comment-14040950 ] Bilgin Ibryam commented on CAMEL-7297: -- [~davsclaus]Thanks for taking care of the licensing issue. I will check whether there is another implementation. > Add remote querying feature to camel-infinispan component > - > > Key: CAMEL-7297 > URL: https://issues.apache.org/jira/browse/CAMEL-7297 > Project: Camel > Issue Type: New Feature >Reporter: Bilgin Ibryam >Assignee: Bilgin Ibryam >Priority: Minor > Fix For: 2.14.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CAMEL-6999) Camel component for dropbox integration
[ https://issues.apache.org/jira/browse/CAMEL-6999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam reassigned CAMEL-6999: Assignee: Henryk Konsek (was: Bilgin Ibryam) Assigning to Henryk as he already took good care of this issue. Component page is remaining still. > Camel component for dropbox integration > --- > > Key: CAMEL-6999 > URL: https://issues.apache.org/jira/browse/CAMEL-6999 > Project: Camel > Issue Type: New Feature >Affects Versions: 2.12.1 >Reporter: Giovanni Marigi >Assignee: Henryk Konsek >Priority: Minor > Labels: camel, dropbox > Fix For: Future > > > Create a camel component (producers and consumers ) for dropbox integration -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-5539) Circuit Breaker EIP
[ https://issues.apache.org/jira/browse/CAMEL-5539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967887#comment-13967887 ] Bilgin Ibryam commented on CAMEL-5539: -- My implementation is completed but I'll leave this issue open in case other implementation as mentioned above are to be added. > Circuit Breaker EIP > --- > > Key: CAMEL-5539 > URL: https://issues.apache.org/jira/browse/CAMEL-5539 > Project: Camel > Issue Type: New Feature > Components: camel-core, eip >Reporter: Claus Ibsen >Assignee: Raúl Kripalani > Fix For: Future > > Attachments: CAMEL-5539-output-82ef800.txt, CAMEL-5539-output.txt > > > Look at add the circuit breaker EIP to the Camel DSL. > http://davybrion.com/blog/2008/05/the-circuit-breaker/ > Would need some thoughts for that though. Either as an explicit in the DSL. > Or as a interceptor for sending to an endpoint. As explicit its a kind to the > load balancer (in fact it may be extended upon that). Either the LB selects > the intended target, or it select the breaker, which rejects executing the > message. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-5539) Circuit Breaker EIP
[ https://issues.apache.org/jira/browse/CAMEL-5539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13961342#comment-13961342 ] Bilgin Ibryam commented on CAMEL-5539: -- Sorry for that, it is fixed now. > Circuit Breaker EIP > --- > > Key: CAMEL-5539 > URL: https://issues.apache.org/jira/browse/CAMEL-5539 > Project: Camel > Issue Type: New Feature > Components: camel-core, eip >Reporter: Claus Ibsen >Assignee: Raúl Kripalani > Fix For: Future > > Attachments: CAMEL-5539-output.txt > > > Look at add the circuit breaker EIP to the Camel DSL. > http://davybrion.com/blog/2008/05/the-circuit-breaker/ > Would need some thoughts for that though. Either as an explicit in the DSL. > Or as a interceptor for sending to an endpoint. As explicit its a kind to the > load balancer (in fact it may be extended upon that). Either the LB selects > the intended target, or it select the breaker, which rejects executing the > message. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-5539) Circuit Breaker EIP
[ https://issues.apache.org/jira/browse/CAMEL-5539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13961108#comment-13961108 ] Bilgin Ibryam commented on CAMEL-5539: -- I've implemented a simple version of circuit breaker pattern a load balancer policy. Let me know what you think. > Circuit Breaker EIP > --- > > Key: CAMEL-5539 > URL: https://issues.apache.org/jira/browse/CAMEL-5539 > Project: Camel > Issue Type: New Feature > Components: camel-core, eip >Reporter: Claus Ibsen >Assignee: Raúl Kripalani > Fix For: Future > > > Look at add the circuit breaker EIP to the Camel DSL. > http://davybrion.com/blog/2008/05/the-circuit-breaker/ > Would need some thoughts for that though. Either as an explicit in the DSL. > Or as a interceptor for sending to an endpoint. As explicit its a kind to the > load balancer (in fact it may be extended upon that). Either the LB selects > the intended target, or it select the breaker, which rejects executing the > message. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Reopened] (CAMEL-7297) Add remote querying feature to camel-infinispan component
[ https://issues.apache.org/jira/browse/CAMEL-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam reopened CAMEL-7297: -- http://camel.465427.n5.nabble.com/Re-git-commit-CAMEL-7297-Add-remote-querying-feature-to-camel-infinispan-component-tt5748863.html > Add remote querying feature to camel-infinispan component > - > > Key: CAMEL-7297 > URL: https://issues.apache.org/jira/browse/CAMEL-7297 > Project: Camel > Issue Type: New Feature >Reporter: Bilgin Ibryam >Assignee: Bilgin Ibryam >Priority: Minor > Fix For: 2.13.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CAMEL-7297) Add remote querying feature to camel-infinispan component
[ https://issues.apache.org/jira/browse/CAMEL-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam closed CAMEL-7297. > Add remote querying feature to camel-infinispan component > - > > Key: CAMEL-7297 > URL: https://issues.apache.org/jira/browse/CAMEL-7297 > Project: Camel > Issue Type: New Feature >Reporter: Bilgin Ibryam >Assignee: Bilgin Ibryam >Priority: Minor > Fix For: 2.13.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CAMEL-7297) Add remote querying feature to camel-infinispan component
[ https://issues.apache.org/jira/browse/CAMEL-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam resolved CAMEL-7297. -- Resolution: Fixed > Add remote querying feature to camel-infinispan component > - > > Key: CAMEL-7297 > URL: https://issues.apache.org/jira/browse/CAMEL-7297 > Project: Camel > Issue Type: New Feature >Reporter: Bilgin Ibryam >Assignee: Bilgin Ibryam >Priority: Minor > Fix For: 2.13.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7297) Add remote querying feature to camel-infinispan component
Bilgin Ibryam created CAMEL-7297: Summary: Add remote querying feature to camel-infinispan component Key: CAMEL-7297 URL: https://issues.apache.org/jira/browse/CAMEL-7297 Project: Camel Issue Type: New Feature Reporter: Bilgin Ibryam Assignee: Bilgin Ibryam Priority: Minor Fix For: 2.13.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CAMEL-7220) Camel Schematron component
[ https://issues.apache.org/jira/browse/CAMEL-7220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam reassigned CAMEL-7220: Assignee: Bilgin Ibryam > Camel Schematron component > -- > > Key: CAMEL-7220 > URL: https://issues.apache.org/jira/browse/CAMEL-7220 > Project: Camel > Issue Type: New Feature >Reporter: ayache khettar >Assignee: Bilgin Ibryam >Priority: Minor > > Hi > I would like to contribute apache camel components by introducing the > schematron engine. Here is a link to it in Github: > https://github.com/akhettar/camel/tree/master/components/camel-schematron > Comments and suggestions are welcome. > Regards, > Ayache -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (CAMEL-6999) Camel component for dropbox integration
[ https://issues.apache.org/jira/browse/CAMEL-6999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam reassigned CAMEL-6999: Assignee: Bilgin Ibryam > Camel component for dropbox integration > --- > > Key: CAMEL-6999 > URL: https://issues.apache.org/jira/browse/CAMEL-6999 > Project: Camel > Issue Type: New Feature >Affects Versions: 2.12.1 >Reporter: Giovanni Marigi >Assignee: Bilgin Ibryam >Priority: Minor > Labels: camel, dropbox > Fix For: Future > > > Create a camel component (producers and consumers ) for dropbox integration -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CAMEL-6726) Camel-Redis: Serializer passed through URI is used only on consumer
[ https://issues.apache.org/jira/browse/CAMEL-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam resolved CAMEL-6726. -- Resolution: Fixed > Camel-Redis: Serializer passed through URI is used only on consumer > --- > > Key: CAMEL-6726 > URL: https://issues.apache.org/jira/browse/CAMEL-6726 > Project: Camel > Issue Type: Bug >Affects Versions: 2.11.1 >Reporter: Tommaso Schiavinotto >Assignee: Bilgin Ibryam >Priority: Minor > Fix For: 2.11.2, 2.12.1, 2.13.0 > > > *Please add camel-redis component* > The serializer passed through URI is used only on consumer and not on > producer. Beside been unexpected and undocumented I think it can cause > problems on interacting with the Redis DB if the same serializer is not used > in both ways. > You can find the example and discussion of this problem on this thread on the > forum: > http://camel.465427.n5.nabble.com/camel-redis-strings-serialization-td5738994.html > I put as minor because from the discussion it looks like it is possible to > have a workaround using a RedisTemplate. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAMEL-6726) Camel-Redis: Serializer passed through URI is used only on consumer
[ https://issues.apache.org/jira/browse/CAMEL-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam reassigned CAMEL-6726: Assignee: Bilgin Ibryam > Camel-Redis: Serializer passed through URI is used only on consumer > --- > > Key: CAMEL-6726 > URL: https://issues.apache.org/jira/browse/CAMEL-6726 > Project: Camel > Issue Type: Bug >Affects Versions: 2.11.1 >Reporter: Tommaso Schiavinotto >Assignee: Bilgin Ibryam >Priority: Minor > Fix For: 2.11.2, 2.12.1, 2.13.0 > > > *Please add camel-redis component* > The serializer passed through URI is used only on consumer and not on > producer. Beside been unexpected and undocumented I think it can cause > problems on interacting with the Redis DB if the same serializer is not used > in both ways. > You can find the example and discussion of this problem on this thread on the > forum: > http://camel.465427.n5.nabble.com/camel-redis-strings-serialization-td5738994.html > I put as minor because from the discussion it looks like it is possible to > have a workaround using a RedisTemplate. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-3096) Create a simple example for JDBC - camel-example-jdbc
[ https://issues.apache.org/jira/browse/CAMEL-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13744933#comment-13744933 ] Bilgin Ibryam commented on CAMEL-3096: -- FYI I added restlet-jdbc example based on https://github.com/bibryam/camel-example-restlet-jdbc > Create a simple example for JDBC - camel-example-jdbc > - > > Key: CAMEL-3096 > URL: https://issues.apache.org/jira/browse/CAMEL-3096 > Project: Camel > Issue Type: New Feature > Components: examples >Reporter: Claus Ibsen > Fix For: Future > > Attachments: CAMEL-3096.patch, CAMEL-3096_v2.patch > > > A simple JDBC example using camel-jdbc (Spring JdbcTemplate) which is a > really good JdbcTemplate. > And show how to deply and run it in OSGi. > The other database examples is based on jpa crapola which is complex and > overkill for most people. So having an easy to understand and use example > would be great. > We can use an in memory database such as HSQLDB. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-6001) Provide documentation for the new camel-redis component
[ https://issues.apache.org/jira/browse/CAMEL-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam resolved CAMEL-6001. -- Resolution: Fixed Thanks Babak All done. Bilgin > Provide documentation for the new camel-redis component > --- > > Key: CAMEL-6001 > URL: https://issues.apache.org/jira/browse/CAMEL-6001 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Babak Vahdat >Assignee: Bilgin Ibryam > Fix For: 2.11.0 > > > Also need to mention it by the release notes as a new Camel component: > http://camel.apache.org/camel-2110-release.html#Camel2.11.0Release-NewComponents -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAMEL-6001) Provide documentation for the new camel-redis component
[ https://issues.apache.org/jira/browse/CAMEL-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam reassigned CAMEL-6001: Assignee: Bilgin Ibryam > Provide documentation for the new camel-redis component > --- > > Key: CAMEL-6001 > URL: https://issues.apache.org/jira/browse/CAMEL-6001 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Babak Vahdat >Assignee: Bilgin Ibryam > Fix For: 2.11.0 > > > Also need to mention it by the release notes as a new Camel component: > http://camel.apache.org/camel-2110-release.html#Camel2.11.0Release-NewComponents -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5483) Component for neo4j
[ https://issues.apache.org/jira/browse/CAMEL-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448564#comment-13448564 ] Bilgin Ibryam commented on CAMEL-5483: -- Thanks Babak. I didn't know that MANIFEST.MF can tell you whether it is OSGI bundled or not. Exactly what I was looking for. > Component for neo4j > --- > > Key: CAMEL-5483 > URL: https://issues.apache.org/jira/browse/CAMEL-5483 > Project: Camel > Issue Type: Improvement >Reporter: stephen samuel >Assignee: Willem Jiang >Priority: Minor > Fix For: 2.11.0 > > Attachments: camel-neo4j.patch, remove-int-tests.patch > > > I have created a component for neo4j. It is a producer only and it allows you > to create / remove nodes and relationships. > -- read me -- > camel-neo4j > > The camel-neo4j component allows you to treat Neo4j as a camel producer > endpoint. This means you can use this component in to() calls but not from() > calls. This component is backed by the Spring Data Neo4j Library. > * As a producer, can create or remove nodes, and create or remove > relationships. > * Can support as many endpoints as required, eg for multiple databases across > multiple instances. > * Headers set for node id (for created nodes), relationship id (for created > relationships) > How to Use > == > You can use neo4j as an endpoint with the following URI. > `neo4j:http://hostname[:port]/database` > Then you need to set a header on each message, one of the following enum types > ` CREATE_NODE, > REMOVE_NODE, > CREATE_RELATIONSHIP, > REMOVE_RELATIONSHIP` > Eg, > `exchange.getIn().setHeader(Neo4jEndpoint.HEADER_OPERATION, > Neo4jOperation.CREATE_NODE);` > The body of the message is used to determine the node or relationship to > manipulate. The following body types are supported: > For CREATE_NODE: > * null body - create default node > * Map body - create node with the properties set from the map > For REMOVE_NODE: > * Long or Integer - remove node using the body as the id > * neo4j Node instance - remove the node specified by that instance > For CREATE_RELATIONSHIP: > * SpringDataRelationship - create relationship specified by any @NodeEntity > annoted Spring entities. > * BasicRelationship - create relationship specified by the neo4j node types > For REMOVE_RELATIONSHIP: > * Long or Integer - remove relationship using the body as the id > * SpringDataRelationship - remove relationship specified by the @NodeEntity > annoted Spring entities. > * BasicRelationship - remove relationship specified by the neo4j node types > Tests > = > camel-neo4j has a complete set of unit tests. In addition there are some > integration tests that require you to run a local instance of neo4j. By > default the tests will look at localhost:7474 on > http://localhost:7474/db/data/ > - Initial contribution by Stephen Samuel. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5483) Component for neo4j
[ https://issues.apache.org/jira/browse/CAMEL-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444128#comment-13444128 ] Bilgin Ibryam commented on CAMEL-5483: -- Guys, I have a question: how do you find out whether a/this new component requires some new OSGI bundles or not? Shouldn't it also be added to features.xml in platfor/karaf? Thanks > Component for neo4j > --- > > Key: CAMEL-5483 > URL: https://issues.apache.org/jira/browse/CAMEL-5483 > Project: Camel > Issue Type: Improvement >Reporter: stephen samuel >Assignee: Willem Jiang >Priority: Minor > Fix For: 2.11.0 > > Attachments: camel-neo4j.patch, remove-int-tests.patch > > > I have created a component for neo4j. It is a producer only and it allows you > to create / remove nodes and relationships. > -- read me -- > camel-neo4j > > The camel-neo4j component allows you to treat Neo4j as a camel producer > endpoint. This means you can use this component in to() calls but not from() > calls. This component is backed by the Spring Data Neo4j Library. > * As a producer, can create or remove nodes, and create or remove > relationships. > * Can support as many endpoints as required, eg for multiple databases across > multiple instances. > * Headers set for node id (for created nodes), relationship id (for created > relationships) > How to Use > == > You can use neo4j as an endpoint with the following URI. > `neo4j:http://hostname[:port]/database` > Then you need to set a header on each message, one of the following enum types > ` CREATE_NODE, > REMOVE_NODE, > CREATE_RELATIONSHIP, > REMOVE_RELATIONSHIP` > Eg, > `exchange.getIn().setHeader(Neo4jEndpoint.HEADER_OPERATION, > Neo4jOperation.CREATE_NODE);` > The body of the message is used to determine the node or relationship to > manipulate. The following body types are supported: > For CREATE_NODE: > * null body - create default node > * Map body - create node with the properties set from the map > For REMOVE_NODE: > * Long or Integer - remove node using the body as the id > * neo4j Node instance - remove the node specified by that instance > For CREATE_RELATIONSHIP: > * SpringDataRelationship - create relationship specified by any @NodeEntity > annoted Spring entities. > * BasicRelationship - create relationship specified by the neo4j node types > For REMOVE_RELATIONSHIP: > * Long or Integer - remove relationship using the body as the id > * SpringDataRelationship - remove relationship specified by the @NodeEntity > annoted Spring entities. > * BasicRelationship - remove relationship specified by the neo4j node types > Tests > = > camel-neo4j has a complete set of unit tests. In addition there are some > integration tests that require you to run a local instance of neo4j. By > default the tests will look at localhost:7474 on > http://localhost:7474/db/data/ > - Initial contribution by Stephen Samuel. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4691) New camel-cmis component
[ https://issues.apache.org/jira/browse/CAMEL-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13428478#comment-13428478 ] Bilgin Ibryam commented on CAMEL-4691: -- Thanks Willem, enjoy your holiday :) > New camel-cmis component > > > Key: CAMEL-4691 > URL: https://issues.apache.org/jira/browse/CAMEL-4691 > Project: Camel > Issue Type: New Feature >Reporter: Bilgin Ibryam >Assignee: Bilgin Ibryam >Priority: Minor > Attachments: camel-cmis.patch, camel-cmis.patch, camel-cmis.patch > > > A new component that would allow Camel to connect to content > repositories(like Alfresco, SharePoint, OpenText) supporting CMIS > specification. > This component can be an alternative to camel-jcr (which actually can only > create node) for accessing content repositories. > The consumer can retrieve content using CMIS queries (very similar to SQL) or > traverse the content tree from root to leaves. > The producer is capable of creating nodes on the server (folders, docs...) > and also executing CMIS queries from the message body. > It is using another Apache project - OpenCMIS client libraries from Apache > Chemistry (also the in-memory-server from the same project for unit tests) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4691) New camel-cmis component
[ https://issues.apache.org/jira/browse/CAMEL-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427792#comment-13427792 ] Bilgin Ibryam commented on CAMEL-4691: -- Willem, is there any progress with the osgi dependencies? The documentation is in place already. > New camel-cmis component > > > Key: CAMEL-4691 > URL: https://issues.apache.org/jira/browse/CAMEL-4691 > Project: Camel > Issue Type: New Feature >Reporter: Bilgin Ibryam >Assignee: Bilgin Ibryam >Priority: Minor > Attachments: camel-cmis.patch, camel-cmis.patch, camel-cmis.patch > > > A new component that would allow Camel to connect to content > repositories(like Alfresco, SharePoint, OpenText) supporting CMIS > specification. > This component can be an alternative to camel-jcr (which actually can only > create node) for accessing content repositories. > The consumer can retrieve content using CMIS queries (very similar to SQL) or > traverse the content tree from root to leaves. > The producer is capable of creating nodes on the server (folders, docs...) > and also executing CMIS queries from the message body. > It is using another Apache project - OpenCMIS client libraries from Apache > Chemistry (also the in-memory-server from the same project for unit tests) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4691) New camel-cmis component
[ https://issues.apache.org/jira/browse/CAMEL-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417121#comment-13417121 ] Bilgin Ibryam commented on CAMEL-4691: -- Thanks Willem. I will update the docs (probably this weekend when I find some time) > New camel-cmis component > > > Key: CAMEL-4691 > URL: https://issues.apache.org/jira/browse/CAMEL-4691 > Project: Camel > Issue Type: New Feature >Reporter: Bilgin Ibryam >Assignee: Bilgin Ibryam >Priority: Minor > Attachments: camel-cmis.patch, camel-cmis.patch, camel-cmis.patch > > > A new component that would allow Camel to connect to content > repositories(like Alfresco, SharePoint, OpenText) supporting CMIS > specification. > This component can be an alternative to camel-jcr (which actually can only > create node) for accessing content repositories. > The consumer can retrieve content using CMIS queries (very similar to SQL) or > traverse the content tree from root to leaves. > The producer is capable of creating nodes on the server (folders, docs...) > and also executing CMIS queries from the message body. > It is using another Apache project - OpenCMIS client libraries from Apache > Chemistry (also the in-memory-server from the same project for unit tests) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4691) New camel-cmis component
[ https://issues.apache.org/jira/browse/CAMEL-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416946#comment-13416946 ] Bilgin Ibryam commented on CAMEL-4691: -- Sounds good, but is it good idea to commit code that fails the features validation? > New camel-cmis component > > > Key: CAMEL-4691 > URL: https://issues.apache.org/jira/browse/CAMEL-4691 > Project: Camel > Issue Type: New Feature >Reporter: Bilgin Ibryam >Assignee: Bilgin Ibryam >Priority: Minor > Attachments: camel-cmis.patch, camel-cmis.patch, camel-cmis.patch > > > A new component that would allow Camel to connect to content > repositories(like Alfresco, SharePoint, OpenText) supporting CMIS > specification. > This component can be an alternative to camel-jcr (which actually can only > create node) for accessing content repositories. > The consumer can retrieve content using CMIS queries (very similar to SQL) or > traverse the content tree from root to leaves. > The producer is capable of creating nodes on the server (folders, docs...) > and also executing CMIS queries from the message body. > It is using another Apache project - OpenCMIS client libraries from Apache > Chemistry (also the in-memory-server from the same project for unit tests) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4691) New camel-cmis component
[ https://issues.apache.org/jira/browse/CAMEL-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416941#comment-13416941 ] Bilgin Ibryam commented on CAMEL-4691: -- TIA Willem. I will improve the implementation of the component further, blocked only with the OSGI stuff. > New camel-cmis component > > > Key: CAMEL-4691 > URL: https://issues.apache.org/jira/browse/CAMEL-4691 > Project: Camel > Issue Type: New Feature >Reporter: Bilgin Ibryam >Assignee: Bilgin Ibryam >Priority: Minor > Attachments: camel-cmis.patch, camel-cmis.patch, camel-cmis.patch > > > A new component that would allow Camel to connect to content > repositories(like Alfresco, SharePoint, OpenText) supporting CMIS > specification. > This component can be an alternative to camel-jcr (which actually can only > create node) for accessing content repositories. > The consumer can retrieve content using CMIS queries (very similar to SQL) or > traverse the content tree from root to leaves. > The producer is capable of creating nodes on the server (folders, docs...) > and also executing CMIS queries from the message body. > It is using another Apache project - OpenCMIS client libraries from Apache > Chemistry (also the in-memory-server from the same project for unit tests) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-4691) New camel-cmis component
[ https://issues.apache.org/jira/browse/CAMEL-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam updated CAMEL-4691: - Attachment: camel-cmis.patch > New camel-cmis component > > > Key: CAMEL-4691 > URL: https://issues.apache.org/jira/browse/CAMEL-4691 > Project: Camel > Issue Type: New Feature >Reporter: Bilgin Ibryam >Assignee: Bilgin Ibryam >Priority: Minor > Attachments: camel-cmis.patch, camel-cmis.patch, camel-cmis.patch > > > A new component that would allow Camel to connect to content > repositories(like Alfresco, SharePoint, OpenText) supporting CMIS > specification. > This component can be an alternative to camel-jcr (which actually can only > create node) for accessing content repositories. > The consumer can retrieve content using CMIS queries (very similar to SQL) or > traverse the content tree from root to leaves. > The producer is capable of creating nodes on the server (folders, docs...) > and also executing CMIS queries from the message body. > It is using another Apache project - OpenCMIS client libraries from Apache > Chemistry (also the in-memory-server from the same project for unit tests) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-4691) New camel-cmis component
[ https://issues.apache.org/jira/browse/CAMEL-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam updated CAMEL-4691: - Attachment: camel-cmis.patch Updated patch. Still have issues with validating the features.xml > New camel-cmis component > > > Key: CAMEL-4691 > URL: https://issues.apache.org/jira/browse/CAMEL-4691 > Project: Camel > Issue Type: New Feature >Reporter: Bilgin Ibryam >Assignee: Bilgin Ibryam >Priority: Minor > Attachments: camel-cmis.patch, camel-cmis.patch > > > A new component that would allow Camel to connect to content > repositories(like Alfresco, SharePoint, OpenText) supporting CMIS > specification. > This component can be an alternative to camel-jcr (which actually can only > create node) for accessing content repositories. > The consumer can retrieve content using CMIS queries (very similar to SQL) or > traverse the content tree from root to leaves. > The producer is capable of creating nodes on the server (folders, docs...) > and also executing CMIS queries from the message body. > It is using another Apache project - OpenCMIS client libraries from Apache > Chemistry (also the in-memory-server from the same project for unit tests) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4691) New camel-cmis component
[
https://issues.apache.org/jira/browse/CAMEL-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414806#comment-13414806
]
Bilgin Ibryam commented on CAMEL-4691:
--
I am trying to add the new component to Camel but struggled with OSGI:
Looking at http://chemistry.apache.org/java/developing/dev-osgi.html
opencmis seems to be already osgi bundled. So I added the following lines in
features.xml
camel-core
mvn:org.apache.chemistry.opencmis/chemistry-opencmis-osgi-server/${cmis-bundle-version}
mvn:org.apache.camel/camel-cmis/${project.version}
But when I try to validate the features, I get the following error:
[WARNING] Failed to validate feature camel-cmis
[WARNING] No export found to match org.apache.chemistry.opencmis.client.runtime
(imported by mvn:org.apache.camel/camel-cmis/2.11-SNAPSHOT)
[WARNING] No export found to match javax.xml.ws.soap (imported by
mvn:org.apache.chemistry.opencmis/chemistry-opencmis-osgi-server/0.5.0)
[WARNING] No export found to match javax.xml.ws (imported by
mvn:org.apache.chemistry.opencmis/chemistry-opencmis-osgi-server/0.5.0)
[WARNING] No export found to match javax.xml.ws.handler (imported by
mvn:org.apache.chemistry.opencmis/chemistry-opencmis-osgi-server/0.5.0)
[WARNING] No export found to match
org.apache.chemistry.opencmis.client.api;version="[0.5,1)" (imported by
mvn:org.apache.camel/camel-cmis/2.11-SNAPSHOT)
[WARNING] No export found to match javax.jws (imported by
mvn:org.apache.chemistry.opencmis/chemistry-opencmis-osgi-server/0.5.0)
Any help on how to fix this or features.xml or how to find existing osgi
bundles is greatly appreciated.
> New camel-cmis component
>
>
> Key: CAMEL-4691
> URL: https://issues.apache.org/jira/browse/CAMEL-4691
> Project: Camel
> Issue Type: New Feature
>Reporter: Bilgin Ibryam
>Assignee: Bilgin Ibryam
>Priority: Minor
> Attachments: camel-cmis.patch
>
>
> A new component that would allow Camel to connect to content
> repositories(like Alfresco, SharePoint, OpenText) supporting CMIS
> specification.
> This component can be an alternative to camel-jcr (which actually can only
> create node) for accessing content repositories.
> The consumer can retrieve content using CMIS queries (very similar to SQL) or
> traverse the content tree from root to leaves.
> The producer is capable of creating nodes on the server (folders, docs...)
> and also executing CMIS queries from the message body.
> It is using another Apache project - OpenCMIS client libraries from Apache
> Chemistry (also the in-memory-server from the same project for unit tests)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAMEL-4691) New camel-cmis component
[ https://issues.apache.org/jira/browse/CAMEL-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam reassigned CAMEL-4691: Assignee: Bilgin Ibryam > New camel-cmis component > > > Key: CAMEL-4691 > URL: https://issues.apache.org/jira/browse/CAMEL-4691 > Project: Camel > Issue Type: New Feature >Reporter: Bilgin Ibryam >Assignee: Bilgin Ibryam >Priority: Minor > Attachments: camel-cmis.patch > > > A new component that would allow Camel to connect to content > repositories(like Alfresco, SharePoint, OpenText) supporting CMIS > specification. > This component can be an alternative to camel-jcr (which actually can only > create node) for accessing content repositories. > The consumer can retrieve content using CMIS queries (very similar to SQL) or > traverse the content tree from root to leaves. > The producer is capable of creating nodes on the server (folders, docs...) > and also executing CMIS queries from the message body. > It is using another Apache project - OpenCMIS client libraries from Apache > Chemistry (also the in-memory-server from the same project for unit tests) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5155) Support JCR Component as Consumer
[ https://issues.apache.org/jira/browse/CAMEL-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261418#comment-13261418 ] Bilgin Ibryam commented on CAMEL-5155: -- You documented pretty well the java classes, I will add them to the wiki. The latest jcr code is in trunk, have a look here http://camel.apache.org/how-can-i-get-the-source-code.html I was thinking how this jcr consumer would be helpful, and once you got a list of jcr Event, and for example if it is an update/add operation, the next thing user wants to do would be to retrieve this node from jcr in order to do some action with it. So I think extending the jcr producer with ability to read nodes by a given id/path from the event might be helpful. WDYT? Also are you using currently the Consumer, I wonder what is your use case to listen only for events, w/o retrieving the actual nodes? > Support JCR Component as Consumer > - > > Key: CAMEL-5155 > URL: https://issues.apache.org/jira/browse/CAMEL-5155 > Project: Camel > Issue Type: New Feature > Components: camel-jcr >Affects Versions: 2.9.1 >Reporter: Woonsan Ko >Assignee: Bilgin Ibryam > Fix For: 2.10.0 > > Attachments: jcr-consumer-patch-2.txt, jcr-consumer-patch.txt > > > I tried to use jcr component as consumer, expecting jcr observation event > listener like behavior, but I realized that it's not supported yet. The > current jcr component supports producer only. So, I'm considering to > implement JcrConsumer an contribute a patch. > My idea is as follows: > i) the uri format is the same. e.g. > 'jcr://user:password@repository/absolute/path/from/node'; the node path is > used for javax.jcr.observation.ObservationManager#addEventListener(..., > absPath, ...). > ii) additionally, we need parameters for eventTypes, isDeep, uuid[], > nodeTypeName[], noLocal parameters (See #addEventListener() for detail). > For example, we may probably use somethings like > 'jcr://user:password@repository/absolute/path/from/node?nodeTypeName=demo:news&eventTypes=3&isDeep=true. > iii) JcrConsumer registers JCR observation event listener from the specified > uri information. > iv) When events notified, I think it can simply return a list of > javax.jcr.observation.Event objects in IN message. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5155) Support JCR Component as Consumer
[ https://issues.apache.org/jira/browse/CAMEL-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261243#comment-13261243 ] Bilgin Ibryam commented on CAMEL-5155: -- Woonsan, I committed your patch, but will keep the ticket open till the documentation is updated. Thanks again, > Support JCR Component as Consumer > - > > Key: CAMEL-5155 > URL: https://issues.apache.org/jira/browse/CAMEL-5155 > Project: Camel > Issue Type: New Feature > Components: camel-jcr >Affects Versions: 2.9.1 >Reporter: Woonsan Ko >Assignee: Bilgin Ibryam > Fix For: 2.10.0 > > Attachments: jcr-consumer-patch-2.txt, jcr-consumer-patch.txt > > > I tried to use jcr component as consumer, expecting jcr observation event > listener like behavior, but I realized that it's not supported yet. The > current jcr component supports producer only. So, I'm considering to > implement JcrConsumer an contribute a patch. > My idea is as follows: > i) the uri format is the same. e.g. > 'jcr://user:password@repository/absolute/path/from/node'; the node path is > used for javax.jcr.observation.ObservationManager#addEventListener(..., > absPath, ...). > ii) additionally, we need parameters for eventTypes, isDeep, uuid[], > nodeTypeName[], noLocal parameters (See #addEventListener() for detail). > For example, we may probably use somethings like > 'jcr://user:password@repository/absolute/path/from/node?nodeTypeName=demo:news&eventTypes=3&isDeep=true. > iii) JcrConsumer registers JCR observation event listener from the specified > uri information. > iv) When events notified, I think it can simply return a list of > javax.jcr.observation.Event objects in IN message. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5155) Support JCR Component as Consumer
[
https://issues.apache.org/jira/browse/CAMEL-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259084#comment-13259084
]
Bilgin Ibryam commented on CAMEL-5155:
--
Hi Woonsan,
I'm looking at your patch, great job.
I have question though: in JcrConsumer.JcrConsumerSessionListenerChecker.run()
why are you calling unregisterListenerAndLogoutSession when there is no live
session?
if (!isSessionLive && isObservationListeningAllowed()) {
unregisterListenerAndLogoutSession();
...
}
Bilgin
> Support JCR Component as Consumer
> -
>
> Key: CAMEL-5155
> URL: https://issues.apache.org/jira/browse/CAMEL-5155
> Project: Camel
> Issue Type: New Feature
> Components: camel-jcr
>Affects Versions: 2.9.1
>Reporter: Woonsan Ko
>Assignee: Bilgin Ibryam
> Fix For: 2.10.0
>
> Attachments: jcr-consumer-patch.txt
>
>
> I tried to use jcr component as consumer, expecting jcr observation event
> listener like behavior, but I realized that it's not supported yet. The
> current jcr component supports producer only. So, I'm considering to
> implement JcrConsumer an contribute a patch.
> My idea is as follows:
> i) the uri format is the same. e.g.
> 'jcr://user:password@repository/absolute/path/from/node'; the node path is
> used for javax.jcr.observation.ObservationManager#addEventListener(...,
> absPath, ...).
> ii) additionally, we need parameters for eventTypes, isDeep, uuid[],
> nodeTypeName[], noLocal parameters (See #addEventListener() for detail).
> For example, we may probably use somethings like
> 'jcr://user:password@repository/absolute/path/from/node?nodeTypeName=demo:news&eventTypes=3&isDeep=true.
> iii) JcrConsumer registers JCR observation event listener from the specified
> uri information.
> iv) When events notified, I think it can simply return a list of
> javax.jcr.observation.Event objects in IN message.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAMEL-5155) Support JCR Component as Consumer
[ https://issues.apache.org/jira/browse/CAMEL-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam reassigned CAMEL-5155: Assignee: Bilgin Ibryam > Support JCR Component as Consumer > - > > Key: CAMEL-5155 > URL: https://issues.apache.org/jira/browse/CAMEL-5155 > Project: Camel > Issue Type: New Feature > Components: camel-jcr >Affects Versions: 2.9.1 >Reporter: Woonsan Ko >Assignee: Bilgin Ibryam > Fix For: 2.10.0 > > Attachments: jcr-consumer-patch.txt > > > I tried to use jcr component as consumer, expecting jcr observation event > listener like behavior, but I realized that it's not supported yet. The > current jcr component supports producer only. So, I'm considering to > implement JcrConsumer an contribute a patch. > My idea is as follows: > i) the uri format is the same. e.g. > 'jcr://user:password@repository/absolute/path/from/node'; the node path is > used for javax.jcr.observation.ObservationManager#addEventListener(..., > absPath, ...). > ii) additionally, we need parameters for eventTypes, isDeep, uuid[], > nodeTypeName[], noLocal parameters (See #addEventListener() for detail). > For example, we may probably use somethings like > 'jcr://user:password@repository/absolute/path/from/node?nodeTypeName=demo:news&eventTypes=3&isDeep=true. > iii) JcrConsumer registers JCR observation event listener from the specified > uri information. > iv) When events notified, I think it can simply return a list of > javax.jcr.observation.Event objects in IN message. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
