Up to now we've developed using the client API 2.6.38.
I've just now installed the standalone API 2.6.43 to do some tests.
The first thing I came across when starting one of our strategies is the following exception.
call: history.getBar(EUR/USD, MONTHLY, ASK, 1);
on current tick: Mon 2011.01.10 00:00:02.139
throws:
Quote:
2011-08-03 14:38:32.126 ERROR LoadDataAction - We can work only with candle concrete numbers or with data sequence times!
java.lang.IllegalArgumentException: We can work only with candle concrete numbers or with data sequence times!
at com.dukascopy.charts.data.datacache.customperiod.candle.CustomPeriodCandleLiveFeedListener.finishLoading(CustomPeriodCandleLiveFeedListener.java:264)
at com.dukascopy.charts.data.datacache.customperiod.candle.CustomPeriodCandleLoadingProgressListener.loadingFinished(CustomPeriodCandleLoadingProgressListener.java:29)
at com.dukascopy.charts.data.datacache.LoadProgressingAction$LoadingProgressWrapper.loadingFinished(LoadProgressingAction.java:36)
at com.dukascopy.charts.data.datacache.LoadDataAction.run(LoadDataAction.java:272)
at com.dukascopy.charts.data.datacache.LoadCustomPeriodDataAction.run(LoadCustomPeriodDataAction.java:96)
at com.dukascopy.charts.data.datacache.LoadDataAction.run(LoadDataAction.java:114)
at com.dukascopy.charts.data.datacache.FeedDataProvider.loadCandlesDataSynched(FeedDataProvider.java:696)
at com.dukascopy.api.impl.History.getBarsSecured(History.java:473)
at com.dukascopy.api.impl.History$10.run(History.java:445)
at com.dukascopy.api.impl.History$10.run(History.java:443)
at java.security.AccessController.doPrivileged(Native Method)
at com.dukascopy.api.impl.History.getBars(History.java:443)
at com.dukascopy.dds2.greed.agent.strategy.tester.TesterHistory.fillCacheBuffer(TesterHistory.java:141)
at com.dukascopy.dds2.greed.agent.strategy.tester.TesterHistory.getBars(TesterHistory.java:703)
at com.dukascopy.api.impl.History.getHistoryBarBlocking(History.java:181)
at com.dukascopy.api.impl.History.getBar(History.java:151)
...
Are there any known workarounds or tips on how to solve this issue?
Any other issues with the standalone API we should be aware of? And what is the development status of the API - is this a stable release or should we wait for an update before performing further tests?
Thanks for any feedback!
Best,
RR.
