On 22/07/2014 11:13, Stian Soiland-Reyes wrote:
I believe you would have to upload the JAR file per run to the lib/ sub-folder of the working directory, e.g. to:/runs/{id}/wd/lib/ See http://dev.mygrid.org.uk/wiki/display/tav250/REST+API#RESTAPI-Resource:/runs/{id}/wdResource:/runs/{id}/wd/{path%E2%80%A6}
This is what I recommend.
Alternatively you would have to modify the bundled Taverna installation. It would not work to add it to webapps/tavernaserver/WEB-INF/lib as that is only used by the Taverna Server web application - the workflow is executed in a standalone process using the bundled Taverna Command line.
I don't recommend modifying the server's global lib directory. I've been doing it that way for a project which used a *very* large external library, and it was a complete mess that required a very complex piece of hacking to make work well. (I can point to the code required if you want — it's on github — but it's genuinely *awful*.) Modifying the per-run lib directory (which you'll need to do per run) should be straight forward by comparison; it's exposed precisely to allow such things. Donal.
<<attachment: donal_k_fellows.vcf>>
------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds
_______________________________________________ taverna-users mailing list [email protected] [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/about/contact-us/
