You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Saminda Wijeratne (JIRA)" <ji...@apache.org> on 2012/08/29 20:01:09 UTC
[jira] [Resolved] (AIRAVATA-538) getWorkflowExecutionByUser(...)
method implementation is not correct
[ https://issues.apache.org/jira/browse/AIRAVATA-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Saminda Wijeratne resolved AIRAVATA-538.
----------------------------------------
Resolution: Fixed
Fix Version/s: 0.5-INCUBATING
Author: lahiru
Date: Tue Aug 14 13:35:35 2012
New Revision: 1372876
> getWorkflowExecutionByUser(...) method implementation is not correct
> --------------------------------------------------------------------
>
> Key: AIRAVATA-538
> URL: https://issues.apache.org/jira/browse/AIRAVATA-538
> Project: Airavata
> Issue Type: Bug
> Components: Registry API
> Reporter: Bhathiya Jayasekara
> Assignee: Bhathiya Jayasekara
> Fix For: 0.5-INCUBATING
>
> Attachments: getWorkflowExecutionByUser.patch
>
>
> Following method in AiravataJCRRegistry is not correct. It calls itself recursively forever.
> public List<WorkflowExecution> getWorkflowExecutionByUser(String user,
> int pageSize, int pageNo) throws RegistryException {
> if (getProvenanceRegistry()!=null){
> return getProvenanceRegistry().getWorkflowExecutionByUser(user, pageSize, pageNo);
> }
> return getWorkflowExecutionByUser(user,pageSize*pageNo,pageSize*(pageNo+1));
> }
--
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