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 2012/11/26 17:56:57 UTC
[jira] [Created] (AIRAVATA-659) Airavata Client Exception handling
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
[jira] [Commented] (AIRAVATA-659) Airavata Client Exception
handling
Posted by "Saminda Wijeratne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504014#comment-13504014 ]
Saminda Wijeratne commented on AIRAVATA-659:
--------------------------------------------
I'll try to get it completed within tomorrow then... With the monitoring exception you mentioned in the thread, it seems we need to drill-down beyond AiravataClient on handling exceptions we hadn't anticipated earlier.
> 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
[jira] [Assigned] (AIRAVATA-659) Airavata Client Exception handling
Posted by "Raminderjeet Singh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raminderjeet Singh reassigned AIRAVATA-659:
-------------------------------------------
Assignee: Raminderjeet Singh
> 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
[jira] [Commented] (AIRAVATA-659) Airavata Client Exception
handling
Posted by "Raminderjeet Singh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503999#comment-13503999 ]
Raminderjeet Singh commented on AIRAVATA-659:
---------------------------------------------
i am working on ODI Api client testing which we have a deadline of Wednesday 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
[jira] [Commented] (AIRAVATA-659) Airavata Client Exception
handling
Posted by "Saminda Wijeratne (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (AIRAVATA-659) Airavata Client Exception
handling
Posted by "Saminda Wijeratne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503924#comment-13503924 ]
Saminda Wijeratne commented on AIRAVATA-659:
--------------------------------------------
The class AiravataClient is infact now legacy code... We need to completely rewrite this class to suit the current 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
>
> 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
[jira] [Commented] (AIRAVATA-659) Airavata Client Exception
handling
Posted by "Raminderjeet Singh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503950#comment-13503950 ]
Raminderjeet Singh commented on AIRAVATA-659:
---------------------------------------------
Then i will leave the class as it is and you can implement the required exception handling in the new class. Any ETA for the rewrite?
> 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