This relates to the original thread heading - as it has only been partially covered:
AFAICT teamwork:scriptBasedFileImport relies on an uploaded file via a multipart form encoding it has a bunch of moving parts as an importer - a plugin, UI page, a service and finally the tag that does the work - all related by code inside prototypes. The code for this tag doesnt seem visible - does that mean there is an import needed - or is it picking up a java function by reflection? I'd like to add the option of saving the input file and referencing it. If it has a URI location I would rather save this and make the importer fetch it. Maybe the EDG Corpora is an appropriate intermediatary data store for the raw data - it has load from URI importers. So I guess I need two pieces of info I cannot find in docs (and maybe because these mode are not supported): 1) how best to save a file via the Corpus importers programattically - i'd rather not have to chain a second multi-part-form call to the service inside my custom importer 2) how to inject some pre- and post-processing into existing EDG importers (at the moment, it seems like the only option is to clone and hack each of the moving parts and then attach this via the ProjectType? ) -- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
