As I have been working through this set of configuration files I have noticed a series or XML fragments. Although it is generally bad form to use fragments, I have not run into any difficulty yet. The schema fragments on the other hand do cause difficulties, because they employ namespaces, which are not supported for XML fragments.
At this time I am planning on an Evil Hack either turning off namespaces at the parser (if this works) or modifying the XML input on the fly to provide namespace information. In the future the configuration files should be written as complete documents.
David
Wait, what's the definition of XML fragments? I'm not sure that I really
understand. If you'd like I can change things for the 1.1.0 release, if
it's not too hard. The current config files have not really been
solidified, they've only been out in a beta release, and we warned that
things might change (though I'll probably do the same for the 1.1.0
release, since it looks like you will be changing things).
As for schema fragments, I assume you're talking about the schema.xml
files? You're actually more than welcome to change those around as you'd
like (as long as you can still get proper responses, be sure to check in
with changes), as I think most users will be fine to let geoserver
generate their schemas for them. Currently if you do not have a
schema.xml file then FeatureTypeTransformer will create a valid schema
based on the FeatureType. The schema.xml file will be around just for
users who want more control (though since we do little actual validation
with it it's not so useful, but if people use the validation code then
they can put the rules in to the schema.xml file - though in an ideal
world we would be able to generate schemas that take into account the
validation rules as well.).
So you can pretty much do what you'd like with schema.xml files, I would
just like a way for users to somehow make more complex schema files than
the ones automatically generated (though I'm not sure any users really
care about that functionality, so it's not the highest priority).
Chris
On Tue, 30 Dec 2003, David Zwiers wrote:
As I have been working through this set of configuration files I have
noticed a series or XML fragments. Although it is generally bad form to
use fragments, I have not run into any difficulty yet. The schema
fragments on the other hand do cause difficulties, because they employ
namespaces, which are not supported for XML fragments.
At this time I am planning on an Evil Hack either turning off namespaces
at the parser (if this works) or modifying the XML input on the fly to
provide namespace information. In the future the configuration files
should be written as complete documents.
David
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--