airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raminderjeet Singh (JIRA)" <>
Subject [jira] [Created] (AIRAVATA-659) Airavata Client Exception handling
Date Mon, 26 Nov 2012 16:56:57 GMT
Raminderjeet Singh created AIRAVATA-659:

             Summary: Airavata Client Exception handling
                 Key: AIRAVATA-659
             Project: Airavata
          Issue Type: Bug
          Components: Airavata Client
    Affects Versions: 0.5
            Reporter: Raminderjeet Singh
            Priority: Critical

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(
			OMElement omElement = AXIOMUtil.stringToOM(XMLUtil
			worflowoutput = stub.launchWorkflow(workflow, topic, null);
			runPreWorkflowExecutionTasks(worflowoutput, user, metadata,

		} 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:

View raw message