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/03/28 16:00:29 UTC
[jira] [Commented] (AIRAVATA-1026) GFacAPI logic to load
input/output handlers is not working property
[ https://issues.apache.org/jira/browse/AIRAVATA-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13950825#comment-13950825 ]
Lahiru Gunathilake commented on AIRAVATA-1026:
----------------------------------------------
This is the logic in gFAc, if you have an application specific configuration we give higher preference for application specific handlers. I am sure you have used the configuration in airavata code where we have a global handler. So global handler will get called for all the configuration.
> GFacAPI logic to load input/output handlers is not working property
> -------------------------------------------------------------------
>
> Key: AIRAVATA-1026
> URL: https://issues.apache.org/jira/browse/AIRAVATA-1026
> Project: Airavata
> Issue Type: Bug
> Components: GFac
> Reporter: Raminderjeet Singh
> Fix For: 0.13
>
>
> I have a grid machine with Gram server but no GridFTP server. I tried to customize gfac-config.xml for a application to have a custom chain like below. Logic is calling GridFTP input/output handlers also after calling the SCP handlers. Work around this problem is to create a copy of GramProvider and then add that to application tag.
> <Application name="Echo_carter" class="org.apache.airavata.gfac.provider.impl.GramProvider" host="org.apache.airavata.schemas.gfac.impl.GlobusHostTypeImpl">
> <InHandlers>
> <Handler class="org.apache.airavata.gfac.handler.SCPDirectorySetupHandler"/>
> <Handler class="org.apache.airavata.gfac.handler.SCPInputHandler"/>
> </InHandlers>
> <OutHandlers>
> <Handler class="org.apache.airavata.gfac.handler.SCPOutputHandler"/>
> </OutHandlers>
> </Application>
--
This message was sent by Atlassian JIRA
(v6.2#6252)