airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lahiru Gunathilake (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AIRAVATA-661) Optimize AiravataJPARegistry.getServiceDescriptor
Date Tue, 01 Apr 2014 19:26:20 GMT

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

Lahiru Gunathilake resolved AIRAVATA-661.
-----------------------------------------

    Resolution: Invalid

This is going to be retired. So resolving.

> 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)

Mime
View raw message