Good catch. If you have not done so already can you please create a jira issue for this.
We love contributions Thanks Pontus On Thu, 26 Jan 2017 at 19:12 Tim Dudgeon <tdudgeon...@gmail.com> wrote: > What I've found out so far is that the box library used by Camel is an old > project. > > The one currently recommended by box.com is this this GitHub project > https://github.com/box/box-java-sdk which has maven coordinates of > com.box:box-java-sdk:2.1.1 > (https://search.maven.org/#search%7Cga%7C1%7Ca%3A%22box-java-sdk%22) and > plenty of examples which I got running fine. > > The one used in Camel have Maven coords of net.box:boxjavalibv2:3.2.1 ( > https://search.maven.org/#search%7Cga%7C1%7Ca%3A%22boxjavalibv2%22) and > has > not been updated since 2014. I can't find source code or much info for this > so have not yet been able to test whether it still works against the > current > box.com site. > > I suspect this is cause of the problem, and, if so, wonder if any of the > Camel box component functions work correctly today. > > Tim > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Using-Box-component-tp5792922p5793091.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
