movilizer/movilizer-spring-connector

movilizer-spring-connector's Issues

Unit test failures

Hi Pavel, as discussed, moving the tickets here from Movilizer JIRA.
We are on master branch of the Spring connector and JUnit tests fail. When executing "gradle test" goal, we get 25 failures. We have noticed that some of the tests can be fixed using the System.setProperty("javax.xml.bind.JAXBContext", "com.sun.xml.internal.bind.v2.ContextFactory") trick, however some cannot, including BindingTest, DataContainerMapperTest, ParticipantProcessorTest, etc..
Questions:

• are we on the right branch? are we supposed to use the "master" branch?
• what are the settings (JVM version, Gradle version, etc.) recommended to build the Spring connector?
• are Unit tests maintained at all for the Spring connector or they are an abandoned effort?

MD update network failure handling

Hi Pavel,

I'm opening this issue on behalf of ENGIE. For the eStar project we are considering usage of the Spring connector. We consider CSV file based interface to one of our backends. Our question concerns the scenario, when due to a network issue the push call to the cloud fails. In the MasterdataProcessor.process method, line 39, we see that the updates are removed from the queue: toMovilizerQueueService.removeMasterdata(masterdataUpdates).
This happens before the actual request is send to the cloud (PollingJob.performSyncToCloud, line 71). How do we "replay" the master data updates, which failed due to a network/proxy/DNS/etc. issue? What is the strategy for this?

Thank you,
Peter