Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 73FD4E985 for ; Mon, 26 Nov 2012 19:12:58 +0000 (UTC) Received: (qmail 35438 invoked by uid 500); 26 Nov 2012 19:12:58 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 35406 invoked by uid 500); 26 Nov 2012 19:12:58 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 35397 invoked by uid 99); 26 Nov 2012 19:12:58 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Nov 2012 19:12:58 +0000 Date: Mon, 26 Nov 2012 19:12:58 +0000 (UTC) From: "Saminda Wijeratne (JIRA)" To: dev@airavata.apache.org Message-ID: <658843606.24069.1353957178358.JavaMail.jiratomcat@arcas> In-Reply-To: <2013934817.23419.1353949018190.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (AIRAVATA-659) Airavata Client Exception handling MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AIRAVATA-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503997#comment-13503997 ] Saminda Wijeratne commented on AIRAVATA-659: -------------------------------------------- If you have an immediate urgent requirement for this I can adjust my priority list to do this sooner... Orelse I can focus on this end of this week. > 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 > > 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