On 31/07/13 20:27, Sylvain GRELLET wrote: > Thank you for your quick answer. > It works.
Great! > I forgot to adjust those namespaces the way I did for the xsds. > What surprises me is the way the internal app-schema processes work on > that aspect. > Xsds produced are clean and contain all the information required to > generate a clean XML. > Redefining the name space apart from the xsd seems a duplication to me > thus a maintenance risk (but I don't know the source code). Namespace prefixes are local to the document in which they are found, so in theory users could set them to be anything in the mapping file. However, you are right: editing XML files is painful. A better app-schema configuration interface would automatically suggest namespaces and prefixes, and even better, allow autocompletion and validation of mapping paths based on loaded schemas. This would make the construction of mapping files easier and less error prone. Unfortunately, this development is not yet funded. But one day! Kind regards, -- Ben Caradoc-Davies <[email protected]> Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
