Raminderjeet Singh created AIRAVATA-659:
-------------------------------------------
Summary: 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
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(
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
