[
https://issues.apache.org/jira/browse/CAMEL-9047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15344752#comment-15344752
]
Dhiraj Bokde commented on CAMEL-9047:
-------------------------------------
When there is a change in the underlying API the upgrade/migration flow for API
Component framework is as follows:
* Minor version change with bug fixes, mostly addition of new API
classes/methods, update the existing component and rebuild. The generated
component and it's endpoint URIs will remain backward compatible
* Major version change, new classes/methods, write a new component, which will
have functionally similar endpoints, but distinct URI prefixes and options.
Note that most of the component code can be copied from the previous version,
only changing how the API proxies are instantiated.
Since the API has changed dramatically with box-java-sdk (including parameter
and return classes like BoxFolder), we should create a new component called
camel-box2, since it's based on 2.1.1. When Box.com comes out with a a major
change in SDK version 3, we can create camel-box3, or if there is a major API
change with version 2.2, camel-box2_2 and so on.
> Replace deprecated boxjavalibv2 with box-java-sdk
> -------------------------------------------------
>
> Key: CAMEL-9047
> URL: https://issues.apache.org/jira/browse/CAMEL-9047
> Project: Camel
> Issue Type: Improvement
> Components: camel-box
> Affects Versions: 2.15.2
> Reporter: Tomas Rohovsky
> Assignee: Dhiraj Bokde
>
> camel-box component is based on boxjavalibv2 \[1\], which was made deprecated
> in favour of box-java-sdk \[2\] \[3\]. "The new SDK is not backwards
> compatible and any code using this SDK will need to be migrated in order to
> take advantage of any new features and bug fixes."
> \[1\] https://github.com/box/deprecated-box-java-sdk-v2
> \[2\] http://opensource.box.com/box-java-sdk/
> \[3\] https://www.box.com/blog/the-new-box-java-sdk/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
