Had a quick look at the connector. It seems straightforward enough, although I already found three bugs by inspection: - Wrong model, should be MODEL_ADD_CHANGE_REMOVE (because neither CHANGE nor REMOVE is in fact possible) - Doesn't initialize this.properties properly in connect(); this can be null after disconnect() called - processDocuments() calls finalizeConnection() inappropriately, so that the connection is discarded and must be reinitialized on every set of documents - getMaxDocuments() returns 50, which seems questionable too... 1 is probably fine, if it wasn't for the finalizeConnection().
In short it appears that the coder did not fully understand the connection object lifecycle, but other than that it is a good starting point. Karl On Tue, Oct 22, 2013 at 2:09 PM, Karl Wright <[email protected]> wrote: > Hi Mark, > No reason other than the one you state. This connector was worked on as > part of the Google Summer of Code 2013, but my understanding is that it was > not completed and the code was never put in Apache svn. It's in git > somewhere. See https://issues.apache.org/jira/browse/CONNECTORS-553 . > > FWIW, I'd love to have someone pick up this project and bring it to > completion. I have very limited time though at the moment, so whoever does > it will have to be willing to put the time in that is necessary to finish > the job properly. > > If you want to take this on, please let me know and I will try to set up a > branch for this. Then you can submit patches against the branch and I'll > commit them as needed. > > Thanks! > Karl > > > > > On Tue, Oct 22, 2013 at 2:00 PM, Mark Libucha <[email protected]> wrote: > >> A MS Exchange repository connector seems like a black hole in the MCF >> connector suite. >> >> Are there reasons it's not there outside of "nobody has written one"? >> >> Thanks, >> >> Mark >> >> >
