You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Lahiru Gunathilake (JIRA)" <ji...@apache.org> on 2014/04/01 21:26:21 UTC

[jira] [Closed] (AIRAVATA-661) Optimize AiravataJPARegistry.getServiceDescriptor

     [ https://issues.apache.org/jira/browse/AIRAVATA-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lahiru Gunathilake closed AIRAVATA-661.
---------------------------------------


> Optimize AiravataJPARegistry.getServiceDescriptor
> -------------------------------------------------
>
>                 Key: AIRAVATA-661
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-661
>             Project: Airavata
>          Issue Type: Improvement
>          Components: Registry API
>            Reporter: Raminderjeet Singh
>
> Rightnow we have 2 method call in getServiceDescriptor(String serviceName) method to 1st check of service object exists and then get the service object using getServiceDescriptorResource . 1st method itself have the service object and can be returned to the client. This is true for other get operations also as isExists method is called from multiple places. 
> GatewayResource gateway = jpa.getGateway();
> if (!gateway.isServiceDescriptorExists(serviceName)){
>         	return null;
>  }
>  ServiceDescriptorResource serviceDescriptorResource = gateway.getServiceDescriptorResource(serviceName);



--
This message was sent by Atlassian JIRA
(v6.2#6252)