[
https://issues.apache.org/jira/browse/OOZIE-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Becker updated OOZIE-3005:
---------------------------------
Description:
All the Oozie workflow actions have to be covered, not only MapReduce ones,
considering following:
* no XSD change should be performed
* XJB mapping file has to be extended to incorporate all the workflow action
types, also the ones inside
* Use the same namespace prefixes / namespaces in the XMLs as in the Oozie
examples.
* *
{{//xs:complexType[@name='ACTION']/xs:sequence/xs:choice/xs:any[@namespace='##other']}}
* XJB mapping file has to be extended to incorporate SLA related stuff inside
{{//xs:complexType[@name='ACTION']/xs:sequence/xs:any[@namespace='uri:oozie:sla:0.1
uri:oozie:sla:0.2']}}
* autogenerate sources from different XSDs to different packages, resolve
namespace clashes that way. Note that it's not a goal to have all namespace
clashes resolve within XSDs
* extend {{TestJAXBWorkflow}} to handle all those different action types, and
SLA, as well
was:
All the Oozie workflow actions have to be covered, not only MapReduce ones,
considering following:
* no XSD change should be performed
* XJB mapping file has to be extended to incorporate all the workflow action
types, also the ones inside
{{//xs:complexType[@name='ACTION']/xs:sequence/xs:choice/xs:any[@namespace='##other']}}
* XJB mapping file has to be extended to incorporate SLA related stuff inside
{{//xs:complexType[@name='ACTION']/xs:sequence/xs:any[@namespace='uri:oozie:sla:0.1
uri:oozie:sla:0.2']}}
* autogenerate sources from different XSDs to different packages, resolve
namespace clashes that way. Note that it's not a goal to have all namespace
clashes resolve within XSDs
* extend {{TestJAXBWorkflow}} to handle all those different action types, and
SLA, as well
> Cover all workflow action types and workflow / action SLA with JAXB
> -------------------------------------------------------------------
>
> Key: OOZIE-3005
> URL: https://issues.apache.org/jira/browse/OOZIE-3005
> Project: Oozie
> Issue Type: Sub-task
> Components: client
> Reporter: Daniel Becker
> Assignee: Andras Piros
>
> All the Oozie workflow actions have to be covered, not only MapReduce ones,
> considering following:
> * no XSD change should be performed
> * XJB mapping file has to be extended to incorporate all the workflow action
> types, also the ones inside
> * Use the same namespace prefixes / namespaces in the XMLs as in the Oozie
> examples.
> * *
> {{//xs:complexType[@name='ACTION']/xs:sequence/xs:choice/xs:any[@namespace='##other']}}
> * XJB mapping file has to be extended to incorporate SLA related stuff inside
> {{//xs:complexType[@name='ACTION']/xs:sequence/xs:any[@namespace='uri:oozie:sla:0.1
> uri:oozie:sla:0.2']}}
> * autogenerate sources from different XSDs to different packages, resolve
> namespace clashes that way. Note that it's not a goal to have all namespace
> clashes resolve within XSDs
> * extend {{TestJAXBWorkflow}} to handle all those different action types, and
> SLA, as well
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
