You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Antonio David Pérez Morales (JIRA)" <ji...@apache.org> on 2014/08/18 11:17:18 UTC

[jira] [Resolved] (STANBOL-1376) Enhance Web Interface for Managing Camel Routes in Stanbol

     [ https://issues.apache.org/jira/browse/STANBOL-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antonio David Pérez Morales resolved STANBOL-1376.
--------------------------------------------------

    Resolution: Fixed

- Created web part for routes
- Default endpoint is http://stanbol.domain:PORT/workflow
- To call a specific route using some text, the endpoint is http://stanbol.domain:PORT/workflow/{workflowRoute} where worflowRoute is the ID of the registered route to be used. A POST request must be done to trigger the route
- The workflow web part only makes sense to call direct endpoints (triggered synchronously)
- If an activemq or another queue component is being used in the from part of a route, that route will be triggered asynchronously when the queue has some information (receives an event and generates an event)
- Routes can be uploaded using the web interface or sending a PUT request to the workflow endpoint with the file ("file" parameter) containing the route. The route is put in the directory used by the RouteInstaller component, so the route is not installed directly but in the next iteration of RouteInstaller monitor.

> Enhance Web Interface for Managing Camel Routes in Stanbol
> ----------------------------------------------------------
>
>                 Key: STANBOL-1376
>                 URL: https://issues.apache.org/jira/browse/STANBOL-1376
>             Project: Stanbol
>          Issue Type: Sub-task
>          Components: Enhancer
>            Reporter: Rafa Haro
>            Assignee: Antonio David Pérez Morales
>             Fix For: 1.0.0
>
>
> Enhance web part, using the new workflow API to call routes (only routes which can be triggered directly like the ones using direct endpoint in from, because there are other routes triggered asynchronously, for example receiving a message in a queue) and also allowing uploading routes from the web interface (and API REST)



--
This message was sent by Atlassian JIRA
(v6.2#6252)