Hi Luis, it seems that here we have to work on the Content Migration extension for also the File System Repository Connector.
This is exactly the same problem that I had during the development of the CMIS Output Connector for implementing the removeDocument method. I think that we should plan an improvement activity for this connector. Cheers, PJ 2017-09-27 11:59 GMT+02:00 Luis Cabaceira <[email protected]>: > Hi all, > > I'm writing the BFSI output connector and i would like it to support all > existing input connectors. I've tested it with cmis input where i can > obtain all the information i need via the getFields method of the document > object. > > Now if i use the filesystem input connector, all i have in getFields is the > URI of the document. I need to access the Job data to know the input > connector repository root paths and i'm not finding a way to get it. > > Is there a way, in the output connector to access the Job attributes ? > > Cheers, > Luis Cabaceira > -- Piergiorgio Lucidi Open Source Evangelist and Enterprise Information Management Specialist Mentor / PMC Member / Committer @ Apache Software Foundation Community Star / Wiki Gardener / Global Forum Moderator @ Alfresco Author and Technical Reviewer @ Packt Publishing Technical Advisory Group Member @ Microsoft Top Community Contributor @ Crafter Project Leader / Committer @ JBoss http://www.open4dev.com
