airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenno Vanommeslaeghe (JIRA)" <>
Subject [jira] [Commented] (AIRAVATA-779) Xbaya: handling of StringArray is not consistent with URIArray
Date Fri, 16 Aug 2013 02:18:47 GMT


Kenno Vanommeslaeghe commented on AIRAVATA-779:

I don't fully understand the options you are proposing - could you provide some examples?

Either way, I don't think there exists a generic solution. There are a lot of UNIX tools and
programs that accept a variable-length argument list. No matter whether you go with a quoted
or a comma-separated list, it will break services that directly call such applications (without
a wrapper script) because both list types will be passed as a single argument. So either you
have to break the possibility of calling these UNIX tools and programs without a wrapper script,
or you have to specify that no Xbaya service should ever receive more than one array (of a
different type).

The big advantage of my proposal is that space-separated lists are the native list format
in UNIX, making the required wrapper script extremely simple:
# Wrapper script to pass 2 arrays to the program "ls"

# In this example, all the elements are passed individually to ls because we don't quote "$arglist"
ls $arglist1 $arglist2
Or, an even simpler solution:
# The quotes are lost (unless we explicitly repeat them)
ls $1 $2
To further illustrate the ease of handling space-separated lists in the shell, here's a script
to perform an operation on each element of an array:

for i in $arglist1 ; do
  cp -p $i $i.bak
> Xbaya: handling of StringArray is not consistent with URIArray
> --------------------------------------------------------------
>                 Key: AIRAVATA-779
>                 URL:
>             Project: Airavata
>          Issue Type: Bug
>          Components: GFac, XBaya
>            Reporter: Suresh Marru
>             Fix For: 0.9
> Reported by Airavata user at -

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:

View raw message