[ https://issues.apache.org/jira/browse/OOZIE-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15621559#comment-15621559 ]
Goun Na commented on OOZIE-1120: -------------------------------- It would be good to have a valid xsd url when developing workflows outside of the oozie server. > User Request: publish permalinks to xsd files > --------------------------------------------- > > Key: OOZIE-1120 > URL: https://issues.apache.org/jira/browse/OOZIE-1120 > Project: Oozie > Issue Type: Improvement > Components: docs > Affects Versions: trunk > Reporter: jun aoki > Priority: Minor > > It will be good if the schema files are accessible from a real xml file, > but not in a part of web page. > For example > http://svn.apache.org/viewvc/oozie/trunk/client/src/main/resources/oozie-workflow-0.4.xsd?revision=1382193&view=co > is a real file, but the URL is not ideal because it has a > revision number and it should not even be in a Subversion. > Instead, it will be great if we could publish it shorter and more permanent > link type like > http://oozie.apache.org/schemas/3.1.3/oozie-workflow-0.4.xsd > What users benefit from it is they can open any XML editor (e.g. Eclipse, > XMLSpy) and start with schemaLocation attribute, then the editors will > autocomplete and suggests possible elements and attributes. > Editor Example > <?xml version="1.0" encoding="UTF-8"?> > <workflow-app xmlns="uri:oozie:workflow:0.4" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="uri:oozie:workflow:0.4 > http://oozie.apache.org/schemas/3.1.3/oozie-workflow-0.4.xsd" > name="flow1"> > <start to="next1"/> > <action name="action1"> > <map-reduce></map-reduce> > <ok to="ok1"/> > <error to="error1"/> > </action> > <end name="end1"/> > </workflow-app> > where <start> <action> <map-reduce> <end> and all other elements defined in > the xsd can be suggested and autocompleted by the XML editors. It is very > productive for users. -- This message was sent by Atlassian JIRA (v6.3.4#6332)