Hi , I have gone through the tutorials Service invocation plugin <http://dev.mygrid.org.uk/wiki/display/developer/Tutorial+-+Service+invocation+plugin> and Service discovery plugin <http://dev.mygrid.org.uk/wiki/display/developer/Tutorial+-+Service+discovery+plugin>. So in order to bring CWL workflows to the Taverna i have to implement Service discovery plugin <http://dev.mygrid.org.uk/wiki/display/developer/Tutorial+-+Service+discovery+plugin> for CWL right ?.
Please tell me following points are correct or not if not say where am i wrong , 1. SCULF2 workflows are saved as workflow bundle document . 2. Service discovery plugin <http://dev.mygrid.org.uk/wiki/display/developer/Tutorial+-+Service+discovery+plugin> Service Description is java bean and it's build using corresponding workflow bundle document . 3. Activity has the logic of workflow .For example let's say service is addtiion of two numbers . Then two numbers are input and the addition is inside the Activity class . 4.Activity class is also configured (build) using corresponding workflow bundle document . *5. when designing a CWL * Service discovery plugin <http://dev.mygrid.org.uk/wiki/display/developer/Tutorial+-+Service+discovery+plugin> i Have to implement dummy Activity class for CWL . It should have logic to execute cwl-runner with corresponding tool and inputs and get the output . regards. On Mon, Mar 14, 2016 at 11:47 PM, Stian Soiland-Reyes (JIRA) < [email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/TAVERNA-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15193811#comment-15193811 > ] > > Stian Soiland-Reyes commented on TAVERNA-880: > --------------------------------------------- > > Hi, potential Google Summer of Code (GSOC) students! > > In a tiny hour the GSOC student application period opens: > > > > https://developers.google.com/open-source/gsoc/timeline > > 14 March 19:00 UTC Student application period opens. > > 25 March 19:00 UTC Student application deadline. > > http://write.flossmanuals.net/gsocstudentguide/ has a good description > of the process. > > > I've tried to summarize who is interested in what here: > > https://cwiki.apache.org/confluence/display/TAVERNADEV/2016-03+GSOC+2016 > > My apologies for any mistakes or if I forgot someone.. it was a bit > hard to track across all the emails! Let me know what to fix. > > > > If you are preparing a GSOC proposal for Apache Taverna, e.g. inspired > by our ideas at: > > https://s.apache.org/taverna-gsoc-2016 > > or your own ideas (e.g further developing Taverna Mobile), then > now is a good time to start working on your project proposal. > > > I suggest writing a Google Docs page, and sharing it on dev@taverna > (which hopefully you have signed up to - see > http://taverna.incubator.apache.org/contact) > > .. or leave a comment on this Jira Issue so we can discuss it and help you > get a good proposal! > > See http://write.flossmanuals.net/gsocstudentguide/writing-a-proposal/ > for suggestions for your proposal, and a template here: > > http://community.staging.apache.org/gsoc#application-template > > > Browse+use CWL tool descriptions > > -------------------------------- > > > > Key: TAVERNA-880 > > URL: https://issues.apache.org/jira/browse/TAVERNA-880 > > Project: Apache Taverna > > Issue Type: New Feature > > Components: Taverna Workbench Common Activities > > Reporter: Stian Soiland-Reyes > > Labels: cwl, gsoc2016 > > > > CWL Tool descriptions may be used by the ELIXIR Tool registry, using > EDAM ontology. > > The Taverna Workbench could parse such descriptions to add Tool > Activities to workflows. > > The Available Services panel is pluggable - see > > > https://github.com/apache/incubator-taverna-workbench/blob/master/taverna-activity-palette-api/src/main/java/org/apache/taverna/servicedescriptions/ServiceDescriptionProvider.java > > and > > > https://github.com/apache/incubator-taverna-workbench/blob/master/taverna-activity-palette-api/src/main/java/org/apache/taverna/servicedescriptions/ServiceDescription.java > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
