[jira] [Resolved] (OOZIE-861) allow for use of multiple

["Virag Kothari (JIRA)" <ji...@apache.org>]

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

Virag Kothari resolved OOZIE-861.
---------------------------------

       Resolution: Fixed
    Fix Version/s: trunk
    
> allow for use of multiple <java-opts>
> -------------------------------------
>
>                 Key: OOZIE-861
>                 URL: https://issues.apache.org/jira/browse/OOZIE-861
>             Project: Oozie
>          Issue Type: Improvement
>            Reporter: Britt Cyr
>            Assignee: Britt Cyr
>            Priority: Minor
>             Fix For: trunk
>
>         Attachments: OOZIE-861-DOCS.patch, OOZIE-861-v2.patch, OOZIE-861-v3.patch, OOZIE-861-v4.patch, OOZIE-861-v5.patch, OOZIE-861.patch
>
>
> From the workflow schema you'll see:
>     <xs:element name="java-opts" type="xs:string" minOccurs="0" maxOccurs="1"/>
> However, 'arg' is:
>     <xs:element name="arg" type="xs:string" minOccurs="0"
> maxOccurs="unbounded"/>
> Notice the 'maxOccurs' difference.
> Instead of having:
> <java-opts>-Dparam1=val1 -Dparam2=val2 -Dparam3=val3 ...</java-opts>
> It would be easier to have:
> <java-opt>-Dparam1=val1</java-opt>
> <java-opt>-Dparam2=val2</java-opt>
> <java-opt>-Dparam3=val3</java-opt>
> ...
> Just like we can do with <arg>.  Hence, the inconsistency.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira