You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Raminderjeet Singh (JIRA)" <ji...@apache.org> on 2013/08/21 19:35:52 UTC
[jira] [Resolved] (AIRAVATA-659) Airavata Client Exception handling
[ https://issues.apache.org/jira/browse/AIRAVATA-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raminderjeet Singh resolved AIRAVATA-659.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 0.9
Resolved in latest API.
> Airavata Client Exception handling
> ----------------------------------
>
> Key: AIRAVATA-659
> URL: https://issues.apache.org/jira/browse/AIRAVATA-659
> Project: Airavata
> Issue Type: Bug
> Components: Airavata Client
> Affects Versions: 0.5
> Reporter: Raminderjeet Singh
> Assignee: Raminderjeet Singh
> Priority: Critical
> Fix For: 0.9
>
>
> Airavata client have runWorkflow method where exceptions are not handled property. similar patterns are followed in other methods of airavata client.
> public String runWorkflow(String topic, String user, String metadata,
> String workflowInstanceName, WorkflowContextHeaderBuilder builder) throws AiravataConfigurationException {
> String worflowoutput = null;
> try {
> WorkflowInterpretorStub stub = new WorkflowInterpretorStub(
> getClientConfiguration().getXbayaServiceURL().toString());
> OMElement omElement = AXIOMUtil.stringToOM(XMLUtil
> .xmlElementToString(builder.getXml()));
> stub._getServiceClient().addHeader(omElement);
> worflowoutput = stub.launchWorkflow(workflow, topic, null);
> runPreWorkflowExecutionTasks(worflowoutput, user, metadata,
> workflowInstanceName);
> } catch (AxisFault e) {
> } catch (RemoteException e) {
> // log.fine(e.getMessage(), e);
> } catch (RegistryException e) {
> // log.fine(e.getMessage(), e);
> } catch (XMLStreamException e) {
> e.printStackTrace(); // To change body of catch statement use File |
> // Settings | File Templates.
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira