[jira] [Commented] (CAMEL-9379) Camel BOM should not include tooling depdencies
[ https://issues.apache.org/jira/browse/CAMEL-9379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15033279#comment-15033279 ] Ioannis Canellos commented on CAMEL-9379: - In general its a good idea to separate the parent pom from the bom. The one is for internal use while the other is something that is meant to be handed over to the user. What we hand to the user doesn't need to contain transitives, but just the camel artifacts. Of course there are cases, where we want to somehow impose specific versions for some of the transitives like tooling etc, to protect the user from running into weird dependency conflicts. To satisfy this need it makes sense to provide a secondary "bom with tooling". I've seen this approach followed by projects like arquilian and it worked really nice. > Camel BOM should not include tooling depdencies > --- > > Key: CAMEL-9379 > URL: https://issues.apache.org/jira/browse/CAMEL-9379 > Project: Camel > Issue Type: Improvement > Components: build system, tooling >Reporter: Claus Ibsen >Assignee: Claus Ibsen > Fix For: 2.17.0 > > > We have some tooling dependencies in the parent bom that causes pain for > Camel end users that import the bom, and cause these depencies to influence > them. > We should move them to the tooling pom.xml so the Camel tooling dependencies > are listed there, and thus separated from the parent bom. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-9379) Camel BOM should not include tooling depdencies
[ https://issues.apache.org/jira/browse/CAMEL-9379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15033279#comment-15033279 ] Ioannis Canellos edited comment on CAMEL-9379 at 12/1/15 7:51 AM: -- In general its a good idea to separate the parent pom from the bom. The one is for internal use while the other is something that is meant to be handed over to the user. What we hand to the user doesn't need to contain transitives, but just the camel artifacts. Of course there are cases, where we want to somehow impose specific versions for some of the transitives like tooling etc, to protect the user from running into weird dependency conflicts. To satisfy this need it makes sense to provide a secondary "bom with tooling". I've seen this approach followed by projects like arquillian and it worked really nice. was (Author: iocanel): In general its a good idea to separate the parent pom from the bom. The one is for internal use while the other is something that is meant to be handed over to the user. What we hand to the user doesn't need to contain transitives, but just the camel artifacts. Of course there are cases, where we want to somehow impose specific versions for some of the transitives like tooling etc, to protect the user from running into weird dependency conflicts. To satisfy this need it makes sense to provide a secondary "bom with tooling". I've seen this approach followed by projects like arquilian and it worked really nice. > Camel BOM should not include tooling depdencies > --- > > Key: CAMEL-9379 > URL: https://issues.apache.org/jira/browse/CAMEL-9379 > Project: Camel > Issue Type: Improvement > Components: build system, tooling >Reporter: Claus Ibsen >Assignee: Claus Ibsen > Fix For: 2.17.0 > > > We have some tooling dependencies in the parent bom that causes pain for > Camel end users that import the bom, and cause these depencies to influence > them. > We should move them to the tooling pom.xml so the Camel tooling dependencies > are listed there, and thus separated from the parent bom. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-7035) camel-core-osgi doesn't properly handle different version of the same bundle
Ioannis Canellos created CAMEL-7035: --- Summary: camel-core-osgi doesn't properly handle different version of the same bundle Key: CAMEL-7035 URL: https://issues.apache.org/jira/browse/CAMEL-7035 Project: Camel Issue Type: Bug Components: osgi Affects Versions: 2.12.2 Reporter: Ioannis Canellos Assignee: Ioannis Canellos Fix For: 2.12.3 CamelContext service is registered once per bundle symbolic name. If multiple bundles share symbolic names (and use different versions) the CamelContext will only registered for the first bundle. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CAMEL-7035) camel-core-osgi doesn't properly handle different version of the same bundle
[ https://issues.apache.org/jira/browse/CAMEL-7035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ioannis Canellos resolved CAMEL-7035. - Resolution: Fixed Fix Version/s: 2.13.0 camel-core-osgi doesn't properly handle different version of the same bundle Key: CAMEL-7035 URL: https://issues.apache.org/jira/browse/CAMEL-7035 Project: Camel Issue Type: Bug Components: osgi Affects Versions: 2.12.2 Reporter: Ioannis Canellos Assignee: Ioannis Canellos Fix For: 2.12.3, 2.13.0 CamelContext service is registered once per bundle symbolic name. If multiple bundles share symbolic names (and use different versions) the CamelContext will only registered for the first bundle. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CAMEL-6517) Upgrade jclouds to 1.6.1-incubating
[ https://issues.apache.org/jira/browse/CAMEL-6517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ioannis Canellos updated CAMEL-6517: Affects Version/s: 3.0.0 2.12.0 Upgrade jclouds to 1.6.1-incubating --- Key: CAMEL-6517 URL: https://issues.apache.org/jira/browse/CAMEL-6517 Project: Camel Issue Type: Improvement Components: camel-jclouds Affects Versions: 2.12.0, 3.0.0 Reporter: Ioannis Canellos Assignee: Ioannis Canellos -- 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] [Updated] (CAMEL-6517) Upgrade jclouds to 1.6.1-incubating
[ https://issues.apache.org/jira/browse/CAMEL-6517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ioannis Canellos updated CAMEL-6517: Issue Type: Improvement (was: Bug) Upgrade jclouds to 1.6.1-incubating --- Key: CAMEL-6517 URL: https://issues.apache.org/jira/browse/CAMEL-6517 Project: Camel Issue Type: Improvement Components: camel-jclouds Reporter: Ioannis Canellos Assignee: Ioannis Canellos -- 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] [Created] (CAMEL-6517) Upgrade jclouds to 1.6.1-incubating
Ioannis Canellos created CAMEL-6517: --- Summary: Upgrade jclouds to 1.6.1-incubating Key: CAMEL-6517 URL: https://issues.apache.org/jira/browse/CAMEL-6517 Project: Camel Issue Type: Bug Components: camel-jclouds Reporter: Ioannis Canellos Assignee: Ioannis Canellos -- 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-6517) Upgrade jclouds to 1.6.1-incubating
[ https://issues.apache.org/jira/browse/CAMEL-6517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ioannis Canellos resolved CAMEL-6517. - Resolution: Fixed Fix Version/s: 2.12.0 Pushed 42125feef2e6a7134e36ca2d97301f1c93a27098 Upgrade jclouds to 1.6.1-incubating --- Key: CAMEL-6517 URL: https://issues.apache.org/jira/browse/CAMEL-6517 Project: Camel Issue Type: Improvement Components: camel-jclouds Affects Versions: 2.12.0, 3.0.0 Reporter: Ioannis Canellos Assignee: Ioannis Canellos Fix For: 2.12.0 -- 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-5539) Circuit Breaker EIP
[ https://issues.apache.org/jira/browse/CAMEL-5539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684693#comment-13684693 ] Ioannis Canellos commented on CAMEL-5539: - A must have! 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: Raul 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 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-6134) camel-jclouds - Does not work in OSGi - Seems META-INF/services loader may not work
[
https://issues.apache.org/jira/browse/CAMEL-6134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13594705#comment-13594705
]
Ioannis Canellos commented on CAMEL-6134:
-
The service loader doesn't work inside OSGi.
So I've added some bits to jclouds itself so that it registers its own stuff
founds under META-INF/service to the Service Registry. I'll have a look and see
why its borked.
camel-jclouds - Does not work in OSGi - Seems META-INF/services loader may
not work
---
Key: CAMEL-6134
URL: https://issues.apache.org/jira/browse/CAMEL-6134
Project: Camel
Issue Type: Bug
Components: camel-jclouds, karaf
Affects Versions: 2.11.0
Reporter: Claus Ibsen
Assignee: Ioannis Canellos
The BlobStoreBlueprintRouteTest test fails in tests/camel-itest-osgi, when
running
{code}
mvn clean test -Dtest=BlobStoreBlueprintRouteTest
{code}
It cannot find the transient provider, which seems to be located in
jclouds-blobstore JAR in the META/INF/services directory.
org.jclouds.blobstore.TransientApiMetadata
Migrating to the new builder API I get this error
{code}
java.util.NoSuchElementException: key [transient] not in the list of
providers or apis: {}
at org.jclouds.ContextBuilder.newBuilder(ContextBuilder.java:172)
at
org.apache.camel.itest.osgi.jclouds.BlobStoreBlueprintRouteTest.doPreSetup(BlobStoreBlueprintRouteTest.java:52)
{code}
Not sure what it takes to get service loader to work in OSGi / Karaf.
--
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] [Created] (CAMEL-6075) Upgrade to jclouds 1.5.7
Ioannis Canellos created CAMEL-6075: --- Summary: Upgrade to jclouds 1.5.7 Key: CAMEL-6075 URL: https://issues.apache.org/jira/browse/CAMEL-6075 Project: Camel Issue Type: Improvement Reporter: Ioannis Canellos Assignee: Ioannis Canellos -- 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-6075) Upgrade to jclouds 1.5.7
[ https://issues.apache.org/jira/browse/CAMEL-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ioannis Canellos resolved CAMEL-6075. - Resolution: Fixed Fix Version/s: 2.11.0 Upgrade to jclouds 1.5.7 Key: CAMEL-6075 URL: https://issues.apache.org/jira/browse/CAMEL-6075 Project: Camel Issue Type: Improvement Reporter: Ioannis Canellos Assignee: Ioannis Canellos Fix For: 2.11.0 -- 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] [Created] (CAMEL-6055) Add export service information to camel bundles
Ioannis Canellos created CAMEL-6055: --- Summary: Add export service information to camel bundles Key: CAMEL-6055 URL: https://issues.apache.org/jira/browse/CAMEL-6055 Project: Camel Issue Type: Improvement Reporter: Ioannis Canellos Assignee: Ioannis Canellos -- 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] [Created] (CAMEL-5756) OSGi resolvers for component, dataformat and language should check if service object is assignable before casting
Ioannis Canellos created CAMEL-5756: --- Summary: OSGi resolvers for component, dataformat and language should check if service object is assignable before casting Key: CAMEL-5756 URL: https://issues.apache.org/jira/browse/CAMEL-5756 Project: Camel Issue Type: Bug Components: osgi Reporter: Ioannis Canellos Assignee: Ioannis Canellos Fix For: 2.9.5, 2.10.3, 2.11.0 Currently, the OSGi resolvers, get all services for the target component, dataformat and language and then cast the first service object to the type of choice. This can be problematic if for any reason multiple version of a component is installed inside the container. -- 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-5701) Update to jclouds 1.5.2 and leverage context names.
[ https://issues.apache.org/jira/browse/CAMEL-5701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ioannis Canellos resolved CAMEL-5701. - Resolution: Fixed Update to jclouds 1.5.2 and leverage context names. --- Key: CAMEL-5701 URL: https://issues.apache.org/jira/browse/CAMEL-5701 Project: Camel Issue Type: Improvement Components: camel-jclouds Reporter: Ioannis Canellos Assignee: Ioannis Canellos Fix For: 2.9.5, 2.10.3 -- 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] [Created] (CAMEL-5701) Update to jclouds 1.5.2 and leverage context names.
Ioannis Canellos created CAMEL-5701: --- Summary: Update to jclouds 1.5.2 and leverage context names. Key: CAMEL-5701 URL: https://issues.apache.org/jira/browse/CAMEL-5701 Project: Camel Issue Type: Improvement Components: camel-jclouds Reporter: Ioannis Canellos Assignee: Ioannis Canellos Fix For: 2.9.5, 2.10.2 -- 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-5653) camel-hbase producer should be able to perform get with just the id as a header
[ https://issues.apache.org/jira/browse/CAMEL-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ioannis Canellos resolved CAMEL-5653. - Resolution: Fixed Committed to trunk and 2.10.x branch. camel-hbase producer should be able to perform get with just the id as a header --- Key: CAMEL-5653 URL: https://issues.apache.org/jira/browse/CAMEL-5653 Project: Camel Issue Type: Bug Components: camel-hbase Affects Versions: 2.10.0, 2.10.1 Reporter: Ioannis Canellos Assignee: Ioannis Canellos Fix For: 2.11.0, 2.10.2 In many cases the user would specify the families/columns of interest as part of the uri and then just specify the row id as part of the headers. The way it currently works, it requires at least one family/column along with the row id as part of the headers. -- 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-5652) camel-hbase unit tests could use a model that is more meaningful and comprehensive
[ https://issues.apache.org/jira/browse/CAMEL-5652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ioannis Canellos resolved CAMEL-5652. - Resolution: Fixed camel-hbase unit tests could use a model that is more meaningful and comprehensive -- Key: CAMEL-5652 URL: https://issues.apache.org/jira/browse/CAMEL-5652 Project: Camel Issue Type: Improvement Components: camel-hbase Reporter: Ioannis Canellos Assignee: Ioannis Canellos Priority: Minor Currently, the unit tests provided from the camel-hbase model, use dummy family and column names, that have no meaning at all. This makes them hard to read and understand. It would make some sense to give some additional love to the unit test, so that people can better understand how they work when they read them. -- 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] [Created] (CAMEL-5650) Upgrade to jclouds 1.5.0
Ioannis Canellos created CAMEL-5650: --- Summary: Upgrade to jclouds 1.5.0 Key: CAMEL-5650 URL: https://issues.apache.org/jira/browse/CAMEL-5650 Project: Camel Issue Type: Improvement Reporter: Ioannis Canellos We can upgrade to jclouds and jclouds karaf 1.5.0 and replace some deprecated code references. Also we should make sure that camel-jclouds can also work with jclouds apis and not only jclouds providers. -- 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] [Created] (CAMEL-5652) camel-hbase unit tests could use a model that is more meaningful and comprehensive
Ioannis Canellos created CAMEL-5652: --- Summary: camel-hbase unit tests could use a model that is more meaningful and comprehensive Key: CAMEL-5652 URL: https://issues.apache.org/jira/browse/CAMEL-5652 Project: Camel Issue Type: Improvement Reporter: Ioannis Canellos Assignee: Ioannis Canellos Priority: Minor Currently, the unit tests provided from the camel-hbase model, use dummy family and column names, that have no meaning at all. This makes them hard to read and understand. It would make some sense to give some additional love to the unit test, so that people can better understand how they work when they read them. -- 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] [Updated] (CAMEL-5652) camel-hbase unit tests could use a model that is more meaningful and comprehensive
[ https://issues.apache.org/jira/browse/CAMEL-5652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ioannis Canellos updated CAMEL-5652: Component/s: camel-hbase camel-hbase unit tests could use a model that is more meaningful and comprehensive -- Key: CAMEL-5652 URL: https://issues.apache.org/jira/browse/CAMEL-5652 Project: Camel Issue Type: Improvement Components: camel-hbase Reporter: Ioannis Canellos Assignee: Ioannis Canellos Priority: Minor Currently, the unit tests provided from the camel-hbase model, use dummy family and column names, that have no meaning at all. This makes them hard to read and understand. It would make some sense to give some additional love to the unit test, so that people can better understand how they work when they read them. -- 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] [Created] (CAMEL-5653) camel-hbase producer should be able to perform get with just the id as a header
Ioannis Canellos created CAMEL-5653: --- Summary: camel-hbase producer should be able to perform get with just the id as a header Key: CAMEL-5653 URL: https://issues.apache.org/jira/browse/CAMEL-5653 Project: Camel Issue Type: Bug Components: camel-hbase Affects Versions: 2.10.1, 2.10.0 Reporter: Ioannis Canellos Assignee: Ioannis Canellos Fix For: 2.11.0, 2.10.2 In many cases the user would specify the families/columns of interest as part of the uri and then just specify the row id as part of the headers. The way it currently works, it requires at least one family/column along with the row id as part of the headers. -- 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-5506) HBase component does not extract that table name in all cases and HBase runtime version issues.
[ https://issues.apache.org/jira/browse/CAMEL-5506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13435160#comment-13435160 ] Ioannis Canellos commented on CAMEL-5506: - Regarding the provided scope I agree, as it seems that unless there is an exact version match between the client and the server, then there will be problems. Regarding the getHost() thing, I am not sure I understand what exactly is the problem. AFAIK it doesn't have issues working with simple names too. In fact in the unit tests simple names have been used and they do work fine. Maybe I misunderstood the problem? HBase component does not extract that table name in all cases and HBase runtime version issues. --- Key: CAMEL-5506 URL: https://issues.apache.org/jira/browse/CAMEL-5506 Project: Camel Issue Type: Bug Affects Versions: 2.10.0 Environment: Any Reporter: Claudio Corsi Assignee: Claus Ibsen Labels: camel-hbase Fix For: 2.10.1, 2.11.0 Attachments: hbase.diffs The current hbase component uses the URI getHost method to retrieve the table name but this method returns null if the host name does not conform to the requirements of this method. For instance, it should include a '.' in the name, or is a ipv4 or ipv6 valid address string. If the table name is a simple name then the getHost method will return null instead of the name of the table. This will in turn cause a NPE exception. The other issue is that if you are using 0.92.x or greater with the current implementation of the camel-hbase component. An IllegalArgumentException is generated because of an incompatible host:port pair. This is caused by the fact that the current hbase integration uses 0.90.5 and this will conflict with those versions. I have a patch that solves both issues but in the second case. It will require that the user define the specific hbase client version that they need to use. btw, the camel-hbase component is not available as an option for the Component/s drop down list. -- 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] [Resolved] (CAMEL-4743) Create a camel component for Hbase
[ https://issues.apache.org/jira/browse/CAMEL-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ioannis Canellos resolved CAMEL-4743. - Resolution: Fixed Fix Version/s: 2.10.0 Create a camel component for Hbase -- Key: CAMEL-4743 URL: https://issues.apache.org/jira/browse/CAMEL-4743 Project: Camel Issue Type: New Feature Reporter: Ioannis Canellos Assignee: Ioannis Canellos Fix For: 2.10.0 Attachments: CAMEL-4743-checkstyle.patch, CAMEL-4743-patch.txt -- 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-5314) camel jclouds blobstore streaming support
[ https://issues.apache.org/jira/browse/CAMEL-5314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ioannis Canellos reassigned CAMEL-5314: --- Assignee: Ioannis Canellos camel jclouds blobstore streaming support - Key: CAMEL-5314 URL: https://issues.apache.org/jira/browse/CAMEL-5314 Project: Camel Issue Type: Improvement Components: camel-jclouds Affects Versions: 2.9.0, 2.9.1, 2.9.2 Reporter: Ioannis Canellos Assignee: Ioannis Canellos When reading and writing from blob stores the camel jclouds component assumes that that the payload is always a java object. Moreover, it fully reads the object and places it inside the message body. We should provide streaming support, since there is no limit in the size of the payload. We should also make sure that it can handle any type of data and not just java objects. -- 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] [Created] (CAMEL-5314) camel jclouds blobstore streaming support
Ioannis Canellos created CAMEL-5314: --- Summary: camel jclouds blobstore streaming support Key: CAMEL-5314 URL: https://issues.apache.org/jira/browse/CAMEL-5314 Project: Camel Issue Type: Improvement Components: camel-jclouds Affects Versions: 2.9.2, 2.9.1, 2.9.0 Reporter: Ioannis Canellos When reading and writing from blob stores the camel jclouds component assumes that that the payload is always a java object. Moreover, it fully reads the object and places it inside the message body. We should provide streaming support, since there is no limit in the size of the payload. We should also make sure that it can handle any type of data and not just java objects. -- 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
