[AIRAVATA-659] Airavata Client Exception handling

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.5
• Fix Version/s: 0.9
• Component/s: Airavata Client
• Assignee: Raminderjeet Singh
• Reporter: Raminderjeet Singh
• Created: 26/Nov/12 16:55
• Updated: 17/Sep/13 20:34
• Resolved: 21/Aug/13 17:35

Description

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