You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/10/03 21:26:20 UTC

[jira] [Commented] (AIRAVATA-2124) Replace XSLT base script generation with Groovy Template Engine.

    [ https://issues.apache.org/jira/browse/AIRAVATA-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543474#comment-15543474 ] 

ASF subversion and git services commented on AIRAVATA-2124:
-----------------------------------------------------------

Commit c3064689d04a1e7f348d48ae733c04b8c3756480 in airavata's branch refs/heads/develop from [~shameera]
[ https://git-wip-us.apache.org/repos/asf?p=airavata.git;h=c306468 ]

Replaced xslt templates with groovy templates, fixed AIRAVATA-2124


> Replace XSLT base script generation with Groovy Template Engine.
> ----------------------------------------------------------------
>
>                 Key: AIRAVATA-2124
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2124
>             Project: Airavata
>          Issue Type: Improvement
>          Components: GFac
>    Affects Versions: 0.17-SNAPSHOT
>            Reporter: Shameera Rathnayaka
>            Assignee: Shameera Rathnayaka
>             Fix For: 0.17-SNAPSHOT
>
>
> We are using XSLT+ XSD + CodeGen to generate our job submission scripts. Compare to our requirement(just to generate simple script)  we are using heavy tools and adding unnecessary complications. Another downside is all dependency we need to do this XSLT transformation cause to increase the size of the airavata distribution. I am thinking of simple Groovy Template base implementations to replace with this XSLT.  Compare to the learning curve of both XSLT and Groovy where Groovy has simplest learning curve compare to XSLT, it is easy to maintain groovy template than XSLT.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)